For what it's worth, still getting the same kind of messages with the
current Saucy (beta) kernel:
[ 42.759017] kvm [1793]: vcpu0 unhandled rdmsr: 0x345
[ 42.791187] kvm [1793]: vcpu0 unhandled wrmsr: 0x680 data 0
[ 42.791211] kvm [1793]: vcpu0 unhandled wrmsr: 0x6c0 data 0
[ 42.791228] kvm [1793]: vcpu0 unhandled wrmsr: 0x681 data 0
[ 42.791245] kvm [1793]: vcpu0 unhandled wrmsr: 0x6c1 data 0
[ 42.791262] kvm [1793]: vcpu0 unhandled wrmsr: 0x682 data 0
[ 42.791279] kvm [1793]: vcpu0 unhandled wrmsr: 0x6c2 data 0
[ 42.791296] kvm [1793]: vcpu0 unhandled wrmsr: 0x683 data 0
[ 42.791312] kvm [1793]: vcpu0 unhandled wrmsr: 0x6c3 data 0
[ 42.791330] kvm [1793]: vcpu0 unhandled wrmsr: 0x684 data 0
[ 42.791347] kvm [1793]: vcpu0 unhandled wrmsr: 0x6c4 data 0
# uname -a
Linux srv1 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
# ps -ef | grep 1793
106 1793 1 6 02:15 ? 00:00:23 qemu-system-x86_64 -machine
accel=kvm:tcg -name vm6 -S -machine pc-i440fx-1.5,accel=kvm,usb=off -cpu
SandyBridge,+erms,+smep,+fsgsbase,+rdrand,+f16c,+osxsave,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
-m 256 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid
0c870de6-930b-c8da-09fd-f7c61879d986 -nographic -no-user-config -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm6.monitor,server,nowait -mon
chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/dev/vm/vm6.img,if=none,id=drive-virtio-disk0,format=raw -device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:4c:27:84,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -
device isa-serial,chardev=charserial0,id=serial0 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
vm is created with the following command line (note the cpu=host
setting):
virt-install \
--disk pool=vm,bus=virtio,size=${SIZE},sparse=false \
-n ${NAME} \
-r ${RAM} --connect qemu:///system \
-l http://${MIRROR}/ubuntu/dists/${RELEASE}/main/installer-amd64/ \
--initrd-inject=/etc/vm/scripts/preseed.cfg \
--nographics \
--autostart \
--virt-type kvm \
--network=bridge:${BRIDGE},model=virtio \
--os-type=linux \
--vcpus=4 \
--cpu host \
--extra-args="auto=true text console=tty0 console=ttyS0,115200n8
interface=eth0 hostname=${NAME} domain=${DOMAIN} netcfg/disable_autoconfig=true
netcfg/get_ipaddress=${IP} netcfg/get_netmask=${NETMASK}
netcfg/get_gateway=${GW} netcfg/get_nameservers=${DNS}
netcfg/confirm_static=true"
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/957957
Title:
kvm: 7767: cpu0 unhandled rdmsr: 0xc0010001
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/957957/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
