Linux 6.13 PM Switches EPYC Turin To AMD P-State, More Aggressive Default For Intel GNR

[phoronix]

Phoronix: Linux 6.13 PM Switches EPYC Turin To AMD P-State, More Aggressive Default For Intel GNR

The power management subsystem updates have been submitted for the newly opened Linux 6.13 merge window. As covered within individual articles over the past few weeks, the Linux 6.13 power management updates include some notable changes for both AMD and Intel systems...

https://www.phoronix.com/news/Linux-6.13-Power-Management

[muncrief]

I apologize for being off topic, but I just upgraded to 6.12 today and none of my QEMU/KVM virtual machines will boot. I have a Windows 10 VM without passthrough, a Windows 10 VM with GPU/USB/SATA passthrough, and A Windows 11 VM with GPU passthrough, and all of them halt after displaying the TianoCore boot message. There's no spinning wheel, no errors in the logs, and no errors displayed when launching the VMs from the command line.

The LTS kernel, 6.6.61, launches the VMs as always, so there's definitely a bug with the 6.12 QEMU/KVM somewhere. Does anyone know anything about this?

[MastaG]

I apologize for being off topic, but I just upgraded to 6.12 today and none of my QEMU/KVM virtual machines will boot. I have a Windows 10 VM without passthrough, a Windows 10 VM with GPU/USB/SATA passthrough, and A Windows 11 VM with GPU passthrough, and all of them halt after displaying the TianoCore boot message. There's no spinning wheel, no errors in the logs, and no errors displayed when launching the VMs from the command line.

The LTS kernel, 6.6.61, launches the VMs as always, so there's definitely a bug with the 6.12 QEMU/KVM somewhere. Does anyone know anything about this?

Are you on Promox?
I had the same problem that my VMs didnt boot any longer with pci passthrough.
On the forum they mentioned I had to enable the testing repo and update.
That fixed it.

[muncrief]

Are you on Promox?
I had the same problem that my VMs didnt boot any longer with pci passthrough.
On the forum they mentioned I had to enable the testing repo and update.
That fixed it.

UPDATE:
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.