|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [qemu-mainline baseline-only test] 74978: regressions - FAIL
This run is configured for baseline tests only. flight 74978 qemu-mainline real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/74978/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-credit2 6 xen-install fail REGR. vs. 74969 test-amd64-amd64-qemuu-nested-intel 10 debian-hvm-install fail REGR. vs. 74969 Tests which did not succeed, but are not blocking: test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail like 74969 test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail like 74969 test-armhf-armhf-xl-rtds 12 guest-start fail like 74969 test-armhf-armhf-libvirt 12 guest-start fail like 74969 test-armhf-armhf-xl 12 guest-start fail like 74969 test-amd64-amd64-xl-pvshim 12 guest-start fail like 74969 test-armhf-armhf-xl-midway 12 guest-start fail like 74969 test-armhf-armhf-xl-multivcpu 12 guest-start fail like 74969 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 74969 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 74969 test-armhf-armhf-xl-vhd 10 debian-di-install fail like 74969 test-armhf-armhf-libvirt-raw 10 debian-di-install fail like 74969 test-amd64-amd64-xl-qemuu-ws16-amd64 10 windows-install fail never pass test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-i386-xl-pvshim 12 guest-start fail never pass test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-i386-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail never pass version targeted for testing: qemuu 9277d81f5c2c6f4d0b5e47c8476eb7ee7e5c0beb baseline version: qemuu ff82d3c73ec20d6f40e8bbfafe8ed5110bba5049 Last test of basis 74969 2018-07-14 20:47:52 Z 2 days Testing same since 74978 2018-07-16 16:22:45 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Daniel Henrique Barboza <danielhb413@xxxxxxxxx> Eduardo Otubo <otubo@xxxxxxxxxx> Fam Zheng <famz@xxxxxxxxxx> John Arbuckle <programmingkidx@xxxxxxxxx> John Snow <jsnow@xxxxxxxxxx> Kevin Wolf <kwolf@xxxxxxxxxx> Marc-André Lureau <marcandre.lureau@xxxxxxxxxx> Paolo Bonzini <pbonzini@xxxxxxxxxx> Peter Lieven <pl@xxxxxxx> Peter Maydell <peter.maydell@xxxxxxxxxx> Ville Skyttä <ville.skytta@xxxxxx> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-armhf-armhf-xl fail 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-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-amd64-xl-pvhv2-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-amd64-amd64-xl-qemuu-ws16-amd64 fail test-amd64-i386-xl-qemuu-ws16-amd64 fail test-amd64-amd64-xl-credit2 pass test-armhf-armhf-xl-credit2 fail test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict pass test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict pass test-amd64-i386-freebsd10-i386 pass test-amd64-amd64-xl-qemuu-win10-i386 fail test-amd64-i386-xl-qemuu-win10-i386 fail test-amd64-amd64-qemuu-nested-intel fail test-amd64-amd64-xl-pvhv2-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-armhf-armhf-xl-midway fail test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu fail 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-xl-pvshim fail test-amd64-i386-xl-pvshim fail test-amd64-amd64-pygrub pass test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw fail test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds pass test-armhf-armhf-xl-rtds fail test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-amd64-xl-shadow pass test-amd64-i386-xl-shadow pass test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd fail ------------------------------------------------------------ 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 Push not applicable. ------------------------------------------------------------ commit 9277d81f5c2c6f4d0b5e47c8476eb7ee7e5c0beb Author: Ville Skyttä <ville.skytta@xxxxxx> Date: Tue Jun 12 09:51:50 2018 +0300 docs: Grammar and spelling fixes Signed-off-by: Ville Skyttä <ville.skytta@xxxxxx> Reviewed-by: Peter Maydell <peter.maydell@xxxxxxxxxx> Reviewed-by: Eric Blake <eblake@xxxxxxxxxx> Message-id: 20180612065150.21110-1-ville.skytta@xxxxxx Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 68f1b569dccdf1bf2935d4175fffe84dae6997fc Merge: dc3c89d 8dcd3c9 Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Thu Jul 12 17:37:49 2018 +0100 Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging Block layer patches: - file-posix: Check correct file type (regular file for 'file', character or block device for 'host_device'/'host_cdrom') - scsi-disk: Block Device Characteristics emulation fix - qemu-img: Consider required alignment for sparse area detection - Documentation and test improvements # gpg: Signature made Thu 12 Jul 2018 17:29:17 BST # gpg: using RSA key 7F09B272C88F2FD6 # 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: qemu-img: align result of is_allocated_sectors scsi-disk: Block Device Characteristics emulation fix iotests: add test 226 for file driver types file-posix: specify expected filetypes qemu-img: Document copy offloading implications with -S and -c iotests: nbd: Stop qemu-nbd before remaking image iotests: 153: Fix dead code Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 8dcd3c9b91a300c86e315d7e5427dce1383f7387 Author: Peter Lieven <pl@xxxxxxx> Date: Thu Jul 12 15:00:10 2018 +0200 qemu-img: align result of is_allocated_sectors We currently don't enforce that the sparse segments we detect during convert are aligned. This leads to unnecessary and costly read-modify-write cycles either internally in Qemu or in the background on the storage device as nearly all modern filesystems or hardware have a 4k alignment internally. This patch modifies is_allocated_sectors so that its *pnum result will always end at an alignment boundary. This way all requests will end at an alignment boundary. The start of all requests will also be aligned as long as the results of get_block_status do not lead to an unaligned offset. The number of RMW cycles when converting an example image [1] to a raw device that has 4k sector size is about 4600 4k read requests to perform a total of about 15000 write requests. With this path the additional 4600 read requests are eliminated while the number of total write requests stays constant. [1] https://cloud-images.ubuntu.com/releases/16.04/release/ubuntu-16.04-server-cloudimg-amd64-disk1.vmdk Signed-off-by: Peter Lieven <pl@xxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 740842c9656cd5dbc9ccf2ea0c3a74f0ba35144a Author: Daniel Henrique Barboza <danielhb413@xxxxxxxxx> Date: Wed Jul 11 17:58:13 2018 -0300 scsi-disk: Block Device Characteristics emulation fix The current BDC VPD page (page 0xb1) is too short. This can be seen running sg_utils: $ sg_vpd --page=bdc /dev/sda Block device characteristics VPD page (SBC): Block device characteristics VPD page length too short=8 By the SCSI spec, the expected size of the SBC page is 0x40. There is no telling how the guest will behave with a shorter message - it can ignore it, or worse, make (wrong) assumptions. This patch fixes the emulation by setting the size to 0x40. This is the output of the previous sg_vpd command after applying it: $ sg_vpd --page=bdc /dev/sda -v inquiry cdb: 12 01 b1 00 fc 00 Block device characteristics VPD page (SBC): [PQual=0 Peripheral device type: disk] Medium rotation rate is not reported Product type: Not specified WABEREQ=0 WACEREQ=0 Nominal form factor not reported FUAB=0 VBULS=0 To improve readability, this patch also adds the VBULS value explictly and add comments on the existing fields we're setting. Signed-off-by: Daniel Henrique Barboza <danielhb413@xxxxxxxxx> Acked-by: Paolo Bonzini <pbonzini@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 2d4cb49ddaa219ed3f5a985ecf8b188aeb2b3d6b Author: John Snow <jsnow@xxxxxxxxxx> Date: Tue Jul 10 13:00:41 2018 -0400 iotests: add test 226 for file driver types Test that we're rejecting what we ought to for file, host_driver and host_cdrom drivers. Test that we're seeing the deprecated message for block and chardevs on the file driver. Signed-off-by: John Snow <jsnow@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 230ff73904e72dde2d7718c2da407786a1c72e57 Author: John Snow <jsnow@xxxxxxxxxx> Date: Tue Jul 10 13:00:40 2018 -0400 file-posix: specify expected filetypes Adjust each caller of raw_open_common to specify if they are expecting host and character devices or not. Tighten expectations of file types upon open in the common code and refuse types that are not expected. This has two effects: (1) Character and block devices are now considered deprecated for the 'file' driver, which expects only S_IFREG, and (2) no file-posix driver (file, host_cdrom, or host_device) can open directories now. I don't think there's a legitimate reason to open directories as if they were files. This prevents QEMU from opening and attempting to probe a directory inode, which can break in exciting ways. One of those ways is lseek on ext4/xfs, which will return 0x7fffffffffffffff as the file size instead of EISDIR. This can coax QEMU into responding with a confusing "file too big" instead of "Hey, that's not a file". See: https://bugs.launchpad.net/qemu/+bug/1739304/ Signed-off-by: John Snow <jsnow@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit eb461485f4558e362fab905735b50987505bca44 Author: Fam Zheng <famz@xxxxxxxxxx> Date: Wed Jul 11 09:22:27 2018 +0800 qemu-img: Document copy offloading implications with -S and -c Explicitly enabling zero detection or compression suppresses copy offloading during convert. Document it. Suggested-by: Kevin Wolf <kwolf@xxxxxxxxxx> Signed-off-by: Fam Zheng <famz@xxxxxxxxxx> Reviewed-by: Stefan Hajnoczi <stefanha@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 2f9d4083f7fdafe82138e983a24ef30b81b029d7 Author: Fam Zheng <famz@xxxxxxxxxx> Date: Wed Jul 11 14:40:46 2018 +0800 iotests: nbd: Stop qemu-nbd before remaking image 197 is one example where _make_test_img is used twice without stopping the NBD server in between. An error will occur like this: @@ -26,9 +26,13 @@ === Partial final cluster === +qemu-img: TEST_DIR/t.IMGFMT: Failed to get "resize" lock +Is another process using the image? Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1024 +Failed to find an available port: Address already in use read 1024/1024 bytes at offset 0 Patch _make_test_img to stop the old qemu-nbd before starting a new one, which fixes this problem, and similarly 215. Signed-off-by: Fam Zheng <famz@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit 0e1a582750269d3dde0481ca034b08a5784e430c Author: Fam Zheng <famz@xxxxxxxxxx> Date: Wed Jul 11 15:05:19 2018 +0800 iotests: 153: Fix dead code This step was left behind my mistake. As suggested by the echoed text, the intention was to test two devices with the same image, with different options. The behavior should be the same as two QEMU processes. Complete it. Signed-off-by: Fam Zheng <famz@xxxxxxxxxx> Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx> commit dc3c89d612252fc461a65f54885a1fe108e9ec05 Author: John Arbuckle <programmingkidx@xxxxxxxxx> Date: Mon Jul 9 11:02:35 2018 -0400 ui/cocoa.m: replace scrollingDeltaY with deltaY The NSEvent class method scrollingDeltaY is available for Mac OS 10.7 and newer. Since QEMU supports Mac OS 10.5 and up, we need to be using a method that is available on these version of Mac OS X. The deltaY method is a method that does almost the same thing as scrollingDeltaY and is available on Mac OS 10.5 and up. So we can replace scrollingDeltaY with deltaY. We only check deltaY's value if it is not zero because zero means that the scrolling increment was sufficiently fine that it was only reported in scrollingDeltaY, or that the scrolling was horizontal. Signed-off-by: John Arbuckle <programmingkidx@xxxxxxxxx> Message-id: 20180709150235.7573-1-programmingkidx@xxxxxxxxx Reviewed-by: Peter Maydell <peter.maydell@xxxxxxxxxx> [PMM: tweak commit message and comment a little] Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 7fdf16e1148a6133c5dee38140d75b0c9b96fa00 Merge: ff82d3c 056de1e Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Thu Jul 12 14:59:28 2018 +0100 Merge remote-tracking branch 'remotes/otubo/tags/pull-seccomp-20180712' into staging pull-seccomp-20180712 # gpg: Signature made Thu 12 Jul 2018 13:55:34 BST # gpg: using RSA key DF32E7C0F0FFF9A2 # gpg: Good signature from "Eduardo Otubo (Senior Software Engineer) <otubo@xxxxxxxxxx>" # Primary key fingerprint: D67E 1B50 9374 86B4 0723 DBAB DF32 E7C0 F0FF F9A2 * remotes/otubo/tags/pull-seccomp-20180712: seccomp: allow sched_setscheduler() with SCHED_IDLE policy Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 056de1e894155fbb99e7b43c1c4382d4920cf437 Author: Marc-André Lureau <marcandre.lureau@xxxxxxxxxx> Date: Tue Jul 10 16:55:57 2018 +0200 seccomp: allow sched_setscheduler() with SCHED_IDLE policy Current and upcoming mesa releases rely on a shader disk cash. It uses a thread job queue with low priority, set with sched_setscheduler(SCHED_IDLE). However, that syscall is rejected by the "resourcecontrol" seccomp qemu filter. Since it should be safe to allow lowering thread priority, let's allow scheduling thread to idle policy. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1594456 Signed-off-by: Marc-André Lureau <marcandre.lureau@xxxxxxxxxx> Acked-by: Eduardo Otubo <otubo@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |