VirtualBox

Ticket #19496 (assigned defect)

Opened 4 months ago

Last modified 6 weeks ago

Virtualbox 6.1.6 guest screen resize broken

Reported by: Wheaties Owned by: gombara
Component: other Version: VirtualBox 6.1.6
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

The virtualbox 6.1.6 update seems to be okay, but if the matching guest additions is applied to the guest, the auto-resize or resize to any resolution is unavailable. I applied guest additions to several hosts before discovering this issue, including Centos-6, Centos-7, Centos-8, kali linux, and OracleLinux-8. Guests that have not gotten the update seem to be working fine.

Matt

Attachments

VBox-6.1.6-OI-no-resize.log Download (126.2 KB) - added by jimklimov 3 months ago.
VBox.log of an OpenIndiana that won't resize with 6.1.6 additions
VBox 6.1.6 + 6.1.7-137622.log Download (169.3 KB) - added by yuhp 3 months ago.
xorg.jpg Download (49.4 KB) - added by zd59 2 months ago.
Slackware64-current running XORG

Change History

comment:1 Changed 4 months ago by gombara

I can reproduce this issue with some Linux vms while some others seem to work as expected. A fix will follow.

comment:2 Changed 4 months ago by Wheaties

This may be of some help(?) Output from one of the broken guests:

# /usr/sbin/VBoxService --version

6.1.6r137129

# ps -ef | grep VBox

root 587 2 0 08:27 ? 00:00:00 [iprt-VBoxWQueue]

root 588 2 0 08:27 ? 00:00:00 [iprt-VBoxWQueue]

root 2068 1 0 08:28 ? 00:00:00 /usr/sbin/VBoxService --pidfile /var/run /vboxadd-service.sh

mwheat 3004 1 0 08:29 ? 00:00:00 /usr/bin/VBoxClient --clipboard

mwheat 3006 3004 0 08:29 ? 00:00:00 /usr/bin/VBoxClient --clipboard

mwheat 3014 1 0 08:29 ? 00:00:00 /usr/bin/VBoxClient --seamless

mwheat 3015 3014 0 08:29 ? 00:00:00 /usr/bin/VBoxClient --seamless

mwheat 3019 1 0 08:29 ? 00:00:00 /usr/bin/VBoxClient --draganddrop

mwheat 3020 3019 0 08:29 ? 00:00:01 /usr/bin/VBoxClient --draganddrop

root 5623 3963 0 08:34 pts/0 00:00:00 grep VBox

# /usr/bin/VBoxClient --display

VBoxClient: error: unrecognized option '--display'

VBoxClient: info: Try 'VBoxClient --help' for more information

Last edited 4 months ago by Wheaties (previous) (diff)

comment:3 Changed 4 months ago by gombara

  • Owner set to gombara
  • Status changed from new to assigned

comment:4 Changed 4 months ago by AndreyVen

This issue is reproducible in most recent KDE Neon distribution.

Screen size issue:

  1. After guest OS restart it's screen resizes to 1024x768
  2. If I resize VirtualBox window then guest OS resizes to actual size of window and then immediately resizes back to 1024x768
  3. If I resize guest OS from KDE monitor settings then it resizes and jumps back to 1024x768

Guest Additions versions:

  1. Upgraded VirtualBox and Extension Pack from 6.1.4 to 6.1.6
    • The issue is not reproducible.
  2. Upgraded VirtualBox Guest Additions from 6.1.4 to 6.1.6
    • The issue is reproducible.
  3. Downgraded Guest Additions by downloading 6.1.4 from  https://download.virtualbox.org/virtualbox/6.1.4/VBoxGuestAdditions_6.1.4.iso
    • Issue gone again.

It's obvious that the bug related to guest additions 6.1.6 for linux.

I can fetch any logs from the guest OS. Just tell me which logs do you need.

comment:5 Changed 4 months ago by AndreyVen

BTW is there a way to subscribe to ticket updates?

comment:6 Changed 4 months ago by sunrider

I see a similar problem here with Ubuntu 18.04 guests on Ubuntu 18.04 host.

The screen size is not modifiable from Ubuntu settings or the VBox window View menu when the guest is running with Wayland.

When the guest is running with X11, the screen is black after initial user login. When the screen is resized from the VBox window View menu, the normal desktop appears.

These observations are probably related.

comment:7 Changed 4 months ago by rghose

Facing a similar problem with Debian 10 Buster running on Windows 10 -VBox version 6.1.6. The screen resolution defaulted to "800x600".

I can confirm that after downgrading to 6.1.4 version of the VBoxGuestAdditions, the screen resolutions started to appear as expected - 1920x1080

comment:8 Changed 3 months ago by soapydk

I can also reproduce this problem with VB 6.1.6 Windows 10 host and RHEL 8.1 guest with GA 6.1.6. The workaround that currently works for me is to downgrade to GA 6.1.2 (6.1.4 has the clipboard bug).

For reference, here are two forum posts describing this problem:

 https://forums.virtualbox.org/viewtopic.php?f=3&t=97781

 https://forums.virtualbox.org/viewtopic.php?f=3&t=97686

I echo @AndreyVen: Is there a way to subscribe to updates to this bug/ticket?

Thanks for looking into this bug.

Last edited 3 months ago by soapydk (previous) (diff)

comment:9 Changed 3 months ago by AndreyVen

The workaround that currently works for me is to downgrade to GA 6.1.2 (6.1.4 has the clipboard bug)

@soapydk Thanks for noting this. Now clipboard works for me too :)

comment:10 Changed 3 months ago by fbatschu

interestingly I have at least 2 distros which do not show this problem when using the 6.1.6 host/GA combo: 1) Ubuntu 20.04 (Mate edition) guest on a Ubuntu 19.10 host and 2) OpenSuse 15.1 guest on a Ubuntu 18.04.4 host. Both guests where using Xorg.

Last edited 3 months ago by fbatschu (previous) (diff)

comment:11 Changed 3 months ago by fbatschu

fwiw, I also have a Fedora Rawhide guest running the 5.7-rc1 kernel and the appropriate 6.1.X GA test builds from:
Guest Additions 6.1.x revision 137519
https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_6.1.7-137519.iso
on a Ubuntu 19.10 host with working screen size adjustments. Using Gnome Classic & Xorg. However it does not work if I use Gome & Xwayland

Last edited 3 months ago by fbatschu (previous) (diff)

Changed 3 months ago by jimklimov

VBox.log of an OpenIndiana that won't resize with 6.1.6 additions

comment:12 Changed 3 months ago by fbatschu

The OpenIndiana comment is a bit misleading in the context of this bug, that did not work even before 6.1.6.

comment:13 Changed 3 months ago by jimklimov

As discussed on IRC, same problem is seen with OpenIndiana (a Solaris next of kin OS) with MATE, XOrg and 6.1.6 guest additions, on both VMSVGA and VBoxSVGA display adapters - display size does not change by events from hypervisor (window resizing, via menu of Virtual Screen / Resize).

Resizing from inside the VM (its Display preferences) locked up the kbd/mouse inputs the first time I tried, so had to restart X11 via SSH. For the second GUI session (in the same VM uptime) such resizing from the inside did work.

Reverting to additions 6.1.2 and same hypervisor (6.1.6 on Windows) fixes the issue. According to IRC however up till 6.1.2 resizing relied on a "hack" removed in later editions.

comment:14 Changed 3 months ago by jimklimov

The OpenIndiana comment is a bit misleading in the context of this bug, that did not work even before 6.1.6.

Not correct, sorry. It did work "like forever", since about the start of post-OpenSolaris era and VirtualBox 3.x? 4.x? For much of the past decade I use OI as a daily workstation, even if the HW system must be a corporate Windows, so I'd notice. And I maintain the vboxsvc for wrapping VMs into SMF instances since before then.

Until VirtualBox 6.x came about, OI users ran directly Oracle-provided binaries for Solaris (hosts and guests). Since 6.0 discrepancies grew to a point that builds from GPL source of releases are made and distributed.

comment:15 Changed 3 months ago by IgorIvanov

I confirm. Host: Windows 7 Pro x64 NVIDIA GeForce GTX 1050 Ti Monitor samsung S32D850T (DisplayPort) The guest: Linux Mint 19.3 Cinnamon

I upgraded from 6.1.4 to 6.1.6 since it fixed the clipboard error. But there was an error resizing the screen, manually resizing the window does not work, or resets to 800x600.

If you downgrade to 6.1.2, the clipboard and dynamic screen resizing work fine.

Tested each version with the corresponding version of GA and EP.

PS. Guys i think it's time to switch to use git!

comment:16 Changed 3 months ago by fbatschu

see also:

Bug 1789545 - Can't auto-resize display on Fedora 31 guest VM  https://bugzilla.redhat.com/show_bug.cgi?id=1789545

comment:17 Changed 3 months ago by caspertone2003

Hi, I wish to bring to the table that this might be also happening also in Window guests (at least my combination W10 x64 (1909/815) host and guest. VBOX 6.1.6 +ExtPack and GA 6.1.6)

Simptoms were frozen guest every time IE11 was opened. This happens when I plug to portable an external monitor, then rezising/resolution changes happen automatically. Then, once stabilized, guest frozen as explained. Might not be related to this bug as I started to use the external monitor at the same time as updated to 6.1.6, so, might be this is related to my settings and not to GA. Anyhow, was solved using the workaround (as provided here  https://forums.virtualbox.org/viewtopic.php?f=3&t=97686&start=15#p474257)

use VBoxSVGA (without 3D acceleration) as being the display device use Maximum guest size to None in the preferences Do not maximize the guest window but resize it manually (whenever you maximize the display, it appears like it is frozen)

(in my case, I had 3D on and Maximun guest size to auto)

As soon as I find some moments I will try to go back to 6.1.4 in GA with VBOX previous settings and see if this solves.

TIA

Later add: I removed GA616, installed GA614, set maximun guest size to auto, and marked 3d acceleration. Problem come back... so, either it is not the same issue or the issue comes in windows GA before 6.1.4 ...

Last edited 3 months ago by caspertone2003 (previous) (diff)

comment:18 Changed 3 months ago by gombara

We have been working on a fix and for some desktop environments like cinnamon/KDE the current state is in a better shape than before. For those interested iso image to the update guest additions is here:

https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_6.1.7-137622.iso

as usual all other test build packages from several branches are accessible here.

https://www.virtualbox.org/wiki/Testbuilds

I would appreciate any feedback especially what is not working concerning vmsvga issues on X11 guests.

Last edited 3 months ago by gombara (previous) (diff)

comment:19 follow-up: ↓ 20 Changed 3 months ago by Ynov

@gombara,

Host: 5.6.7-arch1-1 (X11)
Guest: 5.6.7-arch1-1 (LXQt on X11)
virtualbox: 6.1.6-1
Guest additions: 6.1.7-137622 (from the link above)

VMSVGA w/ 3D accel.: not working (View -> Auto-resize Guest Display is grayed-out), but was working with guest additions 6.0.20
VBoxSVGA w/o 3D accel.: working properly

Do you need any additional info/testing done?

Last edited 3 months ago by Ynov (previous) (diff)

comment:20 in reply to: ↑ 19 Changed 3 months ago by gombara

Nope. I will take a look locally. I will add a comment here if I need something more. Thanks for the feedback.

Replying to Ynov:

@gombara,

Host: 5.6.7-arch1-1 (X11)
Guest: 5.6.7-arch1-1 (LXQt on X11)
virtualbox: 6.1.6-1
Guest additions: 6.1.7-137622 (from the link above)

VMSVGA w/ 3D accel.: not working (View -> Auto-resize Guest Display is grayed-out), but was working with guest additions 6.0.20
VBoxSVGA w/o 3D accel.: working properly

Do you need any additional info/testing done?

comment:21 Changed 3 months ago by Ynov

Add to that:

Host: 5.6.7-arch1-1 (X11)
Guest: Debian 10.3 4.19.0-8-amd64 Debian 4.19.98-1+deb10u1 (GNOME 3.30.2)
virtualbox: 6.1.6-1
Guest additions: 6.1.7-137622 (from the link above)

VMSVGA w/ 3D accel.: working on X11
VMSVGA w/ 3D accel.: not working on Wayland (View -> Auto-resize Guest Display is grayed-out), but again was working with guest additions 6.0.20
VBoxSVGA w/o 3D accel.: working partially - initial resize is working (on gdm3 login), but subsequent window resizes are not applied (View -> Auto-resize Guest Display is not grayed-out), both on X11 and Wayland

comment:22 Changed 3 months ago by gombara

Please note this is not supposed to work on Wayland.

comment:23 follow-up: ↓ 24 Changed 3 months ago by andre-at-cp67

Host = Linux Debian MATE 10.3 (buster)
Guest = Linux Debian MATE 11 (bullseye)
Graphics controller = VMSVGA (with or w/o 3D accel.)

resize to fullscreen at boot is not working: guest screen plain black after boot
6.1.7 behaves just like 6.1.6

BUT ''' when I hit Host-F twice the screen is perfect !

(NB: when I booted my first VM I had no fullscreen either... but that was in 1972 on an IBM 1050 typewriter)

comment:24 in reply to: ↑ 23 ; follow-up: ↓ 28 Changed 3 months ago by gombara

yeah it is one of the remaining bugs. after reboot the full screen is restored but we get a black picture. guest is alive and all that and going out and coming back to full screen solves the problem. I am still trying to find out what goes wrong there.

comment:25 Changed 3 months ago by r0b0t

I can confirm this as well on Arch Linux (host) plus Arch Linux guest.

VBoxClient --display on the guest is never run giving :

VBoxClient: error: unrecognized option '--display'
VBoxService --version is : 
6.1.6r137129 

comment:26 Changed 3 months ago by Vbox43532

Hey ! When the bug will be fixed? Thanks.

comment:27 follow-up: ↓ 29 Changed 3 months ago by klaus

The bug is almost completely fixed in the guest additions test builds. So please try the GA isos from https://www.virtualbox.org/wiki/Testbuilds and if something is not working as expected, please describe in detail. Don't forget to attach VBox.log. It contains a lot of details which most users would otherwise forget, making the comment useless.

The problem with most 'remaining' problem descriptions in this ticket is that they're extremely vague, which makes it impossible for us to tell if we see the same issue or something else.

comment:28 in reply to: ↑ 24 Changed 3 months ago by marvin_littlewood

Replying to gombara:

guest is alive and all that and going out and coming back to full screen solves the problem. I am still trying to find out what goes wrong there.

Thank you for all your efforts. I think I have the same issue.

I routinely boot and use virtual machines in full-screen (high-DPI 1920x1080) mode on a Windows 10 host, using VMSVGA with 128MB video RAM and a Linux (Xubuntu 19:04) guest. Everything works fine with 6.1.4 and its guest additions and mostly OK with VirtualBox 6.1.6 and the 6.1.4 guest additions.

When booting with VirtualBox 6.1.6.137129 whether using the 6.1.4 or the 6.1.6 guest additions, Xubuntu booted to too small a login screen.

After installing the 6.1.6 guest additions, it again booted to too small a login but then went to a black screen after logging in. After a bit of experimentation I found that I could fix the problem by switching to another Linux terminal (ctl-alt-F2) and then back to the GUI (ctl-alt-F7) and from then on the GUI worked fine indicating that the underlying system appears to work.

Changed 3 months ago by yuhp

comment:29 in reply to: ↑ 27 ; follow-up: ↓ 30 Changed 3 months ago by yuhp

Still not working.
Windows 10 6.1.6 + Debian 10 gnome 6.1.7-137622.

ps ax | grep wayland
 1270 tty2     Ssl+   0:00 /usr/lib/gdm3/gdm-wayland-session /usr/bin/gnome-session
 1328 tty2     Sl+    0:00 /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6

VBox 6.1.6 + 6.1.7-137622.log

Replying to klaus:

The bug is almost completely fixed in the guest additions test builds. So please try the GA isos from https://www.virtualbox.org/wiki/Testbuilds and if something is not working as expected, please describe in detail. Don't forget to attach VBox.log. It contains a lot of details which most users would otherwise forget, making the comment useless.

The problem with most 'remaining' problem descriptions in this ticket is that they're extremely vague, which makes it impossible for us to tell if we see the same issue or something else.

Last edited 3 months ago by yuhp (previous) (diff)

comment:30 in reply to: ↑ 29 ; follow-up: ↓ 31 Changed 3 months ago by fbatschu

Replying to yuhp:

Still not working.
Windows 10 6.1.6 + Debian 10 gnome 6.1.7-137622.

ps ax | grep wayland
 1270 tty2     Ssl+   0:00 /usr/lib/gdm3/gdm-wayland-session /usr/bin/gnome-session
 1328 tty2     Sl+    0:00 /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6


This cannot work with Xwayland, you have to use an Xorg X11 session in order for screen resizing to work.

Last edited 3 months ago by fbatschu (previous) (diff)

comment:31 in reply to: ↑ 30 Changed 3 months ago by yuhp

Replying to fbatschu:

This cannot work with Xwayland, you have to use an Xorg X11 session in order for screen resizing to work.

But 6.1.6 + 6.1.4 work perfect (except broken clipboard).

comment:32 follow-up: ↓ 60 Changed 3 months ago by guurpi

Hi, I had the same issue:

  • Windows 10 host, VBox 6.1.6 r137129, GA 6.1.6 as shipped with VBox
  • Debian 9 client with Xorg Xserver
  • VMSVGA with 3D acceleration: log-in screen smaller than normal, then blank screen.
  • VBoxVGA without 3D accel: all good

By chance I increased the assigned video memory for the VM from 12 MB to 32 MB. Now -with VMSVGA- all looks quite normal, no blank screen anymore. Well, the automatic resizing doesn't work. That's no surprise as the VBoxClient refuses the --display option. (Btw. why is that?)

Last edited 3 months ago by guurpi (previous) (diff)

comment:33 Changed 3 months ago by arQon

VBoxGuestAdditions_6.1.7-137891 has fixed the problem in my specific case, at least:

Ubuntu MATE 19.10 x64, kernel 5.4.0-29, mesa 20.0.4, 3D accel OFF.

(Background, in case it's helpful: Was working fine with VB 6.0.12, updated to 6.1.6 a few days ago, changed nothing else, X display needed forcibly refreshing (I used a VT switch rather than Host-F switches) at startup or would only show blank screen. Updated to test GA above, changed nothing else again, all good now at startup on its own).

Thanks.

comment:34 Changed 3 months ago by mrvstudio

same problem in ubuntu mate 20.04 LTS, kernel 5.4.0-29-generic, OpenGL version string: 4.6 Mesa 20.2.0-devel

Last edited 3 months ago by mrvstudio (previous) (diff)

comment:35 Changed 3 months ago by mrvstudio

Last edited 3 months ago by mrvstudio (previous) (diff)

comment:36 follow-up: ↓ 41 Changed 3 months ago by fbatschu

In general this has been fixed in the new release 6.1.8 for guests running Xorg (not Xwayland).

However, see also #19590

Last edited 3 months ago by fbatschu (previous) (diff)

comment:37 follow-up: ↓ 38 Changed 3 months ago by zd59

Hi!

The Title of that defect should have " and 6.1.8" instead of "6.1.6" in its name. And a claim from 6.1.8 Change log:

Guest Additions: Fixed resizing and multi monitor handling for X11 guests. (6.1.0 regression; bug #19496)

should be removed as soon as possible. This simply is not truth. Guest resizing in Linux with VMSVGA DO NOT WORK.

Even worse, there is a new failure message mentioned above - #19590 And yes it shows in XORG. Looks like every new version of guest additions worsen Linux support.

Host: Windows 10 Ent 64 bit, Guest Slackware64-current + KDE5. Version of VBOX-6.1.2+GA-6.1.2 worked.

comment:38 in reply to: ↑ 37 Changed 3 months ago by fbatschu

Replying to zd59:

Hi!

The Title of that defect should have " and 6.1.8" instead of "6.1.6" in its name. And a claim from 6.1.8 Change log:

Guest Additions: Fixed resizing and multi monitor handling for X11 guests. (6.1.0 regression; bug #19496)

should be removed as soon as possible. This simply is not truth. Guest resizing in Linux with VMSVGA DO NOT WORK.

Even worse, there is a new failure message mentioned above - #19590 And yes it shows in XORG. Looks like every new version of guest additions worsen Linux support.

Host: Windows 10 Ent 64 bit, Guest Slackware64-current + KDE5. Version of VBOX-6.1.2+GA-6.1.2 worked.


Slackware is so old:
 http://www.slackware.com/

that it likely falls under the victims of the new X11 environment check as I shown in #19590

There is absolutely no reason for you to clutter this bug with your rant. Even worse, you picked the wrong bug for your complaint.

Much more helpful would be if you could explain which Slackware version you are using and from what Download location that would be available.

comment:39 follow-up: ↓ 40 Changed 3 months ago by zd59

Hi fbatschu

Sorry if I was not clear. Slackware64-current is one of the most current distributions of Linux. You can find it on  ftp://ftp.slackware.com/pub/slackware/slackware64-current/: gcc-9.3.0 xorg-server-1.20.8 On top of it KDE-5 from:  https://alien.slackbook.org/ktown/current/latest/ with: KDE 5_20.04 for Slackware, consisting of KDE Frameworks 5.69.0, Plasma 5.18.4 and Applications 20.04.0 on top of Slackware's Qt 5.13.2.

I compiled/installed kernel 5.6.10 So as you can see above, my system is very modern instead "so old" as you mentioned. Again I note, all worked with VBOX and GA 6.1.2 or less and kernels until 5.4.

Please specify what would help to debug (log files, dmesg...). Will append next time.

Regards.

comment:40 in reply to: ↑ 39 ; follow-up: ↓ 42 Changed 3 months ago by fbatschu

Replying to zd59:

Hi fbatschu

Sorry if I was not clear. Slackware64-current is one of the most current distributions of Linux. You can find it on  ftp://ftp.slackware.com/pub/slackware/slackware64-current/: gcc-9.3.0 xorg-server-1.20.8 On top of it KDE-5 from:  https://alien.slackbook.org/ktown/current/latest/ with: KDE 5_20.04 for Slackware, consisting of KDE Frameworks 5.69.0, Plasma 5.18.4 and Applications 20.04.0 on top of Slackware's Qt 5.13.2.

I compiled/installed kernel 5.6.10 So as you can see above, my system is very modern instead "so old" as you mentioned. Again I note, all worked with VBOX and GA 6.1.2 or less and kernels until 5.4.

Please specify what would help to debug (log files, dmesg...). Will append next time.

Regards.

Rather then immediately jumping into the joys of nailing that slackware manually onto my platter, would you perform 3 checks for me please?

1) is that Slackware thingy running systemd at all? 2) if yes, what is the content in your shell from the environment

variable XDG_SESSION_TYPE

3) Are you using Xorg or Xwayland? From your comments I vaguely

take that you are using Xorg indeed, right?

We know this all worked with 6.1.2 and broke with 6.1.4 and 6.1.8 should return the working state for all Xorg use cases modulo regression bug #19590

comment:41 in reply to: ↑ 36 Changed 3 months ago by yuhp

Replying to fbatschu:

In general this has been fixed in the new release 6.1.8 for guests running Xorg (not Xwayland).

However, see also #19590

Why you ignore Xwayland? Debian 10 default installation use Xwayland. Xwayland works with 6.1.2 and 6.1.4.

Changed 2 months ago by zd59

Slackware64-current running XORG

comment:42 in reply to: ↑ 40 Changed 2 months ago by zd59

Replying to fbatschu:

Rather then immediately jumping into the joys of nailing that slackware manually onto my platter, would you perform 3 checks for me please?

1) is that Slackware thingy running systemd at all? 2) if yes, what is the content in your shell from the environment

variable XDG_SESSION_TYPE

3) Are you using Xorg or Xwayland? From your comments I vaguely

take that you are using Xorg indeed, right?

We know this all worked with 6.1.2 and broke with 6.1.4 and 6.1.8 should return the working state for all Xorg use cases modulo regression bug #19590

1.) Slackware64-current is running system.d

2.) variable XDG_SESSION_TYPE - no sign of it:

[~] # env |grep XDG
XDG_CONFIG_DIRS=/etc/xdg:/etc/kde/xdg
XDG_CURRENT_DESKTOP=KDE
XDG_SESSION_COOKIE=slack.doma-1590050247.597470-689610040
XDG_RUNTIME_DIR=/var/run/user/0
root on slack Thu May 21 10:49 AM

3.) XORG or Xwayland? Yes it's XORG. Take a look a picture I attached: XORG.jpg - Slackware64-current running XORG

And yes, graphics controller is VMSVGA. Auto-resize Guest Display is GRAY - not clickable.

As soon as I replace it with VBoxSVGA the window resize works.

comment:43 follow-up: ↓ 44 Changed 2 months ago by zd59

I also have another Slackware64-current with Xfce on top of XORG.

After VBOX upgrade to 6.1.8 (also Guest Additions)

Xfce-4.12 + VBoxSVGA driver: The parent session seems to be non X11.. Window resize do not work immediately, X11 should be restarted. Auto-resize guest is not gray

Xfce-4.12 + VMSVGA driver: The parent session seems to be non X11.. Window resize do not work, Auto-resize guest is gray.

And another complain: If in a /lib/modules/<kernel_version>/misc are VBOX compiled modules, the installer do not compiles new drivers. And those modules ARE NOT uninstalled with VBOX uninstall program.

comment:44 in reply to: ↑ 43 ; follow-up: ↓ 45 Changed 2 months ago by fbatschu

Replying to zd59:

I also have another Slackware64-current with Xfce on top of XORG.

After VBOX upgrade to 6.1.8 (also Guest Additions)

Xfce-4.12 + VBoxSVGA driver: The parent session seems to be non X11.. Window resize do not work immediately, X11 should be restarted. Auto-resize guest is not gray

Xfce-4.12 + VMSVGA driver: The parent session seems to be non X11.. Window resize do not work, Auto-resize guest is gray.


As hinted above, you need to fix for:
#19590: VBoxClient: The parent session seems to be non-X11

comment:45 in reply to: ↑ 44 ; follow-up: ↓ 46 Changed 2 months ago by zd59

Replying to fbatschu:

Replying to zd59:

I also have another Slackware64-current with Xfce on top of XORG.

After VBOX upgrade to 6.1.8 (also Guest Additions)

Xfce-4.12 + VBoxSVGA driver: The parent session seems to be non X11.. Window resize do not work immediately, X11 should be restarted. Auto-resize guest is not gray

Xfce-4.12 + VMSVGA driver: The parent session seems to be non X11.. Window resize do not work, Auto-resize guest is gray.


As hinted above, you need to fix for:
#19590: VBoxClient: The parent session seems to be non-X11

Sorry fbatschu, but this is NOT truth. I've posted a window screenshot above to prove, X11 is running and NOT Wayland. Slackware-current is not even prepared (compiled) for a Wayland. The statement

The parent session seems to be non-X11

is a prove of a failure of Virtualbox to detect X11 is running. Please accept that as real truth.

The state of XDG_SESSION_TYPE variable can not be the way, VBOX detect X11/Wayland, as on some distributions it is absent.

comment:46 in reply to: ↑ 45 Changed 2 months ago by fbatschu

Replying to zd59:

Replying to fbatschu:

Replying to zd59:

I also have another Slackware64-current with Xfce on top of XORG.

After VBOX upgrade to 6.1.8 (also Guest Additions)

Xfce-4.12 + VBoxSVGA driver: The parent session seems to be non X11.. Window resize do not work immediately, X11 should be restarted. Auto-resize guest is not gray

Xfce-4.12 + VMSVGA driver: The parent session seems to be non X11.. Window resize do not work, Auto-resize guest is gray.


As hinted above, you need to fix for:
#19590: VBoxClient: The parent session seems to be non-X11

Sorry fbatschu, but this is NOT truth. I've posted a window screenshot above to prove, X11 is running and NOT Wayland. Slackware-current is not even prepared (compiled) for a Wayland. The statement

The parent session seems to be non-X11

is a prove of a failure of Virtualbox to detect X11 is running. Please accept that as real truth.

The state of XDG_SESSION_TYPE variable can not be the way, VBOX detect X11/Wayland, as on some distributions it is absent.

Read bug #19590

comment:47 follow-up: ↓ 48 Changed 2 months ago by zd59

fbatschu are you serious?

So stupid X11/Wayland check by VBOX. Reading the forum reveal that XDG_SESSION_TYPE is not a standard env variable! And now the most simple solution, that solved "no window resize" failure:

file /etc/profile - add here:

export XDG_SESSION_TYPE="x11"

and reboot.

Now "window resize" works.

Sometimes the simplest things are so obvious, that nobody to think about it!

Now both my VBOX Slackware machines have a resizable windows. And best, this solution works for all Linux distributions running X11, not only Slackware.

comment:48 in reply to: ↑ 47 Changed 2 months ago by fbatschu

Replying to zd59:

fbatschu are you serious?

So stupid X11/Wayland check by VBOX. Reading the forum reveal that XDG_SESSION_TYPE is not a standard env variable! And now the most simple solution, that solved "no window resize" failure:

file /etc/profile - add here:

export XDG_SESSION_TYPE="x11"

and reboot.

Now "window resize" works.

Sometimes the simplest things are so obvious, that nobody to think about it!

Now both my VBOX Slackware machines have a resizable windows. And best, this solution works for all Linux distributions running X11, not only Slackware.


You could have tried reading and understanding bug #19590 and then using the corresponding test builds mentioned in there which contain the fix to this problem.

Of course you can also do whatever you like in your shell and feel positive about it.

comment:49 Changed 2 months ago by zd59

You are right. But this is a fast and simple solution without any installation. Might help others. I'll wait for a release of a new VBOX version. Thanks for a code that reveal x11 check, so I was able to find that simple solution.

comment:50 follow-up: ↓ 52 Changed 2 months ago by arQon

(In the hope that the devs are still willing to wade through all the ranting in this ticket...)

The fix in 6.1.8 isn't quite there yet, it seems: my Ubuntu 16.04 guest still needs a VT switch, Host-F, or similar "forced refresh" manual trigger to get the initial desktop display to happen.

VMSVGA, 128MB, 3D *dis*abled Mesa 18.0.5, kernel 4.15.0-101-generic

It's an X desktop, with the environment variable VBox is looking for present, so I'm not sure why the initial display isn't happening. If you need further info or would like me to try a potential fix, just let me know.

Thanks.

comment:51 Changed 2 months ago by arQon

and, OUCH - I windowed the VM to see if the various resolutions were greyed out, out of curiosity. They weren't, but mousing over them caused the VM to lock up, hard. It failed to respond to an ACPI Shutdown sent from the VBox Manager, which then greyed out the "Close" option, and the VM process had to be killed from the host.

There's nothing useful that I can see in the log: just a couple of "got a hint" lines from the Host-F itself, but I've saved a copy of it in case it's helpful. I realise this ticket is about resizing not working, not "even thinking about resizing causes the VM to hard lock" :P, but yeah - it seems there's something very nasty indeed lurking in that code still.

comment:52 in reply to: ↑ 50 Changed 2 months ago by fbatschu

Replying to arQon:

(In the hope that the devs are still willing to wade through all the ranting in this ticket...)

The fix in 6.1.8 isn't quite there yet, it seems: my Ubuntu 16.04 guest still needs a VT switch, Host-F, or similar "forced refresh" manual trigger to get the initial desktop display to happen.

VMSVGA, 128MB, 3D *dis*abled Mesa 18.0.5, kernel 4.15.0-101-generic

It's an X desktop, with the environment variable VBox is looking for present, so I'm not sure why the initial display isn't happening. If you need further info or would like me to try a potential fix, just let me know.


This bug is about _screen resizing_ what you describe seems to be different problem. Fwiw I've tested 16.04 with 6.1.8 wihtout problems in the follow up bug #19590, https://www.virtualbox.org/ticket/19590#comment:11

So please could you be more verbose what this actually means:

"guest still needs a VT switch, Host-F, or similar "forced refresh" manual trigger to get the initial desktop display to happen."

and if it is not related to resizing the screen while using the VMSVGA adapter, it should probably handled outside the scope of this bug here.

comment:53 Changed 2 months ago by gombara

As of revision 138395 GA should be able resize virtual monitors on Wayland guests as well. That is when vmsvga graphics adapter is used. The new GAs are available in https://www.virtualbox.org/wiki/Testbuilds.

comment:54 Changed 2 months ago by JasonM

vbox/ga 138395 is not working for openSUSE Tumbleweed guest on Win10 host. It always snaps back to 800x600. The only thing that works for me is GA 6.1.4 so far. Guest is x11, kernel 5.6.14, KDE 5.18.5, VMSVGA no 3D. Host is Win10.

Solution: kill kscreen: "qdbus-qt5 org.kde.kded5 /kded unloadModule kscreen"

Solution: preferred mode:  https://bugs.kde.org/show_bug.cgi?id=407058#c24

Last edited 2 months ago by JasonM (previous) (diff)

comment:55 Changed 2 months ago by fbatschu

The new Xwayland enabling fixes have been verified on the following platforms so far:

All are now resizing capable running with Gnome/Xwayland:

CentOS 8.1
OpenSuse Tumbleweed
Fedora Rawhide
Fedora 31
Oracle Linux 8.2
Ubuntu 19.04

If it still doesn't work for you, it is very likely because you are using KDE/kscreen where the screen gets resized and kscreen immediately forces it back. Good to talk to the kscreen folks about it.

Last edited 2 months ago by fbatschu (previous) (diff)

comment:56 Changed 2 months ago by Feline

Unfortunately full-screen still doesn't work with X11 guests though. I have a number of Debian 10 guests that run full screen. Up to VirtualBox 6.1.4, the login screen was full screen and once the logon details were entered, the screen was still set to full screen.

Starting with VirtualBox 6.1.6 and continuing with VirtualBox 6.1.8, the logon screen is now 800 x 600 and once the logon details are entered, the desktop goes blank. This is the case with the GA's for 6.1.6, 6.1.8 and the latest test build for GA 6.1.9. If you subsequently, use View -> Full-screen mode (to switch back to windowed), the guests desktop is restored. Using View -> Full-screen mode will then restore the guest desktop to full-screen. However, the next time you reboot the guest, it's broken again. Guests are Debian 10 with the Mate desktop.

comment:57 Changed 7 weeks ago by marvin_littlewood

See: comment:56 and comment:28

Feline and I have identical problems, except that I am using VBox 6.1.10. In our usage, there remains a problem with VBox resizing the screen from 800x600 to full size pre login and with seeing a black screen after login. In my case, the last working version was VBox 6.1.4. Throughout, my guest has been: XUbuntu running on X11.

@gombara: Would you prefer that a new bug report is opened?

comment:58 Changed 7 weeks ago by gombara

Hi Marvin. I know that loggin into full screen results in a black screen. Going out and in from/to fullscreen mode restores the picture. I am yet to find the cause and fix for this.

comment:59 Changed 7 weeks ago by Feline

I've already opened another ticket for this, see https://www.virtualbox.org/ticket/19640

comment:60 in reply to: ↑ 32 Changed 6 weeks ago by vmvarga

Replying to guurpi:

Hi, I had the same issue:

  • Windows 10 host, VBox 6.1.6 r137129, GA 6.1.6 as shipped with VBox
  • Debian 9 client with Xorg Xserver
  • VMSVGA with 3D acceleration: log-in screen smaller than normal, then blank screen.
  • VBoxVGA without 3D accel: all good

By chance I increased the assigned video memory for the VM from 12 MB to 32 MB. Now -with VMSVGA- all looks quite normal, no blank screen anymore. Well, the automatic resizing doesn't work. That's no surprise as the VBoxClient refuses the --display option. (Btw. why is that?)

It seems that new VBoxClient doesn't support --display option and doesn't support --vmsvga-x11

root@kali:~# VBoxClient --help
Usage: VBoxClient --clipboard|--draganddrop|--checkhostversion|--seamless|--vmsvga[-d|--nodaemon]                                                                                        
Starts the VirtualBox DRM/X Window System guest services.                                                                                                                                
                                                                                                                                                                                         
Options:
  --clipboard        starts the shared clipboard service
  --draganddrop      starts the drag and drop service
  --checkhostversion starts the host version notifier service
  --seamless         starts the seamless windows service
  --vmsvga           starts VMSVGA dynamic resizing for x11/Wayland guests
  -f, --foreground   run in the foreground (no daemonizing)
  -d, --nodaemon     continues running as a system service
  -h, --help         shows this help text
  -v, --verbose      increases logging verbosity level
  -V, --version      shows version information

root@kali:~# VBoxClient --version
6.1.10_Debianr138449

So after modifying /usr/bin/VBoxClient-all and using --vmsvga instead of --vmsvga-x11 personally i have working resizing again.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use