x86: 0.934
i386: 0.862
KVM: 0.826
graphic: 0.808
vnc: 0.762
device: 0.761
hypervisor: 0.747
virtual: 0.737
network: 0.710
performance: 0.703
debug: 0.681
architecture: 0.645
mistranslation: 0.620
kernel: 0.608
PID: 0.608
files: 0.592
semantic: 0.580
user-level: 0.574
ppc: 0.557
register: 0.519
socket: 0.514
VMM: 0.511
peripherals: 0.502
permissions: 0.490
assembly: 0.471
risc-v: 0.451
boot: 0.429
TCG: 0.415
arm: 0.378

Lockup with vhost network

After using Qemu in this configuration successfully for quite a while, I changed two things:
- moved the VM from a 8-core 4GHz host to a slower 2-core 1.6 Ghz machine
- upgraded qemu from 2.1 to 2.5

and almost immediately (in a couple hours) got hit with a vhost-related lockup.

QEMU command line is:

qemu-system-x86_64 -enable-kvm -daemonize -monitor unix:./monitor,server,nowait -cpu host -M q35 -balloon virtio -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd -drive if=none,id=hd,cache=writeback,aio=native,format=raw,file=xxxx.img,discard=unmap,detect-zeroes=unmap -device virtio-net-pci,netdev=net0,mac=xxxx -netdev tap,vhost=on,id=net0,script=xxxx.sh -usbdevice tablet -smp 2 -m 512 -vnc xxxx:yz

VM was running fine, except no network traffic was passed from/to it. Shutting down the VM, it hung at "Will now halt." The QEMU process was unkillable, so the only choice was to sysrq-b the entire box.

dmesg with sysrq-w attached.



The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.

[Expired for QEMU because there has been no activity for 60 days.]