Vincent Elliott's picture


I have tried to install both the CORE and MONGODB v16.1 appliances running under libvirt and the installation failed everytime when trying to install grub on an LVM disk.

The error reported is a "fatal error" irrespective of selecting any of the provided options except "Manually specifying the drive...".

This issue I have found is that grub defaults to trying to install to /dev/mapper irrespective of the selected target except as noted above "Manually specifying...".  In my instance I had to manually specify "/dev/vda" and then it worked without further issue.

As an asides, the hostnamectl command is missing and attempting to change the hostname from the confconsole menu does nothing...

Thanks again for the great effort in creating and making these applicances available.

Best regards and keep safe,


Jeremy Davis's picture

What you note is a known issue with some VMware platforms, but I have not hit those issues on KVM, Xen or VirtualBox. I'm not sure why, but it seems that for some reason grub trips up on the drives as presented by some VMware virtualisation?!

Did you restart after changing the hostname? It definitely should work!?

Very Siberian's picture

The same thing happened to me just now when installing one of the new TKL apps from the ISO using VirtualBox 6.1.40. Fortunately, Vincent's tip worked like a charm!

Best regards,


William Bryan's picture

I ran into the same issues with unbuntu + cockpit virutal machines (libvirt/kvm).  Thanks for the tip Vincent!!  It basically just ignores the selection and defaults unless you manually type in the drive.
Vision_Thing's picture

Thanks Vince :D Also had to select manually and specify /dev/sda Selecting /dev/sda does not work ... I had to specify Enter device manually and then /dev/sda Solved :D  

Add new comment