KVM VMs hanging (kvm: 2727: cpu0 unhandled wrmsr: 0x684 data 0)

hassan123

Member
Jan 24, 2014
1
0
21
Hello,

I've seen similar threads posted but I am pretty sure my issue is different, I keep getting the following errors and my KVM VMs keep hanging or just crashing:

Jan 24 09:43:28 poseidon kernel: __ratelimit: 119 callbacks suppressed
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled rdmsr: 0x345
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x680 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c0 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x681 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c1 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x682 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c2 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x683 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c3 data 0
Jan 24 09:43:28 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x684 data 0
Jan 24 10:04:16 poseidon kernel: __ratelimit: 119 callbacks suppressed
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled rdmsr: 0x345
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x680 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c0 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x681 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c1 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x682 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c2 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x683 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x6c3 data 0
Jan 24 10:04:16 poseidon kernel: kvm: 2727: cpu0 unhandled wrmsr: 0x684 data 0

I'm not sure whats triggering this and I'm looking for some guidance.



pveversion -v:
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Happening to both my KVM VMs that I have on this node, and I use local storage only.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!