Hi,
I have upgraded from Proxmox VE 4.3 to 4.4. via CD iso. After upgrade I have noticed that one VM which is ubuntu 16.04 LTS caused log printouts on host machine every time when it boots.
Dec 14 22:17:39 proxmoxTest kernel: [43732.924523] kvm [18630]: vcpu0 unhandled rdmsr: 0xc0011020
Dec 14 22:17:39 proxmoxTest kernel: [43733.279639] kvm [18630]: vcpu0 unhandled rdmsr: 0xc0011020
Dec 14 22:17:39 proxmoxTest kernel: [43733.373365] kvm [18630]: vcpu1 unhandled rdmsr: 0xc0011020
Dec 14 22:17:53 proxmoxTest kernel: [43746.926629] kvm [18630]: vcpu0 unhandled rdmsr: 0x3a
Dec 14 22:17:53 proxmoxTest kernel: [43746.926729] kvm [18630]: vcpu0 unhandled rdmsr: 0xd90
Dec 14 22:17:53 proxmoxTest kernel: [43746.926793] kvm [18630]: vcpu0 unhandled rdmsr: 0xc0000103
Versions:
ppve-manager/4.4-1/eb2d6f1e (running kernel: 4.4.35-1-pve)
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
PC:
AMD Athlon(tm) 5350 APU with Radeon(tm) R3
8GB DDR3 1600 ram
Asus AM1M-A mainboard
VM settings
boot: c
bootdisk: sata0
cores: 2
cpu: host
memory: 4096
name: testSrv
net0: e1000=59:54:01:8c:5c:59,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
sata0: local:100/vm-100-disk-1.qcow2,cache=directsync,size=40G
scsihw: virtio-scsi-pci
smbios1: uuid=7cff5c5d-bcac-4cce-9547-2ee2475e1551
sockets: 1
I have upgraded from Proxmox VE 4.3 to 4.4. via CD iso. After upgrade I have noticed that one VM which is ubuntu 16.04 LTS caused log printouts on host machine every time when it boots.
Dec 14 22:17:39 proxmoxTest kernel: [43732.924523] kvm [18630]: vcpu0 unhandled rdmsr: 0xc0011020
Dec 14 22:17:39 proxmoxTest kernel: [43733.279639] kvm [18630]: vcpu0 unhandled rdmsr: 0xc0011020
Dec 14 22:17:39 proxmoxTest kernel: [43733.373365] kvm [18630]: vcpu1 unhandled rdmsr: 0xc0011020
Dec 14 22:17:53 proxmoxTest kernel: [43746.926629] kvm [18630]: vcpu0 unhandled rdmsr: 0x3a
Dec 14 22:17:53 proxmoxTest kernel: [43746.926729] kvm [18630]: vcpu0 unhandled rdmsr: 0xd90
Dec 14 22:17:53 proxmoxTest kernel: [43746.926793] kvm [18630]: vcpu0 unhandled rdmsr: 0xc0000103
Versions:
ppve-manager/4.4-1/eb2d6f1e (running kernel: 4.4.35-1-pve)
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
PC:
AMD Athlon(tm) 5350 APU with Radeon(tm) R3
8GB DDR3 1600 ram
Asus AM1M-A mainboard
VM settings
boot: c
bootdisk: sata0
cores: 2
cpu: host
memory: 4096
name: testSrv
net0: e1000=59:54:01:8c:5c:59,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
sata0: local:100/vm-100-disk-1.qcow2,cache=directsync,size=40G
scsihw: virtio-scsi-pci
smbios1: uuid=7cff5c5d-bcac-4cce-9547-2ee2475e1551
sockets: 1
