https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c11 --- Comment #11 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Roeland Jansen from comment #1)
in my case, ucode-amd triggered the dracut emergency shell.
Both the failed vm (intel) and laptop (intel) dropped in dracut emerg. shell:
+ (In reply to Roeland Jansen from comment #10)
he installed 15.5 (SLES) --> missing lv's and pv's
he just removed ucode-intel and it boots....
so the boot fails with any ucode? that's pretty weird...
regarding the question about the output of `dracut -f --debug test.img`?
I then need to forcefully f* up one instance. Not sure if we can do. At work, these vm's ertainly cannot be f* up.
You can install the ucode package that you say it's breaking your boot, run `dracut -f --debug test.img 2>&1 &> dracut.log` (it does not install the initrd in the /boot partition), and uninstall the ucode package. Otherwise, if we don't have any kind of log it's quite difficult to guess what may be happening, I've never seen a similar bug report. -- You are receiving this mail because: You are on the CC list for the bug.