|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [qemu-mainline baseline-only test] 68559: regressions - trouble: blocked/broken/fail/pass
This run is configured for baseline tests only. flight 68559 qemu-mainline real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68559/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt-xsm 11 guest-start fail REGR. vs. 68557 test-amd64-amd64-i386-pvgrub 9 debian-di-install fail REGR. vs. 68557 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-rtds 14 guest-saverestore fail REGR. vs. 68557 test-armhf-armhf-libvirt 13 saverestore-support-check fail like 68557 test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail like 68557 test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail like 68557 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 9 windows-install fail like 68557 Tests which did not succeed, but are not blocking: test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a test-arm64-arm64-xl 1 build-check(1) blocked n/a build-arm64-libvirt 1 build-check(1) blocked n/a test-arm64-arm64-libvirt-qcow2 1 build-check(1) blocked n/a test-arm64-arm64-libvirt 1 build-check(1) blocked n/a test-arm64-arm64-xl-credit2 1 build-check(1) blocked n/a test-arm64-arm64-xl-rtds 1 build-check(1) blocked n/a test-arm64-arm64-xl-multivcpu 1 build-check(1) blocked n/a test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a build-arm64-pvops 2 hosts-allocate broken never pass build-arm64 2 hosts-allocate broken never pass build-arm64-xsm 2 hosts-allocate broken never pass build-arm64-pvops 3 capture-logs broken never pass build-arm64-xsm 3 capture-logs broken never pass build-arm64 3 capture-logs broken never pass test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 13 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass test-armhf-armhf-xl-midway 12 migrate-support-check fail never pass test-armhf-armhf-xl-midway 13 saverestore-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 12 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 13 saverestore-support-check fail never pass test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass test-armhf-armhf-xl-vhd 11 migrate-support-check fail never pass test-armhf-armhf-xl-vhd 12 saverestore-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail never pass test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail never pass version targeted for testing: qemuu ec7a9bd5bb2c46c60cc0ec9b9d9f2ce404226ec0 baseline version: qemuu 305e6c8a2ff7a6e3f4942b50e853230f18eeb5a9 Last test of basis 68557 2017-02-14 09:14:19 Z 0 days Testing same since 68559 2017-02-14 15:44:10 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Amit Shah <amit.shah@xxxxxxxxxx> Ashijeet Acharya <ashijeetacharya@xxxxxxxxx> Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Halil Pasic <pasic@xxxxxxxxxxxxxxxxxx> Li Zhijian <lizhijian@xxxxxxxxxxxxxx> Pavel Butsykin <pbutsykin@xxxxxxxxxxxxx> Peter Maydell <peter.maydell@xxxxxxxxxx> zhanghailiang <zhang.zhanghailiang@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm broken build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-arm64 broken build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt blocked build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-arm64-pvops broken build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-arm64-arm64-xl blocked test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm pass test-arm64-arm64-libvirt-xsm blocked test-armhf-armhf-libvirt-xsm fail test-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-arm64-arm64-xl-xsm blocked test-armhf-armhf-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-amd64-xl-pvh-amd fail test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-credit2 pass test-arm64-arm64-xl-credit2 blocked test-armhf-armhf-xl-credit2 pass test-amd64-i386-freebsd10-i386 pass test-amd64-amd64-qemuu-nested-intel fail test-amd64-amd64-xl-pvh-intel fail test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-arm64-arm64-libvirt blocked test-armhf-armhf-libvirt pass test-amd64-i386-libvirt pass test-armhf-armhf-xl-midway pass test-amd64-amd64-xl-multivcpu pass test-arm64-arm64-xl-multivcpu blocked test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub fail test-amd64-amd64-pygrub pass test-arm64-arm64-libvirt-qcow2 blocked test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw pass test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds fail test-arm64-arm64-xl-rtds blocked test-armhf-armhf-xl-rtds pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd pass test-amd64-amd64-xl-qemuu-winxpsp3 pass test-amd64-i386-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.xs.citrite.net logs: /home/osstest/logs images: /home/osstest/images Logs, config files, etc. are available at http://osstest.xs.citrite.net/~osstest/testlogs/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary broken-step build-arm64-pvops hosts-allocate broken-step build-arm64 hosts-allocate broken-step build-arm64-xsm hosts-allocate broken-step build-arm64-pvops capture-logs broken-step build-arm64-xsm capture-logs broken-step build-arm64 capture-logs Push not applicable. ------------------------------------------------------------ commit ec7a9bd5bb2c46c60cc0ec9b9d9f2ce404226ec0 Merge: 305e6c8 982b78c Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Mon Feb 13 18:49:26 2017 +0000 Merge remote-tracking branch 'remotes/dgilbert/tags/pull-migration-20170213a' into staging Migration Amit: migration: remove myself as maintainer MAINTAINERS: update my email address Ashijeet: migrate: Introduce zero RAM checks to skip RAM migration Pavel: Postcopy release RAM Halil: consolidate VMStateField.start Hailiang: COLO: fix setting checkpoint-delay not working properly COLO: Shutdown related socket fd while do failover COLO: Don't process failover request while loading VM's state Me: migration: Add VMSTATE_UNUSED_VARRAY_UINT32 migration: Add VMSTATE_WITH_TMP tests/migration: Add test for VMSTATE_WITH_TMP virtio-net VMState conversion and new VMSTATE macros # gpg: Signature made Mon 13 Feb 2017 17:36:39 GMT # gpg: using RSA key 0x0516331EBC5BFDE7 # gpg: Good signature from "Dr. David Alan Gilbert (RH2) <dgilbert@xxxxxxxxxx>" # gpg: WARNING: This key is not certified with a trusted signature! # gpg: There is no indication that the signature belongs to the owner. # Primary key fingerprint: 45F5 C71B 4A0C B7FB 977A 9FA9 0516 331E BC5B FDE7 * remotes/dgilbert/tags/pull-migration-20170213a: virtio/migration: Migrate virtio-net to VMState tests/migration: Add test for VMSTATE_WITH_TMP migration: Add VMSTATE_WITH_TMP migration: Add VMSTATE_UNUSED_VARRAY_UINT32 COLO: Don't process failover request while loading VM's state COLO: Shutdown related socket fd while do failover COLO: fix setting checkpoint-delay not working properly migration: consolidate VMStateField.start migrate: Introduce zero RAM checks to skip RAM migration migration: discard non-dirty ram pages after the start of postcopy add 'release-ram' migrate capability migration: add MigrationState arg for ram_save_/compressed_/page() MAINTAINERS: update my email address migration: remove myself as maintainer Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 982b78c5e37864c06fd7b5f156d80bf02628a855 Author: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Date: Fri Feb 3 16:06:51 2017 +0000 virtio/migration: Migrate virtio-net to VMState Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Reviewed-by: Michael S. Tsirkin <mst@xxxxxxxxxx> Message-Id: <20170203160651.19917-5-dgilbert@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Merge fix against Halil's removal of the '_start' field in VMSTATE_VBUFFER_MULTIPLY commit 5c379d9031931fb1be52b96b25589abc7311f200 Author: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Date: Fri Feb 3 16:06:50 2017 +0000 tests/migration: Add test for VMSTATE_WITH_TMP Add a test for VMSTATE_WITH_TMP to tests/test-vmstate.c Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Reviewed-by: Juan Quintela <quintela@xxxxxxxxxx> Message-Id: <20170203160651.19917-4-dgilbert@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit bcf45131293664118355df03d2ce5458156deaad Author: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Date: Fri Feb 3 16:06:49 2017 +0000 migration: Add VMSTATE_WITH_TMP VMSTATE_WITH_TMP is for handling structures where some calculation or rearrangement of the data needs to be performed before the data hits the wire. For example, where the value on the wire is an offset from a non-migrated base, but the data in the structure is the actual pointer. To use it, a temporary type is created and a vmsd used on that type. The first element of the type must be 'parent' a pointer back to the type of the main structure. VMSTATE_WITH_TMP takes care of allocating and freeing the temporary before running the child vmsd. The post_load/pre_save on the child vmsd can copy things from the parent to the temporary using the parent pointer and do any other calculations needed; it can then use normal VMSD entries to do the actual data storage without having to fiddle around with qemu_get_*/qemu_put_* Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Reviewed-by: David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> Reviewed-by: Juan Quintela <quintela@xxxxxxxxxx> Message-Id: <20170203160651.19917-3-dgilbert@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit b5b5c569570c414bf0aa80a5ae9480debe07ed58 Author: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Date: Fri Feb 3 16:06:48 2017 +0000 migration: Add VMSTATE_UNUSED_VARRAY_UINT32 VMSTATE_UNUSED_VARRAY_UINT32 is used to skip a chunk of the stream that's an n-element array; note the array size and the dynamic value read never get multiplied so there's no overflow risk. Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Message-Id: <20170203160651.19917-2-dgilbert@xxxxxxxxxx> Reviewed-by: Juan Quintela <quintela@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit a8664ba5101446f4f2c24b24ed9e10335bbbd46b Author: zhanghailiang <zhang.zhanghailiang@xxxxxxxxxx> Date: Tue Jan 17 20:57:44 2017 +0800 COLO: Don't process failover request while loading VM's state We should not do failover work while the main thread is loading VM's state. Otherwise the consistent of VM's memory and device state will be broken. We will restart the loading process after jump over the stage, The new failover status 'RELAUNCH' will help to record if we need to restart the process. Cc: Eric Blake <eblake@xxxxxxxxxx> Signed-off-by: zhanghailiang <zhang.zhanghailiang@xxxxxxxxxx> Signed-off-by: Li Zhijian <lizhijian@xxxxxxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Message-Id: <1484657864-21708-4-git-send-email-zhang.zhanghailiang@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Added a missing '(Since 2.9)' commit c937b9a6db2d564b96aae35a6757bb4144ea5184 Author: zhanghailiang <zhang.zhanghailiang@xxxxxxxxxx> Date: Tue Jan 17 20:57:43 2017 +0800 COLO: Shutdown related socket fd while do failover If the net connection between primary host and secondary host breaks while COLO/COLO incoming threads are doing read() or write(). It will block until connection is timeout, and the failover process will be blocked because of it. So it is necessary to shutdown all the socket fds used by COLO to avoid this situation. Besides, we should close the corresponding file descriptors after failvoer BH shutdown them, Or there will be an error. Signed-off-by: zhanghailiang <zhang.zhanghailiang@xxxxxxxxxx> Signed-off-by: Li Zhijian <lizhijian@xxxxxxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Cc: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Message-Id: <1484657864-21708-3-git-send-email-zhang.zhanghailiang@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit 479125d53eb8509d69a0548f131028a65fcbd65a Author: zhanghailiang <zhang.zhanghailiang@xxxxxxxxxx> Date: Tue Jan 17 20:57:42 2017 +0800 COLO: fix setting checkpoint-delay not working properly If we set checkpoint-delay through command 'migrate-set-parameters', It will not take effect until we finish last sleep chekpoint-delay, That's will be offensive espeically when we want to change its value from an extreme big one to a proper value. Fix it by using timer to realize checkpoint-delay. Signed-off-by: zhanghailiang <zhang.zhanghailiang@xxxxxxxxxx> Message-Id: <1484657864-21708-2-git-send-email-zhang.zhanghailiang@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit 59046ec29ad4c24391bb9fe1fbdced33557aaa70 Author: Halil Pasic <pasic@xxxxxxxxxxxxxxxxxx> Date: Fri Feb 3 18:52:17 2017 +0100 migration: consolidate VMStateField.start The member VMStateField.start is used for two things, partial data migration for VBUFFER data (basically provide migration for a sub-buffer) and for locating next in QTAILQ. The implementation of the VBUFFER feature is broken when VMSTATE_ALLOC is used. This however goes unnoticed because actually partial migration for VBUFFER is not used at all. Let's consolidate the usage of VMStateField.start by removing support for partial migration for VBUFFER. Signed-off-by: Halil Pasic <pasic@xxxxxxxxxxxxxxxxxx> Message-Id: <20170203175217.45562-1-pasic@xxxxxxxxxxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit 0827b9e97d443781a17a21c64695940675aa1f8a Author: Ashijeet Acharya <ashijeetacharya@xxxxxxxxx> Date: Wed Feb 8 19:58:45 2017 +0530 migrate: Introduce zero RAM checks to skip RAM migration Migration of a "none" machine with no RAM crashes abruptly as bitmap_new() fails and thus aborts. Instead place zero RAM checks at appropriate places to skip migration of RAM in this case and complete migration successfully for devices only. Signed-off-by: Ashijeet Acharya <ashijeetacharya@xxxxxxxxx> Message-Id: <1486564125-31366-1-git-send-email-ashijeetacharya@xxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Reviewed-by: Philippe Mathieu-Daudé <f4bug@xxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit ced1c6166ef901a91578d54ff39f46b3e7ae870f Author: Pavel Butsykin <pbutsykin@xxxxxxxxxxxxx> Date: Fri Feb 3 18:23:21 2017 +0300 migration: discard non-dirty ram pages after the start of postcopy After the start of postcopy migration there are some non-dirty pages which have already been migrated. These pages are no longer needed on the source vm so that we can free them and it doen't hurt to complete the migration. Signed-off-by: Pavel Butsykin <pbutsykin@xxxxxxxxxxxxx> Message-Id: <20170203152321.19739-4-pbutsykin@xxxxxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit 53f09a1076f5efbba7d751a8005e2fcf008606db Author: Pavel Butsykin <pbutsykin@xxxxxxxxxxxxx> Date: Fri Feb 3 18:23:20 2017 +0300 add 'release-ram' migrate capability This feature frees the migrated memory on the source during postcopy-ram migration. In the second step of postcopy-ram migration when the source vm is put on pause we can free unnecessary memory. It will allow, in particular, to start relaxing the memory stress on the source host in a load-balancing scenario. Signed-off-by: Pavel Butsykin <pbutsykin@xxxxxxxxxxxxx> Message-Id: <20170203152321.19739-3-pbutsykin@xxxxxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Manually merged in Pavel's 'migration: madvise error_report fixup!' commit 9eb14766102b7af5c3ab3d64cc85985bdaa544e2 Author: Pavel Butsykin <pbutsykin@xxxxxxxxxxxxx> Date: Fri Feb 3 18:23:19 2017 +0300 migration: add MigrationState arg for ram_save_/compressed_/page() Cosmetic patch. The use of ms variable instead of migrate_get_current() looks nicer, especially when there reuse. Signed-off-by: Pavel Butsykin <pbutsykin@xxxxxxxxxxxxx> Message-Id: <20170203152321.19739-2-pbutsykin@xxxxxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit cee887d96921d291fa72e90c79b5f03113dae86b Author: Amit Shah <amit.shah@xxxxxxxxxx> Date: Fri Feb 3 16:43:53 2017 +0530 MAINTAINERS: update my email address I'm leaving my job at Red Hat, this email address will stop working next week. Update it to one that I will have access to later. Signed-off-by: Amit Shah <amit.shah@xxxxxxxxxx> Message-Id: <1486120433-11628-1-git-send-email-amit.shah@xxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Reviewed-by: Juan Quintela <quintela@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> commit c77a6c8dd7692e5249d5734df0256faad4c8aca2 Author: Amit Shah <amit.shah@xxxxxxxxxx> Date: Fri Feb 3 16:43:36 2017 +0530 migration: remove myself as maintainer I'm switching jobs, and I'm not sure I can continue maintaining migration. Signed-off-by: Amit Shah <amit.shah@xxxxxxxxxx> Message-Id: <1486120416-11566-1-git-send-email-amit.shah@xxxxxxxxxx> Reviewed-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> Reviewed-by: Juan Quintela <quintela@xxxxxxxxxx> Signed-off-by: Dr. David Alan Gilbert <dgilbert@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |