Error when W2016 vm starts.

its odd as the VM had the "HOST" set for the CPU therefore its my understanding that the VM should be able to see all of the CPUs Flags etc....?
 
the Kernel update via the Test repository has fixed the the BSOD issue I was facing when the backup completed, wasnt aware of your test killing the VM so would rather avoid until proxmox has something further to say. If they fix my issue i will get my client to get the support package from them!
 
The Benchmark kills the complete proxmox host not only the VM. That is really crazy ...
 
Yeah thats savage! i would say list your Host and VM settings and maybe the hardware its sitting on, how have you got your disk(s) setup single? RAID?
 
Hey Guys!

I googled your problem and it seems that it is a common problem you are not alone with that. It's not a solution but a simple workaround. Here you got a few infos I found.
Code: 
http://wiki.stoney-cloud.org/wiki/Workaround_unhandled_rdmsr/wrmsr
https://forum.level1techs.com/t/qemu-guest-reboot-on-game-start/97342
https://gist.github.com/jorritfolmer/d01194a00f440ad257bd56d51baddc2d
 
Hi Thanks for that, the ignore msg feature is already in the parameters directory but doesnt make a difference still get the code on console.
 
I recommend the github way with the modprobe.d configuration.
Code: 
nano /etc/modprobe.d/kvm.conf
# Win2016 bsod install workaround
options kvm ignore_msrs=1
Can you reboot it then at night and look for it again?
 
Hi Oliver,

I have tried that also, message still appears??? i was starting to wonder if it was BIOS related?
 
Which hardware do you use? Is your Bios up to date? Have you installed all drivers for your hardware?
 
Hello,
today I made a new Proxmox 5.1 installation, on a Dell server T440:

proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.13-2-pve: 4.13.13-32
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-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
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-18
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

After that I've installed a Windows server 2016 Essential following this best pratics:

agent: 1
boot: cdn
bootdisk: scsi0
cores: 4
ide2: none,media=cdrom
memory: 20480
name: Win2016DOM
net0: virtio=0E:24:BD:6C:10:2F,bridge=vmbr0
numa: 0
ostype: win10
scsi0: DATA2TB:vm-100-disk-1,discard=on,size=80G
scsihw: virtio-scsi-pci
smbios1: uuid=533ea7fb-60c8-4749-93c6-090fe1273dcc
sockets: 1


Since then my Proxmox start to log the following message:
vcpu0, guest rIP: 0xfffff801dbdddc53 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

I have applied the suggested workoround:
/etc/modprobe.d/kvm.conf
options kvm ignore_msrs=1

But it doesn't fix the message.
______________________________________________________

I am wondering if this issue has been resolved, since I didnt' find any resolution.
any help or suggestion will be appreciated
thanks a million
David
 
Does anyone know if Server 2016 Essentials is part of the Windows Evaluations download? I'm going to try and replicate this on a test system.

[EDIT]
Yes Server 2016 essentials is part of free Windows evaluations. Downloading now, will report back..
 
Last edited:
I also confirm similar message when running W2k16 Essentials on a test system (Intel Core2Duo E8400) with latest 4.13.x pve-test repository/updates as of 3/17/2018

#dmesg -T
kvm [2313]: vcpu0, guest rIP: 0xfffff8012397ac53 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop

Tried changing OS option to 8/2012, same message. Tried using latest 4.15.3-1-pve kernel with OS option 8/2012 and 10/2016, same message.
Other than that message, VM starts and works fine AFAIK.
 
This is still happening with:
Code: 
Linux saito 4.15.17-2-pve #1 SMP PVE 4.15.17-10 (Tue, 22 May 2018 11:15:44 +0200) x86_64 GNU/Linux
 
Anyone found a fix for this?
Code: 
Mar  2 17:00:35 proxmox02 kernel: [  796.980214] kvm_set_msr_common: 60123 callbacks suppressed
Mar  2 17:00:35 proxmox02 kernel: [  796.980215] kvm [2077]: vcpu0, guest rIP: 0xfffff8020c3f5fc2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
 
You must log in or register to reply here.
Top Bottom