Control: tag -1 + moreinfo 29.08.2019 16:36, Stephan Breitrainer wrote: > Package: qemu-system-x86 > Version: 1:2.1+dfsg-12+deb8u11 > Severity: normal > > Dear Maintainer, > > when starting a qemu process, the process terminates suddenly leaving this > error message in /var/log/libvirt/qemu/<machine>.log: > > qemu-system-x86_64: /build/qemu-2.1+dfsg/block.c:3606: bdrv_error_action: > Assertion `error >= 0' failed.
How very useful.. not. Okay. > The qemu command used: > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin > QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name testmachine -S > -machine pc-i440fx-2.1,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp > 2,sockets=2,cores=1,threads=1 -uuid cc300f3e-cdc9-465f-95b3-f208b92ad4ac > -no-user-config -nodefaults -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/testmachine.monitor,server,nowait > -mon > chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot > strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive > file=/data/one/0/322/disk.0,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,discard=unmap,aio=native > -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 > -drive > file=/data/one/0/testmachine/disk.2,format=raw,if=none,id=drive-virtio-disk1,cache=none,discard=unmap,aio=native > -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 > -drive > file=/data/one/0/testmachine/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on > -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 > -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=43 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:ac:10:01:88,bus=pci.0,addr=0x3 > -vnc 0.0.0.0:322 <http://0.0.0.0:322/> -device > cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg > timestamp=on Thank you for providing the qemu command line, it is not often when bug reporters do this, and without it it's usually difficult to say anything about the bug. Ok. Now, I can't say exactly what is happening here, but at least we can assume there's something wrong with your setup. This assert() is in a routine which handles I/O errors in the block layer or qemu. The thing is, some error happened while handling an I/O request from your virtual machine, eg, a read or write to the virtio drive failed, and qemu tried to tell your machine about this error. And we hit a bug on the qemu side somewhere in the error handling path (path which is usually not tested well enough). I suggest you to recreate the images (maybe just copy 'em with qemu-img) and try running your guest again - the error hopefully will just go away. Overall, qemu 2.1 is in oldstable, and the code in there has been changed significantly since then, please try a more recent version. If current version will show this error, we'll try to debug it further. Thanks, /mjt
