Search results
- === Testing and CI ===3 KB (330 words) - 13:35, 16 May 2024
- * More testing1 KB (181 words) - 13:57, 9 March 2020
- This is currently used for testing the integration of rust-vmm components, with plans of extending it2 KB (251 words) - 12:53, 25 February 2022
- place into a Virtio queue for validation, testing, and evaluation purposes.2 KB (241 words) - 16:10, 31 March 2021
- # Testing the connection recovery for all possible failure scenarios.2 KB (262 words) - 18:05, 20 May 2016
- '''Summary:''' Create memory hotplug testing infrastructure.1 KB (233 words) - 14:10, 14 January 2019
- | Debian testing || ? || ? || ? || ? || ? || ? * Comprehensive libvirt testing4 KB (549 words) - 13:08, 28 August 2012
- Early development. Not yet ready for testing.2 KB (234 words) - 18:17, 23 May 2019
- == Testing & documentation ==7 KB (970 words) - 11:30, 12 March 2019
- Currently pre-merge testing is done via a set of tests done by ad-hoc shell scripts run on a set of mac I also have access to a SPARC box but am not currently testing with it as there are hangs which I did not have time to investigate.9 KB (1,554 words) - 17:40, 12 November 2019
- ...eca ("s390/cio: Fix vfio-ccw handling of recursive TICs") but some further testing/proof would be beneficial. == Testing ==9 KB (1,396 words) - 11:18, 11 December 2019
- === 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 yourse19 KB (3,009 words) - 15:08, 16 February 2016
- ...MU maintainer for various Python utilities, libraries and scripts used for testing and debugging in the QEMU codebase, has two cats, and really likes Pokemon. ...ynchronous QMP library]: This is the existing QMP library used for various testing and debug utilities upstream in QEMU today. It is also strictly typed with5 KB (884 words) - 17:57, 15 January 2021
- * [[Testing#Continuous_Integration|Continuous Integration]]: [https://gitlab.com/qemu-p2 KB (312 words) - 11:51, 25 January 2022
- For testing just pull the third part, no need to pull the two firsts.2 KB (356 words) - 15:14, 11 October 2016
- testing as the code develops is needed.2 KB (339 words) - 15:45, 9 February 2023
- * Since compilation and testing time for QEMU is really huge, we could get rid of some QEMU binaries: qemu-2 KB (354 words) - 16:20, 27 April 2018
- == Testing Linux usermode emulation with the Linux Test Project == # skiplist for QEMU testing5 KB (875 words) - 18:07, 20 October 2016
- * Buildbot-style infrastructure for automated migration testing3 KB (323 words) - 10:24, 12 October 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
- ad-hoc testing are: If you are in a position to do perhaps a subset of this ad-hoc testing that would be nice, but it isn't mandatory.8 KB (1,406 words) - 10:09, 13 April 2022
- ...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 a2 KB (389 words) - 15:20, 12 October 2016
- ** Test the code for multiple clients, remove hooks for testing and final cleanup3 KB (455 words) - 08:09, 13 October 2016
- setups (for example, building and testing tools and applications under3 KB (524 words) - 11:14, 5 February 2020
- | 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
- ...I2C devices from inside the guest, for example for developers writing and testing software under QEMU on their computer. This would be used like ''-device i4 KB (626 words) - 16:20, 25 March 2019
- === Testing and CI ===8 KB (1,060 words) - 18:28, 9 December 2021
- === 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 yourse17 KB (2,629 words) - 15:07, 16 February 2016
- * New '''virt''' platform is added to assist with CI and device testing === Testing and CI ===11 KB (1,553 words) - 14:27, 3 February 2023
- ...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 (547 words) - 12:35, 22 March 2022
- ...of this CPU type anymore and no binaries available which could be used for testing. === Testing and CI ===12 KB (1,665 words) - 16:02, 24 August 2021
- * Implement cache testing opcodes. ...on'' can now be configured to report an exit-failure (useful for automated testing)13 KB (1,895 words) - 13:55, 20 August 2022
- === Testing ===11 KB (1,631 words) - 11:24, 3 December 2019
- This docker image can then be used for cross build testing with the normal docker test stanzas:5 KB (738 words) - 09:54, 26 April 2021
- A mini hypervisor is the basis of testing nested virtualization. Here is a mini hypervisor written in C++ named [http6 KB (976 words) - 15:40, 11 October 2016
- === Testing ===11 KB (1,707 words) - 08:58, 24 October 2019
- ...adthedocs.io/en/latest/system/guest-loader.html guest loader] which allows testing of Xen-like hypervisors booting kernels without messing around with firmwar ...adthedocs.io/en/latest/system/guest-loader.html guest loader] which allows testing of Xen-like hypervisors booting kernels without messing around with firmwar19 KB (2,811 words) - 07:39, 16 April 2021
- ...long-term goal is to augment this interface with more features related to testing and debugging.5 KB (823 words) - 15:54, 23 August 2021
- '''Summary:''' Apply the afl-fuzz fuzz testing tool to qemu-img and submit patches fixing bugs discovered with afl-fuzz. ...oject is suitable for candidates interested in software security, software testing, compilers, and disk image file formats.13 KB (1,926 words) - 10:50, 22 March 2016
- === Testing and CI ===12 KB (1,689 words) - 16:12, 14 May 2021
- === Testing and CI ===12 KB (1,752 words) - 14:51, 19 April 2023
- .... If you are starting out you can download the OpenRISC test image from [[Testing/System_Images]]. The test image may be gzipped, so be sure to gunzip it fi5 KB (783 words) - 21:34, 4 July 2022
- ...image manipulation. This is a good foundation API for building integration testing systems, richer QEmu-based applications, and so forth.7 KB (1,011 words) - 08:14, 13 April 2021
- === Testing ===14 KB (2,072 words) - 20:38, 28 April 2020
- * The cipher test suite will automatically skip testing algorithms that have been disabled in the underlying OS crypto library at b === Testing and CI ===14 KB (2,091 words) - 09:34, 7 May 2024
- ...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
- ...to describe the steps needed to setup a development machine for vhost-user testing.5 KB (696 words) - 15:11, 11 October 2016
- * When running <tt>make check-avocado</tt>, the Avocado testing framework and pycdlib must be present if the build tree was configured with === Testing and CI ===15 KB (2,193 words) - 13:57, 18 December 2023
- === Testing and CI ===13 KB (1,888 words) - 07:16, 11 April 2022