"<ExtraDataItem name="CustomVideoMode1" value="1920x1080x32"/>"
Into the vbox file to support that resolution. Seems to work just fine.
However, one of my recent VMs always comes up as 1600x1200 and 1920x1024 is not even available in the Windows 10 guest OS). I have several nearly identical VMs where all this works fine.
Looking at the log, I see the following errors:
Code: Select all
...
00:00:32.130800 2D is supported!
00:00:32.138798 VMMDev: Guest Log: VBoxMP::vboxWddmVModesAdd: WARNING! :resolution 1920x1440 not accepted by the frontend
00:00:32.139105 VMMDev: Guest Log: VBoxMP::voxWddmVModesInitForTarget: WARNING! :vps(0x57)!=NO_ERROR
00:00:32.139316 VMMDev: Guest Log: VBoxMP::voxWddmVModesInitForTarget: WARNING! :vps(0x57)!=NO_ERROR
00:00:32.157137 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryAdapterInfo: DXGKQAITYPE_QUERYSEGMENT3 treating as unsupported!
00:00:32.229457 VBVA: InfoScreen: [0] @0,0 1600x1200, line 0x1900, BPP 32, flags 0x1
00:00:32.229497 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000011260000 w=1600 h=1200 bpp=32 cbLine=0x1900 flags=0x1
00:00:32.229553 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1600x1200, Sending to async-handler
00:00:32.229663 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1600x1200
...
(As I said, I have nearly identical VMs (from what I can tell) on that same host machine and this error does not occur there. On those 1920x1080 works just fine).
I might just abandon this VM and start with a good one that does not show this error, but I wonder if anyone has seen this before and maybe has an easy fix. Thanks!