[Bug]: [KVM] Computer stuck on boot menu: GRUB loading

MassOS-Linux / MassOS

Main source repository for the MassOS operating system.

https://massos.org

Other

97 stars 8 forks source link

[Bug]: [KVM] Computer stuck on boot menu: GRUB loading #34

Open lilian-pouliquen opened 2 years ago

lilian-pouliquen commented 2 years ago

Checklist

[X] I have searched for other issues, and can confirm my issue has not already been reported.
[X] If this is an issue with a specific program, I have checked the upstream project's issue tracker and determined that it is an issue with MassOS itself.

MassOS version

2022.06

Kernel version

Linux 5.18.1-massos #1 SMP PREEMPT_DYNAMIC wed Jun 1 16:11:46 UTC 2022 x86_64

Subject

[X] Issue at runtime of MassOS.
[ ] Issue with the MassOS Live CD.
[X] Issue with installing MassOS.
[ ] Issue with the MassOS documentation.
[ ] Issue compiling MassOS from source.

Expected Behavior

I wanted to test MassOS on a virtual machine. So I built one and used the standard ISO to install MassOS on the virtual disk. Everything is fine until the virtual machine reboots after the installation. At this point it should be restarting and boot into MassOS correctly, allowing me to use it.

Actual Behavior

The fact is, when the virtual machine reboots, it gets stuck in the boot menu with the message "GRUB loading." staying forever. I did not manage to make it work, even by reinstalling the OS with different configurations nor by recreating the virtual machine. grub_loading .

Steps to reproduce

Create a virtual machine using virt-manager (see attached xml file)
Start the virtual machine with the standard ISO: massos-2022.06-x86_64.iso
Install the system on the virtual disk using the MassOS installer
1. Install option
2. Choose the virtual disk and erase it to install
3. xfs or ext4 filesystem
4. Say yes to create swap partition
5. Say yes to erase all data on the disk
6. fr_FR.UTF-8 locale
7. fr FRENCH keyboard
8. Europe/Paris timezone
9. Set root password
10. Create the primary user
11. Say yes or no to make Blueman autostart on login
12. Say yes or no to make the bootloader detect other OSs
Remove the ISO from the virtual machine, or change the boot order
Let the virtual machine reboot after the installation

massos_kvm.txt

Additional Information

No response

marseye commented 2 years ago

Hi,

I have the exact same stuck grub problem when starting Massos, except it's as a VM with VMWARE Workstation 15.5.7 build-17171714. Same settings as lilian-pouliquen above, with these VM settings :

type : linux 64 bits, kernel >5.x
Bridged network
4 Processors
4GB RAM
20GB scsi

I'm using the massos-2022.06-x86_64.iso

As soon as the first reboot initiates (.iso detached), Grub seems to initiate, but then : "A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware Workstation."

I've been trying with and without the grub install : it always installs the same, and its stuck under 2s after the "GRUB Loading." message.

ghost commented 2 years ago

I don't see to be able to replicate this issue on my side as well with a VM (virt-manager nor gnome-boxes) so i can't help you with that.

DanielMYT commented 2 years ago

Thanks for bringing this issue up.

I was able to replicate this issue in Oracle VirtualBox, however it only occurs when the virtual hard disk's interface is IDE and the boot mode is Legacy. If the Virtual hard disk is connected via SATA (which is the default), the boot is fine, and if the boot mode is UEFI (which is preferred for MassOS), the boot works in both IDE and SATA.

From the attached massos_kvm.txt file, it looks like your disk is configured in IDE, so I'd recommend switching it to SATA, and/or switch the boot mode to UEFI if your VM software supports that.

I will leave this issue open though since IDE+Legacy boot shouldn't be failing, however my discussed workaround should allow MassOS to boot in your virtual machine (NOTE: if you switch the interface or boot mode you may need to reinstall MassOS). Hope this helps you.

TheRealSlander commented 2 years ago

I confirm this issue on both virtual machines and real systems. Sometimes the "GRUB loading" message is visible and it stays like that undefinitely, sometimes, the machine reboots itself again and again and again after the BIOS checkup screen.

The machine is an asus AT3-ION TI Deluxe with 3GB of ram and a SATA hard drive plugged in. The installation process is exactly the same as the OP (french locale/keyboard, SWAP, etc...) with the exact same version of MassOS.

I planed to use it on this old machine where Manjaro is working but a bit slow. All other distros I tested are also working without tricking the installation or the harware configuration on this particular machine.

Regarding your workaround, how to achieve the changes?

lilian-pouliquen commented 2 years ago

Thank you guys for your replies!

I confirm that using an UEFI boot firmware on the virtual machine makes MassOS boot correctly after install. The OS works fine, great job guys!

However I noticed that even if I chose French keyboard layout and locale at installation, the system and keyboard are in English (still on a virtual machine). Should I report it in another issue?

TheRealSlander commented 2 years ago

@lilian-pouliquen I suspected something like that for the French locale/keyboard as when the installation process is generating locales, only the "english" ones are displayed. Unfortunately, I could not test the OS after installation due to the issue I reported above, so I cannot confirm that fact. But I think it should be reported as an issue indeed.

Otherwise, can you tell me how you did manage to use an UEFI boot on your virtual machine? I use Qemu and Virtual-Manager for my virtual machines by the way.

lilian-pouliquen commented 2 years ago

@lilian-pouliquen I suspected something like that for the French locale/keyboard as when the installation process is generating locales, only the "english" ones are displayed. Unfortunately, I could not test the OS after installation due to the issue I reported above, so I cannot confirm that fact. But I think it should be reported as an issue indeed.

Otherwise, can you tell me how you did manage to use an UEFI boot on your virtual machine? I use Qemu and Virtual-Manager for my virtual machines by the way.

Okay I'll make another issue for the keyboard layout then.

You can select the boot firmware at the virtual machine creation. In virt-manager. To do so, check the "Customise configuration before installation" checkbox at the 5th step of the VM creation:

customise_config

Then, click on "Finish". it is now opening the customisation window, where you can tweak all your VM. To set the boot firmware to UEFI, go to the "Overview" tab and select an UEFI option in the "Firmware" option:

choose_boot_firmware

Do not forget to apply changes (virt-manager should remind you to do it if you try to do anything else). You can then explore the configuration as you want.

I usually change these settings when I create a VM:

Overview tab:
- Chipset: Q35
- Firmware: UEFI x86_64 : /usr/share/edk2/ovmf/OVMF_CODE.fd
Processors tab:
- Configuration: Copy host processor config if it is host-passthrough, select host-passthrough else
- Topology:
  - Check the define processor topology manually checkbox
  - sockets: 1
  - cores: number_of_wanted_vcpu / number_of_threads
  - threads: 2
Disks:
- Disk bus: SATA or VirtIO

I hope this will help you!

TheRealSlander commented 2 years ago

Thanks a lot @lilian-pouliquen! I tried what you suggested to do for the configuration in virt-manager but first when I clicked on "start installation", I had this error message:

Unable to continue installation: « unsupported configuration: IDE controllers are unsupported for this QEMU binary or machine type »

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/createvm.py", line 2008, in _do_async_install
    installer.start_install(guest, meter=meter)
  File "/usr/share/virt-manager/virtinst/install/installer.py", line 695, in start_install
    domain = self._create_guest(
  File "/usr/share/virt-manager/virtinst/install/installer.py", line 637, in _create_guest
    domain = self.conn.createXML(initial_xml or final_xml, 0)
  File "/usr/lib/python3.10/site-packages/libvirt.py", line 4413, in createXML

I found that this is due to the fact that I didn't select "sata" for the DVD disk as well (only did it for the hard drive entry). Mentioning it just in case someone encounter the same error message.

I was then able to start the live DVD and start the install process. I then had a screen wanting to know if the install was on an internal hard drive or an external/SSD disk, was the first time I was seeing this question. I selected "internal".

I was able to finish the install and to boot in the newly set system. Yeah! Thank you again.

But I confirm selecting French locale/keyboard during the install does not work. If you fill a report, I will get there and confirm it. I think I will try some other languages as well to be sure that this is not just the French one which fails.

By the way, timezone is good (selected Europe/paris).

DanielMYT commented 2 years ago

Please open a separate issue for the locale problem since these are unrelated.