Originally posted by MastaG
View Post
The issue was that hiding the VM no longer works with kernel 6.12, at least not the way I was doing it. I’d completely forgotten that long ago I had an old GT 710 NVIDIA GPU for passthrough and had to hide the hypervisor in order for it to work. And even though the basic Windows 10 VM I had that didn’t use passthrough didn’t need it, I’d configured it the same as the Windows 10 and 11 VMs that did use passthrough. Once I removed the custom inserted lines to hide the hypervisor everything worked again. They weren’t need any longer anyway, as I’d replaced the NVIDIA GPU with an AMD GPU a few years ago.
Specifically, these are the lines I’d inserted that caused the VMs to freeze:
In the features block:
<features>
…
<kvm>
<hidden state=‘on’/>
</kvm>
…
<features/>
In the cpu block:
<cpu>
…
<cache mode=‘passthrough’/>
<feature policy=‘require’ name=‘topoext’/>
<feature policy=‘disable’ name=‘svm’/>
<feature policy=“disable” name=“hypervisor” />
…
</cpu>
ORIGINAL:
No, I run CachyOS which is an optimized derivative of Arch. All I've been able to determine so far is that it has something to do with KVM because it's causing VirtualBox VMs not to boot as well and the work around is to prevent KVM modules from loading. Also note that even my Windows VM without passthrough won't boot, so I don't think it's related to passthrough. In any case it seems to be causing problems for a lot of users so hopefully it will be fixed soon.
Leave a comment: