Possible KVM bug

Possible KVM bug

[Nick Skeen]

Every time a try and start a kvm-based VM with virt-manager the guest
crashes during boot-up with this message in the host's kernel logger.


[ 6762.680687] device eth0 entered promiscuous mode
[ 6769.287090] kvm: 14513: cpu0 unhandled rdmsr: 0xc001100d
[ 6769.287151] kvm: 14513: cpu0 unhandled rdmsr: 0xc0010112
[ 6769.535786] kvm: 14513: cpu0 unhandled rdmsr: 0xc0010001
[ 6771.588616] qemu-kvm[14515]: segfault at 10 ip 00007f93c7848d0e sp
00007f93bfb21c00 error 4 in qemu-system-x86_64[7f93c7718000+308000]
[ 6771.639525] device eth0 left promiscuous mode

>From the libvirt log this is the command being used to launch the VM:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none
/usr/bin/qemu-kvm -S -M pc-1.0 -cpu
phenom,+3dnowprefetch,+cr8legacy,+extapic,+cmp_legacy,+lahf_lm,+rdtscp,+cx16,+ht,+vme,-monitor
-enable-kvm -m 3072 -smp 1,maxcpus=2,sockets=2,cores=1,threads=1 -name
Debian -uuid 0bd3a8c5-3831-edb6-05bb-a0a018849e69 -nodefconfig
-nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/Debian.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-reboot -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/home/virt/images/Debian.img,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2
-drive file=/home/virt/images/Debian-1.img,if=none,id=drive-virtio-disk1,format=raw,cache=none,aio=native
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1
-drive file=/home/virt/images/Debian-2.img,if=none,id=drive-virtio-disk2,format=raw,cache=none,aio=native
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk2,id=virtio-disk2
-drive file=/home/virt/debian-testing-amd64-netinst.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
-netdev tap,fd=21,id=hostnet0 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fd:d0:3b,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0
-vnc 127.0.0.1:1 -vga cirrus -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7


My system details:
CPU: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55
uname -a output on host: Linux arch 3.4.4-2-ARCH #1 SMP PREEMPT Sun
Jun 24 18:59:47 CEST 2012 x86_64 GNU/Linux
KVM version: QEMU emulator version 1.1.0 (qemu-kvm-1.1.0)

Re: Possible KVM bug

[Avi Kivity]

On 07/14/2012 07:08 AM, Nick Skeen wrote:
> Every time a try and start a kvm-based VM with virt-manager the guest
> crashes during boot-up with this message in the host's kernel logger.
> 
> 
> [ 6762.680687] device eth0 entered promiscuous mode
> [ 6769.287090] kvm: 14513: cpu0 unhandled rdmsr: 0xc001100d
> [ 6769.287151] kvm: 14513: cpu0 unhandled rdmsr: 0xc0010112
> [ 6769.535786] kvm: 14513: cpu0 unhandled rdmsr: 0xc0010001
> [ 6771.588616] qemu-kvm[14515]: segfault at 10 ip 00007f93c7848d0e sp
> 00007f93bfb21c00 error 4 in qemu-system-x86_64[7f93c7718000+308000]
> [ 6771.639525] device eth0 left promiscuous mode
> 

Please enable core dumps and generate a backtrace of the failed qemu-kvm
process.


-- 
error compiling committee.c: too many arguments to function