Open joebonrichie opened 11 months ago
I don't use virt-manager, because it makes it too hard to access my NAS. But on VirtualBox, there are two different video adapters for SVGA when choosing settings for a VM. VBoxSVGA works fine for all the other Solus editions, but if I use that for creating a GNOME VM, the result is as you said - no image appears, just a blank screen. If I use the VMware emulator, the VMSVGA setting, GNOME works*. I don't know if this will help you, but you might check to see whether virt-manager also offers a choice when it comes to the video adapter.
I tried booting the Gnome 4.5 RC5 ISO in virt-manager and VirtualBox (UEFI). In virt-manager I got a black background with an X cursor.
The VB VM wouldn't boot at all, with any Graphics Controller, so I couldn't test with that. I got an error (which is a VBox problem, not a Gnome problem)
VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE).
TL;DR, VirtualBox does not play nicely on a system with virt-manager also installed.
I was able to boot to the graphical installer normally using a live USB on a Lenovo Flex.
I have experienced the same problem with virt-manager and a Gnome VM on shannon Also see getsolus/packages/issues/1548
Summary
When booting the GNOME edition in an VM with LLVMPipe graphics enabled an image doesn't always appear on boot. An reset is generally required to fix it.
Steps to reproduce
Expected result
A graphical session to always appear
Actual result
Sometimes no graphical appears
Environment
Repo
Shannon (stable)
Desktop Environment
GNOME
System details
System Details Report
Report details
Hardware Information:
Software Information:
Other comments
I vaguely remember this being an issue at least since the 4.4 ISO
This doesn't seem to happen with other editions so could be a GNOME specific bug or a bug in llvmpipe/mesalib