Comment 3 for bug 1747507

I saw similar issues on an older AMD (Opteron) box. With retpoline4 it was a hang but when I used a test version of what we currently have on master-next I got a reboot as well. The fault seems to happen very quickly, so there is not even output on a serial console.

Checking /sys/devices/system/cpu/vulnerabilities/spectre_v2 I got (not sure I remember the exact phrase) "full AMD retpoline". Then I tried booting with spectre_v2=off. That allows the VM guest to boot, so this can be isolated to the AMD spectre_v2 mitigation.