resolution not accepted by the frontend

Discussions related to using VirtualBox on Windows hosts.
Post Reply
altenbach
Posts: 3
Joined: 15. Aug 2017, 00:34
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: W10, W7
Contact:

resolution not accepted by the frontend

Post by altenbach »

So I've been using virtualbox VMs for a while for software testing. I typically insert a <ExtraData> as

"<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
...
I have no idea where that "1440" WARNING! comes from. The digits 1440 are not contained in the vbox file or anywhere else I looked. (the native host screen is 2560x1440, but that seems irrelevant).

(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!
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: resolution not accepted by the frontend

Post by mpack »

Please provide a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.
altenbach
Posts: 3
Joined: 15. Aug 2017, 00:34
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: W10, W7
Contact:

Re: resolution not accepted by the frontend

Post by altenbach »

mpack wrote:Please provide a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.
I am attaching a zip file with two logs for two quite similar VMs. In one, 1080HD does not work (as described in the first post above) and in the other one 1080HD resolution works just fine. The one that does not work contains the warnings already quoted. Both are on the same host computer.

For each, I freshly launched the VM and then shut it down once W10 was loaded. Then I copied the log file once the VM was closed.

I am sure there must be some subtle difference, but I really don't know where to look. Any pointers appreciated!

Thanks. Let me know f you need anything else.
Attachments
Vbox-1080HDLogs.zip
requested log files.
(61.18 KiB) Downloaded 7 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: resolution not accepted by the frontend

Post by mpack »

I didn't need the working VM log thanks, only the log I asked for.

I don't see any errors in the configuration, so this looks to me like typical aspect ratio problems. Windows thinks it has a 4:3 display and is filtering out display size suggestions from the graphics adapter which are not 4:3.

Sometimes this can be fixed by dragging the monitor to a 16:9 aspect ration. Another thing you can try is, in the manager UI, try setting option File|Preferences|Display|Max Guest Screen Size to None.
altenbach
Posts: 3
Joined: 15. Aug 2017, 00:34
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: W10, W7
Contact:

Re: resolution not accepted by the frontend

Post by altenbach »

Thanks. I guess there is no real explanation what could be wrong here. I am not familiar enough with the system to know what a "typical aspect ratio" problem is. :D

As I said, I have dozens of VMs and only exactly one shows this weird thing (even though it is a clone of a properly working one). I guess there is nothing specific we can blame. I thought that maybe I accidentally messed up something by a slip of the mouse.

I was able to drag the window to the correct size and get my desired resolution now. So thanks! :D
Post Reply