Error message: kvm: 32640 cpu0 unhandled rdmsr: 0x345

[cesarpk]

Hi everybody

Please to anybody or PVE team, I have a strange problem:

I have a computer with cpu "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz" (specifications of this processor in: http://ark.intel.com/products/65719/ )
This processor have: 4 cores and 8 Threads (Multi-cores + hyperThreading)

And if i start the KVM VM with CPU type: host ,
i get this error message on the screen of PVE Host: kvm: 32640 cpu0 unhandled rdmsr: 0x345

Re Edit: and syslog message: kvm1 kernel: kvm: 32640: cpu0 unhandled rdmsr: 0x345


But if i start the same KVM VM with CPU type: "Default (qemu64)" , i don't get the error message

I want to know if there is solution to use the VM without processor emulation (faster)

Best regards
Cesar

 

[osobh]

http://forum.proxmox.com/threads/5046-Error-kvm-cpu0-unhandled-wrmsr-amp-unhandled-rdmsr

You also might want to check and see how you are attaching your storage and wether its coming from NFS or not. I have been having the same issue here and there with my NFS attached storage. I've had my proxmox server alive now for 2 years and that message hasn't done anything negative in my environment.

 

[cesarpk]

http://forum.proxmox.com/threads/5046-Error-kvm-cpu0-unhandled-wrmsr-amp-unhandled-rdmsr

You also might want to check and see how you are attaching your storage and wether its coming from NFS or not. I have been having the same issue here and there with my NFS attached storage. I've had my proxmox server alive now for 2 years and that message hasn't done anything negative in my environment.

Thanks osobh, but i only use LVM local storage.

Re Edit: Can osobh or anybody tell me about of the problem and if you can use cpu: Host in production environments with several KVM VMs?
(The error message: kvm: 32640 cpu0 unhandled rdmsr: 0x345)

My PVE version:
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-72
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1

 

[lpallard]

Same problem here on a dual socket Opteron 4334 server running with a SUpermicro H8DCL-iF motherboard. I only use (for now) the local storage created at install..

Have you found the root cause or solution?

 

[Mitya]

AFAIK, this message is harmless if you do not do guest kernel's profiling. MSR 0x345 is IA32_PERF_CAPABILITIES.
See https://bugs.launchpad.net/qemu/+bug/1208540 for workaround.
I have many of these:

 dmesg | grep rdmsr | wc -l
45

but all works fine.

You can safely use cpu: host if your HA cluster have all identical CPUs or you don't have HA at all.