LEAP gues inside a tumbleweed QEMU/KVM vm, screen stays black after bootloader choice

I can not really tell if the system is booting (slowly, with no video update) or not booting at all.

After waiting 10 minutes, I rebooted both the outer host (tumbleweed) and then started the vm again. After two or three minutes of black, I see a graphical opensuse graphical boot menu, but then after that, I wait 10 minutes and get nowhere.

What can I do to “inspect” the startup of the system? Can I see if it’s doing anything? The CPU usage seems almost but not completely flatlined and very low, so I assume that something may be wrong. Everything worked fine until tumbleweed updates last week. Latest updates as of today still didn’t fix anything. I wonder if it’s some instability in QEMU/KVM. Anything I can do to diagnose?

Ctrl+Alt+F1/F2/… sent via SendKey menu does not even bring up a virtual console.

Windows 10 guests still work fine.

http://i.imgur.com/rpD6ktvl.png

Warren

You have to describe better each stage of the boot process you’re seeing.

In general, there is the first stage which results in the grub menu where you can select a kernel and/or recovery mode, and can specify other options like kernel modules and screen.

After you make a grub menu selection, the boot process continues and ordinarily the boot process is hidden, but you can hit the [ESC] button on your keyboard to reveal the entries. You can then see whether your boot process is frozen or simply taking a long time. You can also see errors that may be happening.

Nowadays, there is also a glitch in the boot process if you have a Desktop installed, the boot process will complete to where a User might login in text mode, but the system is just taking a long time to proceed further but I’ve not seen this glitch to last more than about 60 seconds or so.

TSU

I wasn’t able to see anything with Escape key hit, and even waiting 10 minutes the screen stayed black. I ended up nuking the VM and reinstalling the LEAP vm, and it’s working fine now.

W

Although not common, your experience and solution happens often enough…
When a brand new Guest doesn’t work, I often “nuke” it and create again.

And, I’ve done this in all types of virtualization.

TSU

I had a similiar problem with a openSUSE leap guest in a opensuse leap host, a blank screen after installation but changing the graphics driver in virt-manager solved the problem