|
From: | Lucas Meneghel Rodrigues |
Subject: | Re: [Qemu-devel] The state of testing |
Date: | Tue, 05 Mar 2013 13:09:47 -0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130227 Thunderbird/17.0.3 |
On 03/04/2013 01:22 PM, Gerd Hoffmann wrote:
Hi,How are things looking with device emulation, migration, monitor, char, etc?At the moment autotest/virt-test is pretty much the only workable thing for non-trivial devices because libqtest lacks infrastructure for pci and anything building on top of pci. usb has no in-tree tests, but has autotest coverage. chardevs have some autotest coverage, /me wrote a test for chardev-{add,remove} qmp commands. Still need to rebase + polish + submit that one though. Migration coverage is pretty bad overall I think.
On virt-tests there are at least 48 tests that are easy to run and involve migration. A subset of them is executed regularly in the daily jobs:
./run -t qemu -g Fedora.18.x86_64 --list-tests | grep migrat | grep -v multi_host
21 balloon_check.balloon-migrate 51 cpuflags.stress_guest.qemu_test_migration_with_additional_flags 65 migrate.default.tcp 66 migrate.default.unix 67 migrate.default.exec 68 migrate.default.fd 69 migrate.default.mig_cancel 70 migrate.with_speed_measurement.tcp 71 migrate.with_speed_measurement.unix 72 migrate.with_speed_measurement.exec 73 migrate.with_speed_measurement.fd 74 migrate.with_set_speed.tcp 75 migrate.with_set_speed.unix 76 migrate.with_set_speed.exec 77 migrate.with_set_speed.fd 78 migrate.with_reboot.tcp 79 migrate.with_reboot.unix 80 migrate.with_reboot.exec 81 migrate.with_reboot.fd 82 migrate.with_file_transfer.tcp 83 migrate.with_file_transfer.unix 84 migrate.with_file_transfer.exec 85 migrate.with_file_transfer.fd 86 migrate.with_autotest.dbench.tcp 87 migrate.with_autotest.dbench.unix 88 migrate.with_autotest.dbench.exec 89 migrate.with_autotest.dbench.fd 90 migrate.with_autotest.stress.tcp 91 migrate.with_autotest.stress.unix 92 migrate.with_autotest.stress.exec 93 migrate.with_autotest.stress.fd 94 migrate.with_autotest.monotonic_time.tcp 95 migrate.with_autotest.monotonic_time.unix 96 migrate.with_autotest.monotonic_time.exec 97 migrate.with_autotest.monotonic_time.fd 2146 nic_hotplug.migration.nic_8139 (requires root) 2147 nic_hotplug.migration.nic_virtio (requires root) 2148 nic_hotplug.migration.nic_e1000 (requires root)2483 virtio_console.spread_linear.specifiable.virtserialport.with_vm.migration.offline 2484 virtio_console.spread_linear.specifiable.virtserialport.with_vm.migration.online 2515 virtio_console.spread_linear.specifiable.virtconsole.with_vm.migration.offline 2516 virtio_console.spread_linear.specifiable.virtconsole.with_vm.migration.online 2561 virtio_console.spread_2.specifiable.virtserialport.with_vm.migration.offline 2562 virtio_console.spread_2.specifiable.virtserialport.with_vm.migration.online 2584 virtio_console.spread_2.specifiable.virtconsole.with_vm.migration.offline 2585 virtio_console.spread_2.specifiable.virtconsole.with_vm.migration.online
2672 timedrift.ntp.with_migration 2676 timedrift.date.with_migrationThose can be run with relative ease on every developer laptop, not counting the many multi host tests involving migration, that are still not being executed on a regular basis on our test farm. So I don't think migration coverage is that bad.
[Prev in Thread] | Current Thread | [Next in Thread] |