Error when W2016 vm starts.

[wojcik.m]

I get error like this in host log when starting Windows 2016? Is there any option to fix it?

vcpu3 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

 

[fireon]

Do you know that movie? https://forum.proxmox.com/threads/install-windows-2016-server-on-proxmox-ve-video-tutorial.31344/

 

[wojcik.m]

Do you know that movie? https://forum.proxmox.com/threads/install-windows-2016-server-on-proxmox-ve-video-tutorial.31344/

Yes, all is set like in this tutorial. Only cache is set to write back.

 

[fireon]

Strange... and other vm's running normal? Like Windows 2012r2, 2008 or Ubuntu Linux?

 

[wojcik.m]

Strange... and other vm's running normal? Like Windows 2012r2, 2008 or Ubuntu Linux?

The same situation is on two different servers HP DL360 and this new Supermicro common is only proxmox version. I will try tomorrow with windows 2016 standard because this one is Essentials. On this two proxmox are also vm with linux, windows 10, w2008r2 but only when w2016 boots this error appears.

 

[fireon]

Ok. I understand, look likes an problem with special windowsversion. I've running here in Server 2016 Standard (EVAL) with spice. This is my first install, the server is running some weeks. Please post your VM-config from your server 2016. Here is my config for some diff.

bootdisk: scsi0 
cores: 8 
cpuunits: 10000 
description: Windows 2016 Server 
hotplug: disk,network,usb,memory,cpu 
memory: 4096 
name: win16.tux.local
net0: virtio=BE:83:B1:85:C1:FE,bridge=vmbr0 
numa: 1 
onboot: 1 
ostype: win10 
protection: 1 
sata0: none,media=cdrom 
scsi0: SSD-vmdata-KVM:vm-109-disk-1,discard=on,size=32G 
scsihw: virtio-scsi-pci 
smbios1: uuid=6c254cb1-78f2-4d62-8c83-cb2266e49607 
sockets: 1 
vcpus: 8 
vga: qxl

 

[wojcik.m]

Today I've made new instalations of W2012r2 and W2016 essential error still apears only on W2016.

This error appears only in Essentials version of Windows 2016 on W 2016 Standard it didn't shown.

My config.

agent: 1
bootdisk: scsi0
cores: 8
memory: 4096
name: w2016
net0: virtio=DA:C0:D4:56:00:05,bridge=vmbr0
net1: e1000=D6:51:49:70:88:61,bridge=vmbr0,tag=666
numa: 0
ostype: win10
scsi0: local-lvm:vm-100-disk-1,discard=on,size=100G
scsi1: local-lvm:vm-100-disk-2,discard=on,size=1000G
scsihw: virtio-scsi-pci
smbios1: uuid=0c8ca5a2-86c9-4dbd-ada8-646635ccbf38
sockets: 1

 

[fireon]

Can you build your essentials with legacy hardware for test? So IDE disk, 100mbit network...
But for the first test give your server only 1 CPU and one core.

 

[wojcik.m]

Can you build your essentials with legacy hardware for test? So IDE disk, 100mbit network...
But for the first test give your server only 1 CPU and one core.

The same error. System like in every other vm combination starts but I'm not sure if such "red" error don't make any problems in the future in production environment. Test in next week on living network. Hope that this is gov institution so they dont have much to do

 

[fireon]

Why do you use no standardserver 2016? Or better 2012r2, more stable.

 

[wojcik.m]

I did not expect problems and price for <25 users system was optimal for essential version. I will try W2012r2 essentials probably 2016 is downgradable to this version.

 

[spirit]

as workaround, you can try to add

/etc/modprobe.d/kvm.conf
options kvm ignore_msrs=1

 

[omegaman]

I too have this issue.

(Error Message on Console)
(proxmox kernel: kvm [30968]: vcpu0, guest rIP: 0xfffff801803dcda3 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop )

Proxmox 5.1.35 with virtio-0.1.141 drivers (3 guests, 2 x Windows 10 (1709) and 1 x Windows Server Essentials 2016 (1607) ) All windows machines have been patched as of today 01/12/17.

Both Windows 10 machine during bootup dont seem to trigger the above error message, I have narrowed it down to the Server Essentials 2016. From my research it seems at first the issue is related to CPU flags and Windows 2k16 probing the MSRs but I have changed the CPU option under the guest to "HOST" to match the native processor (Xeon E5-2620v4 2.10Ghz on a Supermicro X10DRH-C/i 32Gb RAM one slot RAID 10 Hardware) this doesnt seem to make a difference.

So far the VM 2K16 seems to be stable and seems to be quite fast i dont have any BSOD however I would like to get rid of the issue because at present I cannot be sure if it is a issue that will cause issues down the line, this server and other guests is due to be returned to the client at some point next week but I would prefer fixing this for peace of mind.

 

[uname]

I too have this issue.
(Proxmox 5.1-39)
During Windows Server 2016 Essentials bootup it trigger the Error Messsage on Console.
But what is really strange that when I do a benchmark with CrystalDiskMark in the VM the complete Host crashes!
That is very reassuring but that is another topic ...

 

[tom]

I too have this issue.
(Proxmox 5.1-39)
During Windows Server 2016 Essentials bootup it trigger the Error Messsage on Console.
But what is really strange that when I do a benchmark with CrystalDiskMark in the VM the complete Host crashes!
That is very reassuring but that is another topic ...

Please post the output of:

> pveversion -v

 

[uname]

here it is:

proxmox-ve: 5.1-31 (running kernel: 4.13.13-1-pve)
pve-manager: 5.1-39 (running version: 5.1-39/5fa9d6c1)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.13.13-1-pve: 4.13.13-31
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-22
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-17
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

fresh proxmox install with zfs raid10 on Supermicro X10SLH-F with 4x sata HDs
and a fresh windows server 2016 essentials install (vm configuration like in the proxmox server 2016 video)

thank you!

 

[omegaman]

Here is my infomation;


Last login: Mon Dec 11 21:48:35 2017
root@proxmox:~# pveversion -v
proxmox-ve: 5.1-31 (running kernel: 4.13.13-1-pve)
pve-manager: 5.1-39 (running version: 5.1-39/5fa9d6c1)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.13.13-1-pve: 4.13.13-31
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-22
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-17
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

 

[omegaman]

Please find attached screenshot of the error message I get on the console. during the Host bootup everything is fine, once the proxmox console is running I can confirm that running Windows 10 VM won't cause the error message to appear, however if you run the Windows Server Essentials 2016 Server VM the message appears during "Applying Settings" messages, so this OS must be doing something different compared to the standard Win 10 Pro VM. I also attach a screenshot of my proxmox settings for Server Essentials 2016.

 

[uname]

@omegamen
exactly the same. I don't think that this messages are critical.

can you do a benchmark with CrystalDiskMark in the VM (windows server 2016 essentials)?
of course only if this is a test server ...

 

[omegaman]

Hi,

This i cannot as its a production server and they are using it right now, don't think they would be happy with me lol