windows 10 vm brakes when setting cpu host

[liebero3]

Hi all,

I try to install a win10 vm, but no matter what, setting cpu to host doesn't throws a Windows bluescreen right after boot.

Its a ryzen7 1800 and x370 gaming 5 motherboard from gigabyte.

I used to have it runnig some time ago, but right now, I'm lost. Anyone any ideas, what could be wrong?

 

[dylanw]

Does the VM work if you set another cpu type?
Does the bluescreen display any helpful/usable information?
Can you post the VM's config (cat /etc/pve/qemu-server/<VMID>.conf)?

 

[liebero3]

Hi,

1. The vm works fine, if I just use the default kvm64.
2. The Bluescreen is just the "something went wrong"-thing from microsoft.
3. here is my (actual...i tried already a few different ones) config:

agent: 1
balloon: 4096
bios: ovmf
boot: order=virtio0;ide2;net0
cores: 10
efidisk0: local-lvm:vm-104-disk-1,size=4M
ide0: local:iso/virtio-win-0.1.190.iso,media=cdrom,size=489986K
ide2: local:iso/Windows.iso,media=cdrom
machine: q35
memory: 10240
name: windows10
net0: virtio=9A:B3:BFC:14:9B,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=173290c2-811c-457f-a2c1-4c1edbb0ae1b
sockets: 1
vga: std
virtio0: local-lvm:vm-104-disk-0,cache=writeback,discard=on,size=100G
vmgenid: 1167ed84-07f4-4bd1-8ca5-4eeb563b6c61

if I add cpu: host it stops working.

My plan is passing through the gpu.

Thanks in advance!

 

[dylanw]

What version of Proxmox VE are you running (pveversion -v?
Does the bluescreen appear on the initial boot or after installation?
Does Proxmox VE display any errors when the VM bluescreens?