I have proxmox with nested virtualization enabled. I have a windows 10 guest with cpu type set to host to get all features of my xeon. I have bitten by a windows 10 1803 bug: if vt-x is enabled the system not boot anymore. So I change cpu type to kvm64 that has no support for vt-x and windows boots again! But I lose xeon features. How can I disable only vt-x for only that guest? Thanks, Mario
any reference to that? i am running multiple windows installations with vt-x enabled no problem the only possibility at the moment is to look at the generated qemu cmdline with 'qm showcmd ID --pretty' and take the '-cpu line' (should look like: "-cpu 'host,+kvm_pv_unhalt,...' ") modify it so that you add ',-FLAG' and put that whole thing into the 'args' parameter of the vm config (in /etc/pve/qemu-server/ID.conf a new line with args: ... )
I started from this: https://answers.microsoft.com/en-us...t/582bd0ba-e29f-46b3-b347-2fd73c8556e3?auth=1 Then tried also these workarounds ( I also was able to boot in safe mode too): http://www.tomshardware.co.uk/forum...indows-corrupted-bootres-dll-unable-boot.html But this was the solution: https://www.reddit.com/r/techsupport/comments/8mh3t0/cefimicrosoftbootresourcescustombootresdll_is/ So I suppose I will keep kvm64 for now.
