My VM screen is ridiculous since VirtualBox 6.1 [Lubuntu VM]

[AKR54]

Hello world,

All explanations are in subject above.
Since VBox 6.1, my VM window is ridiculusly short and I can't change anything !
Has somebody an idea about the problem, please ?
Thank you all !

[mpack]

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[AKR54]

OK
Thanks

[mpack]

I don't expect a graphical OS to show higher display sizes if you only give it 16MB graphics RAM. It is also helpful to enable 3D acceleration after the GAs are installed. 1024MB normal RAM and a single core is not kind either for a modern 64bit VM. I would suggest 2048MB RAM, 128MB graphics RAM, 2 cores.

00:00:03.351528 [/Devices/vga/0/Config/] (level 4)
00:00:03.351530 3DEnabled <integer> = 0x0000000000000000 (0)
...
00:00:03.351539 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

Your Guest Additions are crazy out of date and aren't from VirtualBox, they are from the Ubuntu fork build. This should be updated ASAP.

00:00:31.999941 VMMDev: Guest Additions information report: Version 5.2.8 r120774 '5.2.8_KernelUbuntu'

Finally, this does not seem to be hurting anything, but in the log I see a number of complaints about unsigned host DLLs, specifically "FileSyncShell64.dll" (part of MS OneDrive I think), and also "ASUSWSShellExt64.dll" - part of a third party shell extension I'm guessing from the name. VirtualBox discards unsigned DLLs, which can lead to stability problems. You should check the digital signatures on both files. You can find full filenames in the log.

[AKR54]

I did never change any VM settings before.
What I mean is : everything worked before VirtualBox 6.1.34 r150636.
Settings have since been changed... without success.
Thank you for everything !
Akr54

[mpack]

A new log is required to demonstrate that all of the changes were made. See previous instructions.

[scottgus1]

In addition to the new log, if you revert back to the old version of Virtualbox, does the screen size start working correctly again?

Something pertinent about the video sizes: the VM toggles around between 640x480 and 800x600, which are basic no-frills bad-or-no-drivers fallback sizes. If the 5.2.# Guest Additions in the VM were an indication that you were running earlier than 6.0 Virtualbox (you don't mention what version actually worked before, only that in 6.1 it doesn't work, hint hint ) then if you switched up to 6.1 from 5.2 there were several video changes, which require more up-to-date Guest Additions. The big kahuna: 5.2 GAs does not have drivers for VMSVGA video, which didn't exist in Virtualbox 5.2.

[AKR54]

Hi,

If I had the old VBox version, I would have already reinstalled it without coming here.
I think I'm going to destroy all my VM. That's disappointing me too much.
And my previous VBox version was 6.0.

[scottgus1]

If I had the old VBox version, I would have already reinstalled it without coming here.

Reinstalling the old version is not trying to blow you off. It's a valid testing procedure: Coming up with a repeatable process to demonstrate an error helps the error fixers find the problem. If the old version reliably works when reverted, and the new version does not, then we can look at what changed between versions. But if reverting to the old version does not restore a working VM, then the problem is elsewhere, maybe a coincidental problem in the VM OS.

If I had the old VBox version

Ask and ye shall receive:
https://download.virtualbox.org/virtualbox/
Saving old installers is always a wise idea.

The new log shows a VM with 3D acceleration turned on, old Guest Additions that don't have drivers for the VMSVGA video card, and hardening errors from old unsigned video drivers on the host, which are necessary for 3D acceleration and cannot be used due to bad security signing. This VM used to have 3D off. Turning on 3D probably caused the error. This VM and host cannot use 3D acceleration.

I think I'm going to destroy all my VM.

You don't need to go that far yet, but trying to make a new VM with 2 processors, 3D off, see if the VM boots, install Guest Additions (prerequisites first https://www.virtualbox.org/manual/ch02. ... nux-prereq), see if the VM screen works well.

[AKR54]

Sorry, I was trying 3D acceleration because I was asked to do :

[quote="mpack"]It is also helpful to enable 3D acceleration after the GAs are installed.
[quote]

[scottgus1]

Sorry, I was trying 3D acceleration because I was asked to do :

No need to apologize, it's not wrong to try things, especially if you were asked to. In this case trying 3D exposed further problems that weren't visible before. So we now know that 3D won't work on your host, unless you can update your host video drivers.

Please let us know how the new VM works.