Search results

  • test-cluster-01 192.168.220.244 test-cluster-02 192.168.220.245
    6 KB (701 words) - 09:15, 5 September 2021
  • == How to test the feature == If possible, include instructions to also test with other projects - e.g. libvirt interfaces with qemu
    4 KB (547 words) - 04:52, 1 December 2015
  • == Testing Linux usermode emulation with the Linux Test Project == ...ttp://linux-test-project.github.io/ Linux Test Project]'s syscall tests to test QEMU's linux-user mode support. These instructions are for how to do that u
    5 KB (875 words) - 18:07, 20 October 2016
  • === Memory hotplug test === ...ovide ability to inspect memory settings using QMP interface and implement test cases on top of that.
    1 KB (233 words) - 14:10, 14 January 2019
  • * Step 2: use cryptodev-linux test the crypto functions Use the cryptodev-linux module to test the crypto functions in the guest.
    3 KB (450 words) - 19:41, 30 September 2023
  • ...register-test ...That's okay: if there is no incoming edge, simply there will be no way to test the device. Another machine can add the required node and then QSDHCI_MM w
    13 KB (1,416 words) - 14:21, 25 March 2019
  • == Test case == The test is just to migrate a machine to another with a different qemu version.
    9 KB (917 words) - 10:26, 12 October 2016
  • userspace, so it can be used to test programs which only implement # Test MIPS MSA/SIMD/LoongsonMMI with RISU
    3 KB (401 words) - 09:48, 4 February 2021
  • ...project will be mostly to QEMU, but some parts will also extend LTP (Linux Test Project). # Within LTP (Linux Test Project), develop unit tests for selected ioctls that are supported in QEMU
    3 KB (524 words) - 11:14, 5 February 2020
  • ...be open source, and preferably having license compatible with QEMU); those test programs should be distributed like this: 4-5 FPU CPU-intensive, 4-5 non-FP * measure execution time and other performance data of all selected test program across all targets on Intel and possibly other hosts, for the lates
    3 KB (483 words) - 10:42, 5 February 2020
  • ...ow, this automated tool has been running continuously for months to stress test FVD.
    2 KB (253 words) - 14:45, 11 October 2016
  • openSUSE Factory ppc64le fails acpi-test, whereas ppc and ppc64 succeed. ''Turned out to be tcg/ppc64/ broken for pp
    565 bytes (93 words) - 14:27, 3 April 2014
  • * tests/test-char fails on CentOS 7 - see https://patchew.org/logs/20200716150617.402735 ...059], [https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg01952.html test 259]
    3 KB (468 words) - 08:45, 20 August 2020
  • * Implement automated tests with cargo test. * Test the implementation with QEMU, which can act as a vhost-user frontend.
    3 KB (412 words) - 14:56, 12 February 2024
  • ...for communication with the per-session processes. Make a dummy process and test that the connection does work. ** Parse the incoming responses from host to guest-session RPCs and test the proper working of RPCs and their responses.
    3 KB (455 words) - 08:09, 13 October 2016
  • * centos and ubuntu.i386 vm-test-build targets ** check-unit: tests/test-aio-multithread fails on NetBSD
    2 KB (288 words) - 13:58, 16 June 2020
  • === '''Test environment prepare''' === === '''Test steps''' ===
    6 KB (789 words) - 18:43, 6 June 2020
  • ...s Linaro's Automated Validation test suite [http://www.linaro.org/projects/test-validation/]. In QEMU's context a number of CI job have been set-up to trac
    641 bytes (106 words) - 14:52, 7 August 2017
  • | Tag qemu-1.0-rc1. [[Planning/1.0/Testing|Test Day]]
    761 bytes (113 words) - 07:37, 4 November 2011
  • * SPARC host failure in tests/virtio-9p-test (using le*_to_cpus() on unaligned field in packed struct) * SPARC host failure in tests/bios-tables-test (unaligned field in packed struct)
    3 KB (397 words) - 00:07, 29 August 2017
View ( | ) (20 | 50 | 100 | 250 | 500)