Search results

Jump to: navigation, search

Page title matches

  • =QEMU 0.14 Release Testing= Add yourself to volunteer for QEMU 0.14 release testing.
    3 KB (435 words) - 05:13, 19 May 2011
  • =QEMU 0.15 Release Testing= Add yourself to volunteer for QEMU 0.15 release testing.
    2 KB (297 words) - 16:56, 13 October 2011
  • | Debian testing || ? || <b><font color="green">rc2</font></b> || <b><font color="green">rc2 * Comprehensive libvirt testing [LuizCapitulino]
    7 KB (1,052 words) - 16:41, 29 November 2011
  • * [[Testing/QemuIoTests|qemu-iotests]], a regression test suite for the block layer cod ...continuous integration]] systems, based on [[Testing/Travis|Travis]] and [[Testing/Patchew|Patchew]].
    8 KB (1,206 words) - 17:22, 15 November 2017
  • | Debian testing || ? || ? || ? || ? || ? || ? * Comprehensive libvirt testing
    4 KB (549 words) - 13:08, 28 August 2012
  • == Testing Linux usermode emulation with the Linux Test Project == # skiplist for QEMU testing
    5 KB (875 words) - 18:07, 20 October 2016
  • 1 KB (204 words) - 18:22, 15 February 2013
  • 2 KB (298 words) - 10:00, 12 October 2016
  • 865 B (140 words) - 13:56, 25 October 2016
  • 565 B (93 words) - 14:27, 3 April 2014
  • 641 B (106 words) - 14:52, 7 August 2017
  • ...C Linux 4.10 test image + initramfs with busybox, kselftest and strace for testing
    1 KB (160 words) - 17:06, 7 August 2017
  • 2 KB (255 words) - 21:28, 16 April 2015
  • 655 B (82 words) - 17:13, 9 July 2015
  • This docker image can then be used for cross build testing with the normal docker test stanzas:
    4 KB (547 words) - 09:23, 12 October 2016
  • 0 B (0 words) - 19:30, 13 August 2017
  • Patchew is an open source CI project to automate testing of patches submitted as emails on mailing lists.
    471 B (74 words) - 02:16, 21 August 2017
  • ...al -device mechanism. It needs a control unit type especially reserved for testing. As only numbers are used for real control unit types, 0xffff looks like a From the guest side, this looks like a normal ccw device. Testing might be done via a custom Linux kernel driver, the kvm-test infrastructure
    1 KB (223 words) - 08:46, 18 September 2017

Page text matches

  • ...image manipulation. This is a good foundation API for building integration testing systems, richer QEmu-based applications, and so forth.
    8 KB (1,200 words) - 14:11, 20 February 2017
  • * [[Testing#Continuous_Integration|Continuous Integration]]: [https://travis-ci.org/qem
    2 KB (277 words) - 16:35, 29 November 2017
  • ...ested guests. This can improve performance and greatly aid with automated testing.
    14 KB (2,116 words) - 15:02, 16 February 2016
  • This could be fixed by fleshing out error handling code and testing using Kevin's blkdebug.
    2 KB (379 words) - 14:54, 11 October 2016
  • * Coded query-netdev fixes. Needs more testing.
    23 KB (3,423 words) - 17:43, 11 August 2010
  • ...erent targets (x86, mips, powerpc, ...). Images can be obtained from the [[Testing]] page. == Testing your changes ==
    7 KB (1,207 words) - 18:49, 27 February 2017
  • ...HEAD scripts/qmp/] directory in QEMU's source-tree. It automates a bit the testing work, as it can construct commands objects for you.
    4 KB (574 words) - 18:01, 17 February 2017
  • Also see [[Planning/2.4/Testing]].
    882 B (126 words) - 16:12, 21 October 2015
  • = QMP Testing TODO = kvm-autotest is going to be used to do all client-side QMP testing.
    2 KB (388 words) - 08:17, 12 October 2016
  • .... If you are starting out you can download the OpenRISC test image from [[Testing/System_Images]].
    2 KB (305 words) - 14:27, 18 July 2017
  • = Testing plan = Please see the [[Planning/0.14/Testing|testing page]].
    423 B (56 words) - 09:57, 7 February 2017
  • =QEMU 0.14 Release Testing= Add yourself to volunteer for QEMU 0.14 release testing.
    3 KB (435 words) - 05:13, 19 May 2011
  • * testing and stabilizing host pass-through of various devices The task consists of identifying open issues and use cases by testing them against various guest systems, then fixing the deficits, and proposing
    15 KB (2,288 words) - 15:07, 16 February 2016
  • ...as designed and engineered rigorously. Following a systematic methodology, testing and debugging facilities were built into FVD from day one to automatically * On the observation of the lack of a method for testing race conditions (I/O order and callback order) in QEMU block drivers, an ev
    2 KB (253 words) - 14:45, 11 October 2016
  • can dedicate their time to implementing and testing. If there is no previous
    9 KB (1,281 words) - 10:12, 9 September 2016
  • === Continuous VMState testing (GSOC project) === * Unit testing. In colaboration with qdev, allow devices to be tested alone with old/new
    5 KB (737 words) - 06:10, 25 March 2015
  • ...that well. I think I've worked out most of these issues but more rigorous testing is needed.
    14 KB (2,108 words) - 15:06, 11 October 2016
  • =QEMU 0.15 Release Testing= Add yourself to volunteer for QEMU 0.15 release testing.
    2 KB (297 words) - 16:56, 13 October 2011
  • | Tag qemu-1.0-rc1. [[Planning/1.0/Testing|Test Day]]
    761 B (113 words) - 07:37, 4 November 2011
  • existing QMPOutputVisitor, as well as debugging/testing migration via a well == (old) Testing ==
    8 KB (1,202 words) - 16:21, 24 April 2014
  • | Debian testing || ? || <b><font color="green">rc2</font></b> || <b><font color="green">rc2 * Comprehensive libvirt testing [LuizCapitulino]
    7 KB (1,052 words) - 16:41, 29 November 2011
  • == Testing ==
    8 KB (1,276 words) - 05:38, 3 June 2012
  • ...lirp is posted to vmstate still missing are the toplevel lists , need some testing ** VmState Sections/Subsections testing.
    2 KB (390 words) - 15:54, 11 October 2016
  • * [[Testing/QemuIoTests|qemu-iotests]], a regression test suite for the block layer cod ...continuous integration]] systems, based on [[Testing/Travis|Travis]] and [[Testing/Patchew|Patchew]].
    8 KB (1,206 words) - 17:22, 15 November 2017
  • ...rtualizing OS X guests in KVM. A few devices still need to be up-streamed. Testing needs to be done, and likely some new code will have to be written to fix c
    17 KB (2,611 words) - 15:07, 16 February 2016
  • ** QMP: [[ToDo/QMP|infrastructure]] and [[ToDo/QMPTesting|testing]]
    387 B (47 words) - 10:12, 9 August 2017
  • ...to add on_error to the existing block-stream command, if only to ease unit testing. Concerns about the stability of the API can be handled by adding introspe
    8 KB (1,370 words) - 14:10, 18 February 2013
  • | [[Planning/1.2/Testing|Test Day]]. Community effort to shake out v1.2.0-rc bugs.
    1 KB (159 words) - 15:38, 11 October 2016
  • See also [[Testing/DockerBuild]] for more information.
    6 KB (915 words) - 14:27, 6 November 2017
  • | Debian testing || ? || ? || ? || ? || ? || ? * Comprehensive libvirt testing
    4 KB (549 words) - 13:08, 28 August 2012
  • == Testing == ...data is prepared. We can use the space time to fill the cache queue. In my testing, the read speed can be improved from 0.9k/s to 500k/s
    6 KB (994 words) - 16:08, 17 October 2016
  • For testing just pull the third part, no need to pull the two firsts.
    2 KB (356 words) - 15:14, 11 October 2016
  • * Buildbot-style infrastructure for automated migration testing
    3 KB (323 words) - 10:24, 12 October 2016
  • === Continuous vmstate testing === ...oject you will learn about live migration and device emulation. When your testing tool discovers bugs you can delve into the affected device to fix it yourse
    17 KB (2,629 words) - 15:07, 16 February 2016
  • == Testing Linux usermode emulation with the Linux Test Project == # skiplist for QEMU testing
    5 KB (875 words) - 18:07, 20 October 2016
  • Testing so far has shown no problems using the vanilla upstream OpenFabrics RDMA li
    20 KB (3,092 words) - 14:55, 11 October 2016
  • == Testing ==
    4 KB (547 words) - 15:41, 11 October 2016
  • For testing only, you can ignore the aforementioned requirements Current required until testing is complete. There are some COLO
    25 KB (4,019 words) - 14:39, 20 July 2015
  • ...nd] works much like QEMU's TCG mode except it has a focus on debugging and testing. You can use it to detect memory corruption and leaks within QEMU as well a
    2 KB (389 words) - 15:20, 12 October 2016
  • ** Test the code for multiple clients, remove hooks for testing and final cleanup
    3 KB (455 words) - 08:09, 13 October 2016
  • A mini hypervisor is the basis of testing nested virtualization. Here is a mini hypervisor written in C++ named [http
    6 KB (976 words) - 15:40, 11 October 2016
  • * Get qemu-img compiling and start testing where it fails
    758 B (105 words) - 01:35, 19 July 2013
  • ...is needed (Now supported on most architectures, tested mainly on x86, some testing on Power and aarch64, s390 support being worked on)
    6 KB (885 words) - 12:28, 16 March 2017
  • * support for testing AIO requests
    17 KB (2,627 words) - 10:39, 6 September 2017
  • === Continuous vmstate testing === ...oject you will learn about live migration and device emulation. When your testing tool discovers bugs you can delve into the affected device to fix it yourse
    19 KB (3,009 words) - 15:08, 16 February 2016
  • Also see [[Planning/2.0/Testing]].
    949 B (134 words) - 20:30, 6 August 2014
  • ...C Linux 4.10 test image + initramfs with busybox, kselftest and strace for testing
    1 KB (160 words) - 17:06, 7 August 2017
  • ===Testing=== * Alex BennĂ©e (ARM testing, base enabling tree)
    3 KB (519 words) - 15:39, 12 July 2017
  • Also see [[Planning/2.3/Testing]].
    931 B (133 words) - 11:24, 30 July 2015
  • It continues to lack any sort of unit-testing framework with the QEMU source tree, however. This is an open-ended project to design/implement a unit-testing framework to address this. This could potentially be done using python, or
    25 KB (3,900 words) - 10:50, 22 March 2016

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)