Recent content by omegaman

Hi Oliver, I have tried that also, message still appears??? i was starting to wonder if it was BIOS related?

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.

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?

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!

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....?

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

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...

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...

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) )...