I’ve installed EOS under VirtualBox 7.0.22 using a Debian Stable host on two different machines and EOS will not boot from the VirtualBox virtual hard drive.
I thought I read not too long ago that GRUB doesn’t get installed when using the live ISO, although the option is available during installation. So I decided to try an EFI install with systemd handling booting. That didn’t work either.
However, I ran GParted after the EFI install and the mount points are pointing to /tmp/calamares… Perhaps that is the issue. Shouldn’t the mount points be sda or sda1/sda2?
These mount points are from install process, after install has finished they should get unmounted automtically.
Indicating something not working with your install.
Also used space is 570MB on the Root partition… thats not the size of any installed system.
With automatic partition options to erase the complete drive there is no known BUG only in cases when using replace empty space with replace partition, and on legacy/Bios installs with manual partition.
thats no installed Desktop but info is the king you do not said that before… same counts for the state where you see the mountpoints… in case its the same Livesession the mountpoints are from installer… on real boot or after reboot to a new livesession nothing would be mounted like that.
And a no-desktop install will not boot into any graphical Desktop (there is no) it will boot into login prompt in text only mode. Does it show any boot menu or does it show any virtual error message when try to boot?
Same with the efi partition yours showing only 2 MB used… with systemd-boot kernel images would be stored there
Just checked even with no-desktop and everything unselected on packages screen i got over 600MB in size:
In addition if install wents fine without error calamares would unmount the partitions… In case of error it would stop installing and popup an error window…
The install progress indicator (% complete) goes away and then nothing…no messages, no prompts…NOTHING. Same thing happened on two different computers.
So, I figured the install was finished. However, a reboot with the live installer disconnected results in a message something about no bootable medium.
…I got over 600MB in size.
Okay, but I unchecked some packages so that they wouldn’t be installed.
So installer was crashing? or does it said install finished and offer to checkmark to reboot with a button to finish bottom right?
were? if you done so with the packages screen inside installer process, it would be more in size if you only unselect some packages, my test was with unselecting everything there.
In case the issue is not with the install also and instead is an issue with the vm setup… but thats alll calling the magic ball without any log or details.
So, evidently there is a time limit to respond once installation has completed. I don’t think that’s ideal. I’m going to try the install again under VirtualBox on my desktop and try not responding and see what happens.
