Search results

Greetings, I'm getting a BSOD immediately on install of Win10 if I use host for cpu type. I'm running pve 5.4-6 and a Win10 iso I pull/created from MS' tool w/in the last month. My vm config is thus: bios: ovmf bootdisk: virtio0 cores: 4 cpu: host efidisk0: local-lvm:vm-106-disk-1,size=4M...

Yeah, I read your words, but they weren't in a form I could parse. Were it not for these additional data points, I would _still_ not be able to grok wtf you were trying to convey. It was fully well not clear that the cpus on a numa nodeline were the indices used to comprise the aggregate cores...

But given my numa topology as (after booting w/no vms ever having started): root@p5pve:~# numactl -H available: 4 nodes (0-3) node 0 cpus: 0 1 2 3 4 5 6 7 32 33 34 35 36 37 38 39 node 0 size: 64403 MB node 0 free: 62904 MB node 1 cpus: 16 17 18 19 20 21 22 23 48 49 50 51 52 53 54 55 node 1...

I have a ThreadRipper 2990WX w/128GB of RAM and am running into a the same basic issue. I've attempted to duplicate most of Byron's suggestions/findings w/even less success. Although we're going for different goals. I just want one vm w/most of the RAM. root@p5pve:~# cat /proc/cmdline...