Comment # 4 on bug 1177009 from Neil Rickert

>Per your description, the issue happened after kernel upgrade in the VM.

No, that's not quite right.

The system booted fine with all kernels, up through Sept 22.  This included
booting with 5.3.18-lp152.41  However, something changed (I'm not sure what),
and  now neither 5.3.18-lp152.41 nor 5.3.18-lp152.36 will boot.  The kernel
from the release iso also will not boot, but it did at one time.

I originally installed Leap 15.2 into this VM on Aug 30, 2019 when it was an
alpha release.  I'm checking that date from the date of "/lost+found".  And it
has worked well ever since, until a few days ago.

To check the possibility that the NVRAM might be corrupt, I recreated the VM
(with a different name) using "virt-install".  And it still would not boot
those kernels.  So I don't think it is an NVRAM corruption problem.