|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [qemu-mainline test] 107277: regressions - trouble: blocked/broken/fail/pass
flight 107277 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/107277/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-arndale 2 hosts-allocate broken REGR. vs. 107219 test-amd64-i386-xl-raw 18 guest-start/debian.repeat fail REGR. vs. 107219 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-libvirt 13 saverestore-support-check fail like 107219 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 107219 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 107219 test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail like 107219 test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail like 107219 test-amd64-amd64-xl-rtds 9 debian-install fail like 107219 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 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 test-amd64-i386-libvirt 12 migrate-support-check 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-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass build-arm64-pvops 5 kernel-build fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 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-libvirt 12 migrate-support-check 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-xl-cubietruck 12 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 13 saverestore-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-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-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass test-armhf-armhf-libvirt-xsm 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 version targeted for testing: qemuu 5daf9b3025baef10ee7b77daa003d5696b58d5dc baseline version: qemuu 1fde6ee885d3e778acb326cab9f7037939839537 Last test of basis 107219 2017-04-05 15:36:01 Z 3 days Failing since 107250 2017-04-06 17:17:05 Z 2 days 2 attempts Testing same since 107277 2017-04-07 19:47:31 Z 1 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Alex Williamson <alex.williamson@xxxxxxxxxx> Fam Zheng <famz@xxxxxxxxxx> Jeff Cody <jcody@xxxxxxxxxx> Kashyap Chamarthy <kchamart@xxxxxxxxxx> Kevin Wolf <kwolf@xxxxxxxxxx> Max Reitz <mreitz@xxxxxxxxxx> Paolo Bonzini <pbonzini@xxxxxxxxxx> Peter Maydell <peter.maydell@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-arm64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-arm64-pvops fail 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 pass 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 pass 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-armhf-armhf-xl-arndale broken test-amd64-amd64-xl-credit2 pass test-arm64-arm64-xl-credit2 blocked test-armhf-armhf-xl-credit2 pass test-armhf-armhf-xl-cubietruck pass test-amd64-i386-freebsd10-i386 pass test-amd64-amd64-qemuu-nested-intel pass test-amd64-amd64-xl-pvh-intel pass 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-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 pass 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 fail 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 pass 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.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary broken-step test-armhf-armhf-xl-arndale hosts-allocate Not pushing. ------------------------------------------------------------ commit 5daf9b3025baef10ee7b77daa003d5696b58d5dc Merge: 5fe2339 19dd29e Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Fri Apr 7 15:23:48 2017 +0100 Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging Block layer fixes for 2.9.0-rc4 # gpg: Signature made Fri 07 Apr 2017 13:44:17 BST # gpg: using RSA key 0x7F09B272C88F2FD6 # gpg: Good signature from "Kevin Wolf <kwolf@xxxxxxxxxx>" # Primary key fingerprint: DC3D EB15 9A9A F95D 3D74 56FE 7F09 B272 C88F 2FD6 * remotes/kevin/tags/for-upstream: mirror: Fix aio context of mirror_top_bs block: Assert attached child node has right aio context block: Fix unpaired aio_disable_external in external snapshot block: Don't check permissions for copy on read qemu-img: img_create does not support image-opts, fix docs iotests: Add mirror tests for orphaned source block/mirror: Fix use-after-free commit: Set commit_top_bs->total_sectors commit: Set commit_top_bs->aio_context block: Ignore guest dev permissions during incoming migration Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 19dd29e8a77cd820515de5289f566508e0ed4926 Author: Fam Zheng <famz@xxxxxxxxxx> Date: Fri Apr 7 14:54:11 2017 +0800 mirror: Fix aio context of mirror_top_bs It should be moved to the same context as source, before inserting to the graph. Reviewed-by: Eric Blake <eblake@xxxxxxxxxx> Reviewed-by: Kevin Wolf <kwolf@xxxxxxxxxx> Signed-off-by: Fam Zheng <famz@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit bb2614e991d88166fccf4a26c7180ee39f39a48d Author: Fam Zheng <famz@xxxxxxxxxx> Date: Fri Apr 7 14:54:10 2017 +0800 block: Assert attached child node has right aio context Suggested-by: Kevin Wolf <kwolf@xxxxxxxxxx> Signed-off-by: Fam Zheng <famz@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit c26a5ab71338a53340257233bd172bbe22c06b16 Author: Fam Zheng <famz@xxxxxxxxxx> Date: Fri Apr 7 14:54:09 2017 +0800 block: Fix unpaired aio_disable_external in external snapshot bdrv_replace_child_noperm tries to hand over the quiesce_counter state from old bs to the new one, but if they are not on the same aio context this causes unbalance. Fix this by setting the correct aio context before calling bdrv_append(). Reported-by: Ed Swierk <eswierk@xxxxxxxxxxxxxxxxxx> Reviewed-by: Eric Blake <eblake@xxxxxxxxxx> Signed-off-by: Fam Zheng <famz@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 1bf03e66fd03af46ff0f98dd04b6e28f432ac1e3 Author: Kevin Wolf <kwolf@xxxxxxxxxx> Date: Fri Apr 7 12:29:05 2017 +0200 block: Don't check permissions for copy on read The assertion is currently failing. We can't require callers to have write permissions when all they are doing is a read, so comment it out. Add a FIXME comment in the code so that the check is re-enabled when copy on read is refactored into its own filter driver. Reported-by: Richard W.M. Jones <rjones@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> Reviewed-by: Richard W.M. Jones <rjones@xxxxxxxxxx> commit 89aa0465b9135d70682420918b28b6e38a0f6322 Author: Jeff Cody <jcody@xxxxxxxxxx> Date: Thu Apr 6 13:45:42 2017 -0400 qemu-img: img_create does not support image-opts, fix docs The documentation and help for qemu-img claims that 'qemu-img create' will take the '--image-opts' argument. This is not true, so this patch removes those claims. Signed-off-by: Jeff Cody <jcody@xxxxxxxxxx> Reviewed-by: Eric Blake <eblake@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 5694923ad1c60a86383244793663c0715bd88e83 Author: Max Reitz <mreitz@xxxxxxxxxx> Date: Mon Apr 3 19:51:50 2017 +0200 iotests: Add mirror tests for orphaned source Signed-off-by: Max Reitz <mreitz@xxxxxxxxxx> Reviewed-by: John Snow <jsnow@xxxxxxxxxx> Reviewed-by: Eric Blake <eblake@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 7a25fcd056ddd34ee7abc906c957d252e2889461 Author: Max Reitz <mreitz@xxxxxxxxxx> Date: Mon Apr 3 19:51:49 2017 +0200 block/mirror: Fix use-after-free If @bs does not have any parents, the only reference to @mirror_top_bs will be held by the BlockJob object after the bdrv_unref() following block_job_create(). However, if block_job_create() fails, this reference will not exist and @mirror_top_bs will have been deleted when we goto fail. The issue comes back at all later entries to the fail label: We delete the BlockJob object before rolling back our changes to the node graph. This means that we will delete @mirror_top_bs in the process. All in all, whenever @bs does not have any parents and we go down the fail path we will dereference @mirror_top_bs after it has been deleted. Fix this by invoking bdrv_unref() only when block_job_create() was successful and by bdrv_ref()'ing @mirror_top_bs in the fail path before deleting the BlockJob object. Finally, bdrv_unref() it at the end of the fail path after we actually no longer need it. Signed-off-by: Max Reitz <mreitz@xxxxxxxxxx> Reviewed-by: John Snow <jsnow@xxxxxxxxxx> Reviewed-by: Philippe Mathieu-Daudé <f4bug@xxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 0d0676a1040d34339731a4e26a9b39b78c8a1fdf Author: Kevin Wolf <kwolf@xxxxxxxxxx> Date: Thu Apr 6 19:07:14 2017 +0200 commit: Set commit_top_bs->total_sectors Like in the mirror filter driver, we also need to set the image size for the commit filter driver. This is less likely to be a problem in practice than for the mirror because we're not at the active layer here, but attaching new parents to a node in the middle of the chain is possible, so the size needs to be correct anyway. Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> Reviewed-by: Eric Blake <eblake@xxxxxxxxxx> Reviewed-by: Fam Zheng <famz@xxxxxxxxxx> commit 02be4aeb9343d9a4993b1de6cebe6280e82d7254 Author: Kevin Wolf <kwolf@xxxxxxxxxx> Date: Thu Apr 6 19:05:07 2017 +0200 commit: Set commit_top_bs->aio_context The filter driver that is inserted by the commit job needs to use the same AioContext as its parent and child nodes. Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> Reviewed-by: Eric Blake <eblake@xxxxxxxxxx> Reviewed-by: Fam Zheng <famz@xxxxxxxxxx> commit d35ff5e6b3aa3a706b0aa3bcf11400fac945b67a Author: Kevin Wolf <kwolf@xxxxxxxxxx> Date: Tue Apr 4 17:29:03 2017 +0200 block: Ignore guest dev permissions during incoming migration Usually guest devices don't like other writers to the same image, so they use blk_set_perm() to prevent this from happening. In the migration phase before the VM is actually running, though, they don't have a problem with writes to the image. On the other hand, storage migration needs to be able to write to the image in this phase, so the restrictive blk_set_perm() call of qdev devices breaks it. This patch flags all BlockBackends with a qdev device as blk->disable_perm during incoming migration, which means that the requested permissions are stored in the BlockBackend, but not actually applied to its root node yet. Once migration has finished and the VM should be resumed, the permissions are applied. If they cannot be applied (e.g. because the NBD server used for block migration hasn't been shut down), resuming the VM fails. Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> Tested-by: Kashyap Chamarthy <kchamart@xxxxxxxxxx> commit 5fe2339e6b09da7d6f48b9bef0f1a7360392b489 Merge: 54d6899 8f419c5 Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Fri Apr 7 10:29:56 2017 +0100 Merge remote-tracking branch 'remotes/awilliam/tags/vfio-updates-20170406.0' into staging VFIO fixes 2017-04-06 - Extra test for NVIDIA BAR5 quirk to avoid segfault (Alex Williamson) # gpg: Signature made Thu 06 Apr 2017 23:05:53 BST # gpg: using RSA key 0x239B9B6E3BB08B22 # gpg: Good signature from "Alex Williamson <alex.williamson@xxxxxxxxxx>" # gpg: aka "Alex Williamson <alex@xxxxxxxxxxx>" # gpg: aka "Alex Williamson <alwillia@xxxxxxxxxx>" # gpg: aka "Alex Williamson <alex.l.williamson@xxxxxxxxx>" # Primary key fingerprint: 42F6 C04E 540B D1A9 9E7B 8A90 239B 9B6E 3BB0 8B22 * remotes/awilliam/tags/vfio-updates-20170406.0: vfio/pci-quirks: Exclude non-ioport BAR from NVIDIA quirk Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 8f419c5b43b988df4ef11315aeb8524e50c99687 Author: Alex Williamson <alex.williamson@xxxxxxxxxx> Date: Thu Apr 6 16:03:26 2017 -0600 vfio/pci-quirks: Exclude non-ioport BAR from NVIDIA quirk The NVIDIA BAR5 quirk is targeting an ioport BAR. Some older devices have a BAR5 which is not ioport and can induce a segfault here. Test the BAR type to skip these devices. Link: https://bugs.launchpad.net/qemu/+bug/1678466 Signed-off-by: Alex Williamson <alex.williamson@xxxxxxxxxx> commit 54d689988c847271d87b3eb113712147129fb811 Merge: 1fde6ee 8c9f42f Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Thu Apr 6 09:27:49 2017 +0100 Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging * TCO watchdog fix # gpg: Signature made Wed 05 Apr 2017 16:24:52 BST # gpg: using RSA key 0xBFFBD25F78C7AE83 # gpg: Good signature from "Paolo Bonzini <bonzini@xxxxxxx>" # gpg: aka "Paolo Bonzini <pbonzini@xxxxxxxxxx>" # Primary key fingerprint: 46F5 9FBD 57D6 12E7 BFD4 E2F7 7E15 100C CD36 69B1 # Subkey fingerprint: F133 3857 4B66 2389 866C 7682 BFFB D25F 78C7 AE83 * remotes/bonzini/tags/for-upstream: tco: do not generate an NMI Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 8c9f42f3cf3598e8bb612b3f81cd12632efd3ca4 Author: Paolo Bonzini <pbonzini@xxxxxxxxxx> Date: Wed Apr 5 10:11:36 2017 +0200 tco: do not generate an NMI This behavior is not indicated in the datasheet and can confuse the OS. The TCO can trap NMIs from SERR# or IOCHK# and convert them to SMIs; but any other TCO event is either delivered as an SMI or completely disabled. Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |