Windows 10 Display Size(Full HD) Problem

[Owner of Snow]

Hi, VB Users.

I'm using VB 5.2.10 for Windows 10 Guest OS on Centos 7.4 Host OS but
I cannot see Full HD(1920 x 1080) resolution.
It's max resolution is 1040 x 1050 on Windows 10 Guest OS.

My PC Spec is as follows.
Monitor: LG Electronics 27 inch
Graphic Card: No Additional
CPU: Intel i7 (6th edition, skylake)
Hos OS: Centos 7.4
Guest OS: Windows 10 Pro. Latest
Virtual Box : 5.2.10

When I install Virtual Box Guest Addition. it displays some problems( d3d8.dll, d3d9.dll DirectX related).
So, I tried changing permissions of those files and replacing vb driver files manually but the result is same.
And I tried changing VB Main Display Setting into "Hint 1920 x 1080" or "Auto", the result is same.

There was no problem on VB 5.1.x about a year ago but latest 5.1.34 version causes problems still.

Please share your experiences and opinions.
Thanks in advance!

[socratis]

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[Owner of Snow]

Thanks for your reply, Socratis.

I attach my zipped VB log file.

Have a nice day, Socratis!

[socratis]

00:00:00.259682 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 0 work area is actually resized to: 0x28 x 1920x1018
...
00:00:45.709627 GUI: UIFrameBufferPrivate::performResize: Size=1400x1050, Directly using source bitmap content
00:00:45.709787 GUI: Show mini-toolbar for window #0
00:00:45.716675 GUI: Adjust mini-toolbar for window #0
00:00:45.716854 GUI:  Resize mini-toolbar for window #0 to 1920x1080

VirtualBox (or Windows) tries it's best to do the maximum possible size. Since you have toolbars and status bars on your host, that max. size is 1920x1018. If you want to get to your full resolution, press HostKey+F, or from the menu View » Full-screen Mode. Then you'll get to 1920x1080. But you do *not* want to be in 1920x1080 if you're not in Full-screen mode. Scrollbars will appear in your VM window. You don't want that...

Other notes:

00:00:00.314689 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:00.427225 CPUM: Physical host cores: 4
00:00:00.427492 Full Name: "Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz"

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). See "CPU Cores versus threads" and "Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?". Your i7-6700K has 4 cores, so the maximum I would allocate to the guest would be 3.

00:00:00.314773 Path <string>  = "/usr/share/virtualbox/VBoxGuestAdditions.iso" (cb=45)

Please eject the GAs CD after you're done with the installation of the GAs. You're going to be thankful down the road...

[Owner of Snow]

Thans for you detail reply, Socratis!

I usually use Full Screen Mode(1920x1080, Ctrl + F Key), but the result screen size is not full like the attached image file.
(Maybe I guess that changed for acquiring VB log file.)

And I changed my cpu core setup 4 into 3 cores, ejected VB Guest Addition CD as your opinion.

Once again, Thank you for you reply, Socratis!

[socratis]

I'm going to need to see the recipe of the VM. Can you right-click on the VM in VirtualBox Manager, "Show in <whatever>". ZIP that ".vbox" file and attach it to your response.

[Owner of Snow]

Socratis,
this is my "Windows 10 Pro." vbox file.
(zipped because of upload limit, ".vbox" file.)

Thanks, Socratis!

[socratis]

Thanks for the ".vbox" file. You can do the following procedure in a Terminal, whether VirtualBox is running or not, but not while the VM is running, so make sure that the VM is completely shutdown from within the VM, not paused or saved-state. Issue the following commands:

• VBoxManage setextradata "win 10 pro" "GUI/LastGuestSizeHint"
  VBoxManage setextradata "win 10 pro" "GUI/LastNormalWindowPosition"
  VBoxManage setextradata "win 10 pro" "GUI/LastScaleWindowPosition"

Also, make sure that if you go to the VirtualBox Manager » Preferences » Display » Maximum Guest Screen Size: that it's set to "Auto".

Launch the VM "win 10 pro". Press HostKey+F (or from the menu View » Full-screen Mode), to take the VM full screen.


BTW, why do you have an NVMe controller in your VM?

<StorageController name="NVMe" type="NVMe" PortCount="1" useHostIOCache="true" Bootable="true"/>

[Owner of Snow]

Hi, Socratis.
After VM shut down, executed the command that told me and setup Display Size to "Auto", but the result is same.
I added the NVMe controller because I wish that will be more speedy and my host server's SSD support NVMe.

[socratis]

I'll need to see a new ZIPPED VBox.log from a new VM complete cycle run, just like last time.

And what you put as a controller for the guest, has almost zero impact to the I/O speed. It still is up to the host. You could have put a floppy controller; you'd still get "similar" speeds. I'm exaggerating a little bit here, but it's better to put a more compatible, well tested SATA controller, than an experimental, beta version NVMe controller. I'm trying to help you avoid discovering new bugs...

[arch2brain]

Hi,

I'm experiencing exactly the same problem, running Arch linux (kernel 4.16.5-1-ARCH, x86_64) host system,
Virtualbox 5.2.10 r121806, Qt5.10.1, native host resolution 2560x1440 and the resizing issue exists in all guest systems, not just Windows10!

It doesn't matter if I install the guest additions or not, I can't resize the guest resolution beyond 1280x615.

In my Windows10 guest I installed the latest guest additions for version 5.2.10, but the problem persists.

Running this exact virtual machine with Windows10 Host OS everything is fine, I can get the max resolution possible.

Windows10 Host System (x64): Virtualbox Version 5.2.8 r121009 (Qt5.6.2), latest version available;
-->auto resizing working: guest resolution 2560x1335.

This seems to be a problem with the linux version of Virtualbox.

P.S.: Guest resolution was working fine with Arch linux host OS until the update to Virtualbox 5.2.6.
Version 5.2.6 broke the auto resize function and is broken until now (5.2.10)!

P.S.2: I even reinstalled Arch linux with brand new Virtualbox (5.2.10), but I experienced exactly the same problems.
Fresh installation didn't solve this issue!

[Owner of Snow]

Hi, Socratis.

I removed NVMe Controller, restarted the Guest and attach my "Win 10 Pro" vbox zip file.

Thank you, Socratis.

Welcome, Arch2brain
And thank you about sharing your experiences, Arch2brain.

[arch2brain]

Hi,

with the arch linux updates of today, VirtualBox 5.2.12 r122571 was installed (Qt5.10.1) including the Windows Guest Additions 5.2.12.0.
After updating VirtualBox, uninstalling the old guest additions in Win10 and installing the current version, my problem still exists.
I'm still stuck with 1280x615 resolution and I can't change it to a higher value manually.

PLEASE FIX THIS BUG!

[socratis]

@Owner of Snow
I don't see anything wrong in your recipe. Try to take it in and out of FullScreen mode, don't start up with it.

@arch2brain
Until you've provided some logs, PLEASE DO NOT SHOUT!

[arch2brain]

@Socratis: Sorry I've attached the logfile of my Win10-VM.
This is what I did: Powered on the VM, logged into Win10, tried auto resize by changing the main window size (maximize vs smaller window) twice,
powered off the VM. The VM resolution in main window maximized mode was always 1280x615 and couldn't be changed manually, this was the highest resolution possible.