virtualbox.org

If you set a Win10 guest display settings to use 3D, you can bump the VRAM up to 256MB from 128. But, if you run your VM, shut it down, then toggle off 3D, the VRAM limit doesn't go back to 128 and remains at 256.

This bug is in 5.2 and 6.0.

JustinH wrote:This bug is in 5.2 and 6.0.

Even if the VirtualBox devs do consider this to be a bug how high on their priority list do you think fixing it is going to come?

-Andy.

I'd take it one step further; why would you even call it a bug? There are some controls in the GUI to prevent you from going crazy with the VRAM when it's not needed. There are no such controls if you modify the VRAM from the CLI, and this is a valid command, even for a DOS VM:

VBoxManage modifyvm "<VM name>" --vram 256

Note that the following command is not valid:

$ VBoxManage modifyvm "<VM name>" --vram 257
VBoxManage: error: Invalid VRAM size: 257 MB (must be in range [0, 256] MB)
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "COMSETTER(VRAMSize)(ValueUnion.u32)" at line 624 of file VBoxManageModifyVM.cpp

socratis wrote:I'd take it one step further; why would you even call it a bug?

I originally started my reply with exactly those words. I then thought my poky stick was too sharp so took them out again to blunt it!

-Andy.