https://bugzilla.suse.com/show_bug.cgi?id=1218104 https://bugzilla.suse.com/show_bug.cgi?id=1218104#c12 --- Comment #12 from Michael Chang <mchang@suse.com> --- (In reply to Jaan Haabma from comment #11)

Hi Michael,

Thank you for your Debug boot hints, I will try them as soon as possible, but unfortunately can not do this today since the box is in other use ...

Yes, before my fresh install of Leap 15.X (e.g. 13.X, 42.X) it booted with legacy BIOS boot. At that old times, I thought UEFI was not mature enough ... So I changed this to UEFI before fresh installing Leap 15.X. I also made the FS btrfs (used to be ext3 also of maturity reasons ...). I hoped that the latest 15.5 upgrade now would had fixed the Xen problem - have seen the same error message on Google, but no solution ... This was probably a bad idea. But I have UEFI and btrfs Leap 15.X running on other boxes for several years so I thought it now was a safe thing to do ...

Several factors can lead to failure, and it's not solely dependent on the age of the computer. Older hardware may deteriorate due to less usage, and tests are often conducted on modern, widely-used systems.

So reverting back to legacy BIOS boot might also be a solution to test later ?

I'd recommend to continue with legacy bios test to establish a common ground of verifying the issue for $subject in relation to software regression.

The Leap install ha one FS name diff in /boot (which I do not understand but probably does not matter). The Xen error box have /boot/efi/efi/... The upgraded (working) Xen box have /boot/efi/EFI/...

The vfat* file-system are not case sensitive, so it should be fine ... Thanks. -- You are receiving this mail because: You are on the CC list for the bug.