#21512 new defect
Auto-Resize Guest Display not applied at X startup
回報者: | Nicolas | 負責人: | |
---|---|---|---|
元件: | guest additions | 版本: | VirtualBox-7.0.6 |
關鍵字: | 副本: | ||
Guest type: | Linux | Host type: | Windows |
描述
Hi,
Sometimes, especially at startup, guest resolution is not changed, even, if Auto-Resize Guest Display. This is a regression from 6.1.
Steps to reproduce:
- Start a VM in full screen mode (Debian stable, UEFI resolution set to 1080p, physical screen is QHD)
- X starts, guest stays in 1080p
- quit then re-enter full screen: guest screen size correctly adapts to QHD resolution
Regards, Nicolas
附加檔案 (5)
更動歷史 (15)
21 月 前 由 編輯
comment:3 20 月 前 由 編輯
Hi Nicolas,
Could you please attach VBox.log for this VM when running VirtualBox 6.1, so we could compare two logs?
comment:4 20 月 前 由 編輯
I have a similar problem with 7.0.6 (guest OS Oracle Linux Server release 7.9, host OS MS Windows 10).
In my case the physical screen is FHD and when X starts it's not in FHD; doing a restart of the guest OS X starts in FHD, but restarting VirtualBox makes the problem happens again.
The problem started with a 6.x version (I can't remember correctly, it should be upgrading from 6.1.6 to 6.1.10). @Nicolas, which was your 6.1 version exactly?
Then that problem apparently was fixed starting from 7.0.0 and it is also working correctly with 7.0.2 and 7.0.4 but the problems appeared again upgrading to 7.0.6.
Obvioulsy VBoxGuestAdditions are rebuilt at every upgrade.
P.S. sorry, I don't want to "steal" your ticket, I just want report another case about what seems to be the same issue.
P.S.S. Starting from 7.0.6 I also have a problem with serviced at shutdown, it hangs on vboxadd as far as I can remember; I have to wait 5 minutes for the timeout at every shutdown, so I went back to 7.0.4.
comment:5 20 月 前 由 編輯
I reinstalled 7.0.6 again (and than 7.0.4 again). The problem seems different from the similar one I had from 6.1.x (with x > 6) and solved starting from 7.0.0 because in that case pressing R_CTRL+F2 and then R_CTRL+F1 was enough to make the screen fit the whole screen.
About the previosly mentioned problem with the vboxadd.service I wasn't remembering correctly. The problem starts after installing 7.0.4 after 7.0.6. It seems that installing GA 7.0.4 twice solve the problem, even if I run uninstall.sh on GA 7.0.6 before uninstalling 7.0.6 and installing 7.0.4 again.
I added VBox.log from both 7.0.6 and 7.0.4. I stripped the time "column" to make a comparison easier.
comment:6 19 月 前 由 編輯
Hi all,
@galitsyn attaching 6.1 log. @alealeale currently running 6.1.42, but the behavior is consistent across the whole 6.1 series.
Regards, Nicolas
19 月 前 由 編輯
comment:7 19 月 前 由 編輯
@NicolaF_
does the display resize correctly for you on 6.1.x pressing R_CTRL+F2 and then R_CTRL+F1 on the first login screen?
comment:8 19 月 前 由 編輯
This started happening for me too in 7.0.6. This was an issue I remember from 6.something that has been fixed for a long time. 7.0.6 reintroduced the problem. If I start in full screen, I have to exit and re-enter full screen for the guest resolution to refresh. 7.0.8 is doing the same thing. I have a Windows 10 host and this happens with every Linux guest. I have multiple Ubuntu guests at 18.04, 20.04, and 22.04. Also, an Oracle Linux 7.9. Windows guests do not have this problem.
This is logged as a guest additions issue, but it's happening for me regardless of guest additions version. I have a VM still running 6.1.36 and it happens on that machine too. It seems to be related to VirtualBox itself.
comment:9 19 月 前 由 編輯
Hi,
Just looked further, and there ineed seems to be an issue with advertized mode. Here is the xrandr -q
output just after X startup (host sscreen is 2560x1440):
nico@work:~$ xrandr -q Screen 0: minimum 1 x 1, current 1920 x 1080, maximum 16384 x 16384 Virtual1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1920x1080 60.00*+ 2560x1600 59.99 1920x1440 60.00 1856x1392 60.00 1792x1344 60.00 1920x1200 59.88 1600x1200 60.00 1680x1050 59.95 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 60.02 1280x800 59.81 1152x864 75.00 1280x768 59.87 1024x768 60.00 800x600 60.32 640x480 59.94 Virtual2 disconnected (normal left inverted right x axis y axis) Virtual3 disconnected (normal left inverted right x axis y axis) Virtual4 disconnected (normal left inverted right x axis y axis) Virtual5 disconnected (normal left inverted right x axis y axis) Virtual6 disconnected (normal left inverted right x axis y axis) Virtual7 disconnected (normal left inverted right x axis y axis) Virtual8 disconnected (normal left inverted right x axis y axis)
and after leaving/reentering full screen:
Screen 0: minimum 1 x 1, current 2560 x 1440, maximum 16384 x 16384 Virtual1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 2560x1440 60.00*+ 2560x1600 59.99 1920x1440 60.00 1856x1392 60.00 1792x1344 60.00 1920x1200 59.88 1600x1200 60.00 1680x1050 59.95 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 60.02 1280x800 59.81 1152x864 75.00 1280x768 59.87 1024x768 60.00 800x600 60.32 640x480 59.94 Virtual2 disconnected (normal left inverted right x axis y axis) Virtual3 disconnected (normal left inverted right x axis y axis) Virtual4 disconnected (normal left inverted right x axis y axis) Virtual5 disconnected (normal left inverted right x axis y axis) Virtual6 disconnected (normal left inverted right x axis y axis) Virtual7 disconnected (normal left inverted right x axis y axis) Virtual8 disconnected (normal left inverted right x axis y axis)
comment:10 7 週 前 由 編輯
Hi,
Some news after upgrading to 7.1.x: The issue persists, but we now have an error:
Failed to change display parameter. The console is not powered up (Display::setVideoModeHint). Result Code: E_ACCESSDENIED (0x80070005) Component: DisplayWrap Interface: IDisplay {4680b2de-8690-11e9-b83d-5719e53cf1de}
4 週 前 由 編輯
附檔: | 新增 Vbox-7.1.2.log |
---|
Hi Nicolas,
I think it was always an issue, also with 6.1. We cannot prevent guest window manager from setting screen resolution to its default value when it starts. At least there is no simple solution for this at the moment.