Hi,
I just tried to upgrade my kvm (from 79) to the new 85. I'm using qemu-kvm-
devel with the kvm-modules (and kernel-includes) that came with 2.6.29.1.
Qemu-blockdevices and virtio-net work well. But virtio blockdevices are not
accessible from within the guest system. Neither can the BIOS boot from them
("Boot failed: could not read the boot disk") nor can the guest-kernel
(2.6.29.1 too) see them.
I am (or better libvirt is) starting the guest like this:
/usr/bin/qemu-kvm -S -M pc -m 1024 -smp 1 -name test \
-uuid 283d1332-c234-9f28-24cf-8bbcc17b44c1 -monitor pty \
-pidfile /var/run/libvirt/qemu//test.pid -boot c \
-drive file=/dev/VolGroup00/testboot,if=ide,index=0 \
-drive file=/dev/VolGroup00/testvirt,if=virtio,index=1 \
-net nic,macaddr=54:52:00:7c:a5:89,vlan=0,model=virtio \
-net tap,fd=17,script=,vlan=0,ifname=vnet0 \
-serial pty -parallel none -usb -vnc 127.0.0.1:0
When booting the guest I get these messages in the host log, but don't know if
they are related:
kernel: kvm: 3082: cpu0 unhandled wrmsr: 0xc0010117 data 0
kernel: kvm: 3082: cpu0 unhandled rdmsr: 0xc0010117
kernel: kvm: 3082: cpu0 unhandled rdmsr: 0xc0010117
They show up when not using virtio-blk too.
Any ideas?
Kind regards,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
