Linux Fixes Hosts Randomly Rebooting During Virtualization With Ryzen 7000/8000 CPUs

[pWe00Iri3e7Z9lHOX2Qx]

Not this issue, but my 7900X3D desktop still hard crashes on resume from sleep frequently on 6.11.x. I've been running OpenSUSE Slowroll with their 6.6.x LTS kernel to have something stable. I'll try again once 6.12 makes it into a snapshot.

[fafreeman]

i hate ryzen fanboys so much its unreal. i'm not even an intel fanboy and even use a amd gpu but for as long as i can remember amd cpu fanboys have been the absolute worst. almost like they have rabies

[Paradigm Shifter]

Cyrix forever...?

i hate ryzen fanboys so much its unreal. i'm not even an intel fanboy and even use a amd gpu but for as long as i can remember amd cpu fanboys have been the absolute worst. almost like they have rabies

Just like Intel. Fanboys are fanboys. Insufferable no matter whose flag they wave.

[intelfx]

Do you have any idea what you are talking about

Lol, no, he doesn’t.

Judging by this guy’s recent comments across various topics, I’m practically convinced he is on some sort of a “trolling by cluelessness” contest.

[caligula]

i hate ryzen fanboys so much its unreal. i'm not even an intel fanboy and even use a amd gpu but for as long as i can remember amd cpu fanboys have been the absolute worst. almost like they have rabies

At least many models of Ryzen series have been very competitive products. Before Ryzen AMD had only shit hardware. Intel has f*cked the asses of their buyers several times without using lube. Two whole generations of recent chips are flawed and will eventually break down. Lots of unimpressive products. Totally f*cked up energy consumption for some generations of i7 CPUs. Also most of the 3rd to 7th generation models were totally unimpressive in terms of performance. 2600/2700k was good, the next good model was 8700k. Most users were also affected by SPECTRE/MELTDOWN. So much performance lost due to incompetence.

[jenav]

Great news! I've been hitting this bug frequently on a Ryzen 7600.

[ssokolow]

This issue is about nested virtualization, i.e. VMSAVE/VMLOAD in the guest. You won't ever experience this issue unless you really go out of your way (and get unlucky with the BIOS/ucode).

*nod* I upgraded to a Ryzen 5 7600 at the beginning of the year, I do what should be fairly typical VM stuff, and it's been rock-solid for me. I imagine the only way a typical user might run into this is if they're trying to do something like virtualizing a Windows version new enough to have Virtualization-Based Security.

[yump]

Zen 4 aka Ryzen 7000/8000 does not support VMLOAD/VMSAVE. Never has. The hardware is there, because it's shared silicon with EPYC 4004, but it's not supposed to be enabled/advertised. It is, due to motherboard OEMs just enabling everything and shipping. Easy fix kernel side, means you don't need a firmware update.

In a more perfect world, we'd probably be able to dump out some supporting microcode/firmware enablement from a board that properly supports EPYC 4004 and enable VMLOAD/VMSAVE for everyone on Zen4, but it's really not worth the effort.

I was affected by this, replaced quite a bit of hardware trying to diagnose. Unlike some, I won't be making any melodramatic edicts about it.

I think it's safe to assume it's broken on 4004 too unless somebody comes along who actually has one and can demonstrate otherwise.

Mailing list message says nothing about it, and bugged hardware is bugged hardware.

[Espionage724]

Lol, no, he doesn’t.

Judging by this guy’s recent comments across various topics, I’m practically convinced he is on some sort of a “trolling by cluelessness” contest.

And yet you never have anything countering even upon request

[intelfx]

And yet you never have anything countering even upon request

Nobody pays me to counter every piece of bullshit I see on the Internet.