Re: [Qemu-block] QEMU v2.12.0-rc1 iotest failures

[Vladimir Sementsov-Ogievskiy]

30.03.2018 15:22, Eric Blake wrote:

On 03/29/2018 07:18 PM, John Snow wrote:

Collecting the remaining failures that I know about for sake of easy
tracking on the list. I think Max has been having troubles with iotest
169 as well, but I haven't reproduced the failure myself. I do
occasionally see a locking failure on 153, but it appears to be
relatively rare.




051, 186: Related to culling SCSI options. Do we remove the tests?


A patch for this one is pending:
https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06086.html


185: Being handled by QingFeng Hao
205: Can't create images for bochs/cloop.
208: Can't create images for bochs/cloop, and seems to be mismanaging 
LUKS?







# luks

Failures: 208

commit 44a8174e0a2919693dc28f19c3ce8eef6d4ac2c3
Author: Stefan Hajnoczi 
Date:   Mon Mar 12 16:04:39 2018 -0500

 iotests: add 208 nbd-server + blockdev-snapshot-sync test case


qemu-system-x86_64: -drive
if=none,id=drive0,file=/home/bos/jhuston/src/qemu/bin/git/tests/qemu-iotests/scratch/9125-disk.img,format=luks,cache=writeback,node-name=drive0-node,key-secret=keysec0: 


Volume is not in LUKS format


Not sure if this test can easily be updated to support luks, or if it 
should just blacklist it




let me try :)
http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg07439.html

--
Best regards,
Vladimir

Re: [Qemu-block] QEMU v2.12.0-rc1 iotest failures

[Eric Blake]

On 03/29/2018 07:18 PM, John Snow wrote:

Collecting the remaining failures that I know about for sake of easy
tracking on the list. I think Max has been having troubles with iotest
169 as well, but I haven't reproduced the failure myself. I do
occasionally see a locking failure on 153, but it appears to be
relatively rare.




051, 186: Related to culling SCSI options. Do we remove the tests?


A patch for this one is pending:
https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06086.html


185: Being handled by QingFeng Hao
205: Can't create images for bochs/cloop.
208: Can't create images for bochs/cloop, and seems to be mismanaging LUKS?






# luks

Failures: 208

commit 44a8174e0a2919693dc28f19c3ce8eef6d4ac2c3
Author: Stefan Hajnoczi 
Date:   Mon Mar 12 16:04:39 2018 -0500

 iotests: add 208 nbd-server + blockdev-snapshot-sync test case


qemu-system-x86_64: -drive
if=none,id=drive0,file=/home/bos/jhuston/src/qemu/bin/git/tests/qemu-iotests/scratch/9125-disk.img,format=luks,cache=writeback,node-name=drive0-node,key-secret=keysec0:
Volume is not in LUKS format


Not sure if this test can easily be updated to support luks, or if it 
should just blacklist it


--
Eric Blake, Principal Software Engineer
Red Hat, Inc.   +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

[Qemu-block] QEMU v2.12.0-rc1 iotest failures

[John Snow]

Collecting the remaining failures that I know about for sake of easy
tracking on the list. I think Max has been having troubles with iotest
169 as well, but I haven't reproduced the failure myself. I do
occasionally see a locking failure on 153, but it appears to be
relatively rare.




051, 186: Related to culling SCSI options. Do we remove the tests?
185: Being handled by QingFeng Hao
205: Can't create images for bochs/cloop.
208: Can't create images for bochs/cloop, and seems to be mismanaging LUKS?



# raw, parallels, qed, vdi, vpc, vhdx, vmdk, qcow

none.

# bochs

Failures: 205 208

205: 2dadedce2b2fbdfdce1de8f108a3d67c2241df87 (checkin for 205)
208: 44a8174e0a2919693dc28f19c3ce8eef6d4ac2c3 (checkin for 208)

qemu-system-x86_64: -drive
if=none,id=drive0,file=/home/bos/jhuston/src/qemu/bin/git/tests/qemu-iotests/scratch/9633-disk.img,format=bochs,cache=writeback,node-name=drive0-node:
Could not open
'/home/bos/jhuston/src/qemu/bin/git/tests/qemu-iotests/scratch/9633-disk.img':
No such file or directory

because of:

qemu-img: foo.img: Format driver 'bochs' does not support image creation


# cloop

Failures: 205 208

205: 2dadedce2b2fbdfdce1de8f108a3d67c2241df87 (checkin for 205)
208: 44a8174e0a2919693dc28f19c3ce8eef6d4ac2c3 (checkin for 208)

Same story:

qemu-img: foo.img: Format driver 'cloop' does not support image creation


# qcow2

Failures: 051 185 186

051, 186:

commit 1454509726719e0933c800fad00d6999752688ea
Author: Thomas Huth 
Date:   Tue Feb 20 11:42:37 2018 +0100

scsi: Remove automatic creation of SCSI controllers with -drive if=scsi


185:

4486e89c219c0d1b9bd8dfa0b1dd5b0d51ff2268 is the first bad commit
commit 4486e89c219c0d1b9bd8dfa0b1dd5b0d51ff2268
Author: Stefan Hajnoczi 
Date:   Wed Mar 7 14:42:05 2018 +

vl: introduce vm_shutdown()

# luks

Failures: 208

commit 44a8174e0a2919693dc28f19c3ce8eef6d4ac2c3
Author: Stefan Hajnoczi 
Date:   Mon Mar 12 16:04:39 2018 -0500

iotests: add 208 nbd-server + blockdev-snapshot-sync test case


qemu-system-x86_64: -drive
if=none,id=drive0,file=/home/bos/jhuston/src/qemu/bin/git/tests/qemu-iotests/scratch/9125-disk.img,format=luks,cache=writeback,node-name=drive0-node,key-secret=keysec0:
Volume is not in LUKS format