Red Hat Bugzilla – Bug 1097363
qemu ' KVM internal error. Suberror: 1' when query cpu frequently during pxe boot in Intel "Q95xx" host
Last modified: 2015-03-05 03:09:22 EST
Upstream patch at http://permalink.gmane.org/gmane.comp.emulators.qemu/273522 kvm.c and machine.c hunks only.
Fix included in qemu-kvm-1.5.3-76.el7
(In reply to Paolo Bonzini from comment #2) > Upstream patch at > > http://permalink.gmane.org/gmane.comp.emulators.qemu/273522 > > kvm.c and machine.c hunks only. Hi, Paolo How to verify this qemu-kvm bug, since if just test the original scenario, it is only kernel bug as bug 1088784 , with unfixed kernel(and any qemu builds), the original bug can be reproduced. So if to verify the qemu-kvm side (bug 1088784 comment 17), do we need check something, could you help provide some suggestion? Thanks
Hi Qian, you need to test it together with a fixed kernel, as suggested by the "depends on bug 1088784" in this BZ.
Test this bug with kernel-3.10.0-196.el7.x86_64 and qemu-kvm-1.5.3-77.el7.x86_64 steps: 1.# /usr/libexec/qemu-kvm -cpu Penryn -m 4G -smp 4,sockets=1,cores=4,threads=1 -M pc -enable-kvm -device piix3-usb-uhci,id=usb -name rhel7 -nodefaults -nodefconfig -device virtio-balloon-pci,id=balloon0 -vnc :10 -vga std -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio -drive file=test,if=none,media=disk,format=raw,rerror=stop,werror=stop,aio=native,id=scsi-disk0 -device virtio-scsi-pci,id=bus2 -device scsi-hd,bus=bus2.0,drive=scsi-disk0,id=disk0 -netdev tap,id=netdev0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=netdev0,id=vn1,mac=52:54:a0:0b:00:01 -boot menu=on -monitor unix:/tmp/m1,server,nowait -S 2.In host, query vcpu via hmp, # while true; do echo "info cpus" |nc -U /tmp/m1 ; done Result, guest can continue to boot, and did not hit the crash. And test with kernel-3.10.0-196.el7.x86_64 and qemu-kvm-rhev-2.1.2-6.el7.x86_64, can get same result as qemu-kvm-1.5.3-77.el7.x86_64. So this bug is verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0349.html