The interesting thing is that this message:
Code: Select all
00:00:51.792671 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=2560 h=1440 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
Code: Select all
00:00:51.792671 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=2560 h=1440 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
If this error was a "Disk Full" error, Ubuntu et al is known to fail to open a GUI desktop with a full disk, whether on real hardware or in a VM. Fixing as one would do on a real PC with the problem is needed. Web-search how to fix this through Ubuntu's help channels.adi5 wrote:I was using my Lubuntu 20.04 virtualbox guest OS just this morning and it was running fine. .... I attempted to install an update, I remember it said there was some error with installing it but I can't recall exactly what it said.
Thanks for posting what worked for you! However, I have to respectfully point out that, knowing what that ISO does, I see no way that changing host permissions on that ISO can influence how the VM OS would boot. That is an installer ISO. It has no function unless it's mounted in the VM's CD drive and the executable on it is being run inside the already-booted-to-desktop VM OS. Since the Ubuntu OS isn't booting to the desktop yet, I'm not certain how the host's permissions for the container file holding the data could help the VM OS to boot.JaimeAlba wrote:I solved it updating the permissions of the VBoxGuestAdditions.iso in C:\Program Files\Oracle\VirtualBox