Windows – Virtualbox 4.2.10 Auto resize not working. Will auto-resize down but not up unless in full screen

resolutionvirtualboxvirtualizationwindows 7

Using Virtualbox 4.2.10 with Windows 7 as host and guest.

If I press Ctrl+F, the OS goes full screen. If I check the resolution, it says 1680×1050 — same size as my host OS that has many (approximately 20) other options, including MUCH bigger resolutions.

Now if I press Ctrl+F again (I want it to just fill the available window), it goes back down to 1024×732.

If I shrink the window, the resolution DOES scale down, BUT will not scale back up when I resize the window again. When I check the resolution after resizing it down, it's at 640×480 (no other options available).

Here is a video describing the problem.

HD Version

Could someone please help me fix this odd problem?

Configuration:

Host

  • Windows 7
  • 16 GB RAM
  • 2 Nvidia 680's (factory overclock) on SLI (4GB for each video card)
  • CPU virtualization turned on

Guest

  • Windows 7
  • 4 GB RAM
  • Guest tools installed

Best Answer

From the virtualbox.org manual Chapter 9. Advanced topics :

When guest systems with the Guest Additions installed are started using the graphical frontend (the normal VirtualBox application), they will not be allowed to use screen resolutions greater than the host's screen size unless the user manually resizes them by dragging the window, switching to full screen or seamless mode or sending a video mode hint using VBoxManage. This behavior is what most users will want, but if you have different needs, it is possible to change it by issuing one of the following commands from the command line:

VBoxManage setextradata global GUI/MaxGuestResolution any

will remove all limits on guest resolutions.

VBoxManage setextradata global GUI/MaxGuestResolution >width,height<

manually specifies a maximum resolution.

VBoxManage setextradata global GUI/MaxGuestResolution auto

restores the default settings. Note that these settings apply globally to all guest systems, not just to a single machine.

In the case of the poster, it was the first command that fixed the problem.

Related Question