Recent content by tloe

Hum.. There was a reason as I was setting up a gitlab windows runner and needed to run docker in hyper-v.. I decided to just use the gitlab shell executor instead.. So I actually don't need the args anymore.. I removed them and it started just fine now :)

➜ ~ qm start 100 kvm: error: failed to set MSR 0x48f to 0xffffff00036dfb kvm: ../target/i386/kvm.c:2701: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. start failed: QEMU exited with code 1 ➜ ~ qm config 100 agent: 1 args: -cpu host,+vmx,-hypervisor,-mpx,kvm=off boot...

Finally got it working :) I had to have these args args: -cpu host,-hypervisor,-mpx What does the mpx flag do?

Might be that the Comet Lake cpu don't have proper suport for this.

I have tried without kvm=off .. as far as I know though that does not disable kvm.. its only suppose to hide it from the guest.. Disable kvm is "kvm: 0", but as you can see in my config kvm is enabled

I also tried to copy the full cpu args line from the qm command to get all the default flags ➜ ~ qm config 100 agent: 1,type=virtio args: -cpu...

I am struggling to get wsl2, which uses Hyper-V to work in a Windows 10 Pro guest. Proxmox is running on a Intel NUC with a i7-10710U CPU. "Intel Virtualization Technology" and "Intel VT for directed I/O (VT-d)" is both enabled in the bios. I got the latest bios (0050) I have followed this...