Search results

Page title matches

  • === 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

Page text matches

  • = CCW Test Device = ...ly exiting emulated devices (like virtio-ccw or 3270). This can be used to test features mandated by the architecture that are not yet implemented for any
    1 KB (223 words) - 08:46, 18 September 2017
  • The qemu-iotests test suite is located in tests/qemu-iotests/. It contains test for disk image formats and block layer features. ==Running test cases==
    2 KB (298 words) - 10:00, 12 October 2016
  • ===Nested SVM test improvements=== between them. When we want to test nested virtualization we need to make
    1 KB (221 words) - 16:55, 23 January 2019
  • ! Test/Environment | ERROR:tests/test-aio-multithread.c:365:test_multi_fair_mutex: assertion failed (counter == a
    2 KB (184 words) - 14:57, 14 February 2020
  • | | Test feature | | | | | | | ...| | +--------+----------+ | | | Tag Release |<-+ qemu.git |<-+ Test and Merge |<-------+ Request | |
    5 KB (134 words) - 20:04, 9 March 2018
  • '''Summary:''' Automated test of Guest ABI and compatibility automated test cases that will compare a virtual machine to a
    1 KB (218 words) - 18:51, 21 January 2019
  • = Compatibility Test Matrix = == Guest Configuration and Test Criteria ==
    3 KB (323 words) - 10:24, 12 October 2016
  • This page describes the work to be done on improving QMP test coverage and quality. ...* specification. This is a big effort, as each command should have its own test suite
    2 KB (388 words) - 08:17, 12 October 2016
  • == Test jobs ==
    1 KB (182 words) - 11:03, 1 August 2019
  • Here is a collection of links to disk images which can be used to test system emulation. | OpenRISC Linux 5.0 smp test image. Contains a vmlinux binary that includes an initramfs with busybox, n
    1 KB (176 words) - 12:21, 27 January 2020
  • ...Test based test will spin up one or more QEMU binaries and orchestrate the test via a qtest control socket. The binaries themselves are usually controlled === Isolating the failing test ===
    4 KB (694 words) - 09:21, 5 January 2024
  • ...alization, including a hypervisor and the link script to integrate current test suites. This module of kvm-unit-tests aims at providing a suite of test cases for nested virtualization. It consists of two parts:
    6 KB (976 words) - 15:40, 11 October 2016
  • ...e about and are willing to test release candidates against. Please try to test each release candidate and raise any regressions on the mailing list. Mark a test success <font color="green">green</font> and a failure with <font color="re
    2 KB (297 words) - 16:56, 13 October 2011
  • make docker-test-quick@centos7 ...available flavors, such as "make docker-test-full@ubuntu" or "make docker-test-mingw@fedora". Run
    5 KB (738 words) - 09:54, 26 April 2021
  • ...ite a prototype coroutine implementation coroutine-cpc.c that passes tests/test-coroutine * Debugged implementation to see why it fails the last test
    876 bytes (123 words) - 00:06, 14 July 2013
  • == N8x0Machine.test_n810 avocado test sometimes times out == .../builds/qemu-project/qemu/build/tests/results/job-2023-03-09T22.29-2da5ef9/test-re... (90.26 s)
    7 KB (914 words) - 10:34, 10 March 2023
  • == Compilation test == | Test || Result
    1 KB (204 words) - 18:22, 15 February 2013
  • * ahci-test fails on openSUSE Tumbleweed ppc64. (fixed in 2.3.0-rc1) * rcutorture test fails to build on openSUSE Tumbleweed ppc (gcc 4.8.3): <code>undefined refe
    2 KB (255 words) - 21:28, 16 April 2015
  • ...e about and are willing to test release candidates against. Please try to test each release candidate and raise any regressions on the mailing list. Mark a test success <font color="green">green</font> and a failure with <font color="re
    3 KB (435 words) - 05:13, 19 May 2011
  • == How to Test PowerPC Instructions Using Risu == ...runs in qemu-system-ppc is the host. Both copies of risu must use the same test file. This file is called ppc.out. It will contain machine code that will b
    5 KB (921 words) - 23:02, 9 December 2017
  • 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
  • ...f we do not have an "make check" regression test for it. (i.e. did anybody test the bluetooth code in the recent years?)
    2 KB (354 words) - 16:20, 27 April 2018
  • ...OS bringup, debugging and bootstrapping very difficult. Having a local dev&test environment that looks like an Enclave, but is 100% controlled by the devel * Add integration test for the machine model executing an actual EIF payload
    2 KB (363 words) - 20:30, 29 March 2022
  • =QEMU 1.2 Test day: Aug 16 2012= If the test:
    4 KB (549 words) - 13:08, 28 August 2012
  • ...or seq in $(seq 1 100); do echo "test $seq" > /dev/virtio-ports/org.kraxel.test; sleep 1; done</pre> ...1 100); do echo "test $seq"; sleep 1; done) > /dev/virtio-ports/org.kraxel.test</pre>
    4 KB (549 words) - 12:39, 22 March 2022
  • ** PCI test device ({{src|path=docs/specs/pci-testdev.txt}})
    1 KB (162 words) - 15:02, 7 July 2017
  • The result then runs the entire GCC test suite with ARM or AArch64 qemu-user. On failure the tool identifies which o
    1 KB (207 words) - 14:49, 14 July 2020
  • Having a local development and test environment that looks like an Enclave, but is * Add integration test for the machine model executing an actual EIF payload
    3 KB (426 words) - 20:13, 30 January 2024
  • ...rk, but must be open source, and preferably license compatible with QEMU); test programs should be distributed like this: 4-5 FPU CPU-intensive, 4-5 non-FP
    2 KB (373 words) - 05:56, 31 January 2020
  • - Test cases around with doing this indirectly to test the conversions by doing some
    8 KB (1,202 words) - 16:21, 24 April 2014
  • QEMU includes a test suite comprising: * [[Testing/QemuIoTests|qemu-iotests]], a regression test suite for the block layer code.
    9 KB (1,420 words) - 12:16, 12 July 2021
View (previous 50 | ) (20 | 50 | 100 | 250 | 500)