Win10 limited display size on headless Linux server via RDP

[avsfxm10]

Host: Gentoo on remote rack server
Guest: Windows 10 Pro 64bit
Virtualbox 5.0.2
Guest additions 5.0.2 installed
Oracle VM VirtualBox Extension Pack 5.0.2 installed

Virtualbox headless is running on a remote Gentoo rack server box. I am logging in to the VM remote from a Windows 8 system via RDP (Remote Desktop Connection) using the Oracle Virtualbox VRDP module.

The screen resolution of my Windows 8 system is 1920x1200 but the maximal virtual display resolution the remote Win10 offers via RDP is 1600x1200.

The Win10 VM is configured with

Code: Select all

--vram 16

which I believe should be sufficient for 1920x1200@32bit.

What am I doing wrong? How could I get the Win10 remote guest to run via RDP in full screen (1920x1200)?

[noteirak]

Gentoo is, AFAIK, not directly supported by Oracle. Just so you're aware you should also check with them if we can't help here.
By default, VirtualBox assign 128MB of vRAM to Windows 10 guest. Try that first.

[avsfxm10]

By default, VirtualBox assign 128MB of vRAM to Windows 10 guest. Try that first.

Thx a lot! 128MB vRAM indeed fixed it.

When I set up the VM specifying OSType Windows10_64, it was automatically configured with 8MB vRAM. I doubled it to be on the safe side, calculating that the required resolution should need around 9MB... obviously I was wrong.

[Martin]

When I set up the VM specifying OSType Windows10_64, it was automatically configured with 8MB vRAM.

I just created a new VM with OS type Windows 10 (64bit) and the VRAM was automatically set to the correct 128MB.

[avsfxm10]

I just created a new VM with OS type Windows 10 (64bit) and the VRAM was automatically set to the correct 128MB.

Did you do it on a headless server box using

Code: Select all

VBoxManage createvm --name "Win10" --ostype Windows10_64 --register

?

I am not 100% sure it was 8MB but am pretty sure I checked the VM settings after creating the VM with the above command and decided to increase vRAM to 16MB...

Maybe it has to do with the unsupported Gentoo setup mentioned above. Anyways, problem solved with 128MB