Autoscale Ubuntu 22.04 guest in VirtualBox 6.1 Windows Host
Posted: 23. Aug 2022, 22:54
VirtualBox version: 6.1.36 r152435
Windows host version: 10 Pro 64-bit
Ubuntu version: 22.04
I've installed the latest VirtualBox version on a new Windows 10 laptop workstation, along with the updated Guest Additions. I've created a single VM running Ubuntu 22.04. Here are some details on the Display configuration within the machine config:
Memory: 32 Mb
Scale factor: 100%
Graphics controller: VMSVGA (recommended by VirtualBox)
If I select either of the other 2 available Graphics Controllers, VBoxVGA or VBoxSVGA, VirtualBox gives an error that an invalid controller is selected. When I start the VM the View option to Auto-resize Guest Display is grayed out.
I have a similar configuration on an older desktop machine running the prior version of VirtualBox and Ubuntu 18.04. The Auto-resize option works fine in that configuration. I created an Ubuntu 18.04 VM in the newer VirtualBox installation on the laptop just to see if something about the guest OS was contributing or causing the problem. No dice. So, the problem seems specific to this latest version of VirtualBox.
Any ideas?
Windows host version: 10 Pro 64-bit
Ubuntu version: 22.04
I've installed the latest VirtualBox version on a new Windows 10 laptop workstation, along with the updated Guest Additions. I've created a single VM running Ubuntu 22.04. Here are some details on the Display configuration within the machine config:
Memory: 32 Mb
Scale factor: 100%
Graphics controller: VMSVGA (recommended by VirtualBox)
If I select either of the other 2 available Graphics Controllers, VBoxVGA or VBoxSVGA, VirtualBox gives an error that an invalid controller is selected. When I start the VM the View option to Auto-resize Guest Display is grayed out.
I have a similar configuration on an older desktop machine running the prior version of VirtualBox and Ubuntu 18.04. The Auto-resize option works fine in that configuration. I created an Ubuntu 18.04 VM in the newer VirtualBox installation on the laptop just to see if something about the guest OS was contributing or causing the problem. No dice. So, the problem seems specific to this latest version of VirtualBox.
Any ideas?