VMSVGA graphics controller issue in VirtualBox 6.1.0 r135406

[agb2008]

I've got problem with current VirtualBox 6.1.0 r135406 x64 installation on Windows 10 Pro x64 host workstation and
linux x64 guest system... With previous 6.0.x release everything seems to be working fine, but in current one I can't
use 3D graphics acceleration and VMSVGA graphics controller (recommended setting now) at all - because I am getting
640x480 resolution in my guest linux system that I can't change... Latest VirtualBox extension pack installed. Latest
VirtualBox guest additions compiled in my guest linux x64 system (CenOS 6.5, 6.9, GosLinux IC4, RosaLinux R11 and few
others that I tried). Tested on two different Windows 10 Pro x64 host workstations - absolutely the same results.
To be able to use my guest workstation in VirtualBox I have to select VBoxSVGA graphics controller and remove
3D acceleration option - only in that case I could set correct resolution that I want and proper resolution auto-scale option
working...
Because as I said this problem noted on different workstations and different gust linus systems I could suggest that
it's somehow related to current implementation of VMSVGA driver. Could you please advice if any solution exist for this
issue or I should just wait for next VirtualBox build and hope that it would be resolved there ?

[Whiskeyjack]

This looks very much like a known problem we had (and still have to some extend) with resizing and multi-monitor handling on Linux with VMSVGA adapter. The situation has been much improved in our development branch and upcoming 6.1.x release will include these fixes. I'd suggest you try the said release once it is out. Until then there is not much you can do about it.

[agb2008]

Unfortunately in new version that just released 6.1.2 r135662 problem that I mention still exist. And solution only to use VBoxSVGA adapter without option 3D acceletation switched on.
Looks like I would have to find a way to downgrade to 6.0.x VirtualBox release - because with current settings 3D graphics performance not good enough. I was waiting for this maintenance release with hope that problem would be solved...

This looks very much like a known problem we had (and still have to some extend) with resizing and multi-monitor handling on Linux with VMSVGA adapter. The situation has been much improved in our development branch and upcoming 6.1.x release will include these fixes. I'd suggest you try the said release once it is out. Until then there is not much you can do about it.

[Whiskeyjack]

Did you update the guest additions?

Unfortunately in new version that just released 6.1.2 r135662 problem that I mention still exist. And solution only to use VBoxSVGA adapter without option 3D acceletation switched on.
Looks like I would have to find a way to downgrade to 6.0.x VirtualBox release - because with current settings 3D graphics performance not good enough. I was waiting for this maintenance release with hope that problem would be solved...

This looks very much like a known problem we had (and still have to some extend) with resizing and multi-monitor handling on Linux with VMSVGA adapter. The situation has been much improved in our development branch and upcoming 6.1.x release will include these fixes. I'd suggest you try the said release once it is out. Until then there is not much you can do about it.

[agb2008]

Whiskeyjack: Of cause I did. Several experiments were done - but unfortunately still the same problem with VMSVGA adapter (with or without 3D graphics acceleration option).
Have to switch once again back to VBoxSVGA adapter without 3D graphics acceleration. Guest and host systems were rebooted a couple of times, guest additions were recompiled as well. Several attempts were made. Also I have to mention that suggested solution that suppose to be working as workaround (running command: VBoxClient -vf --vmsvga as root user) for Gentoo linux got no effect in my case (tested on CentOS 6.6 system).

Did you update the guest additions?

Unfortunately in new version that just released 6.1.2 r135662 problem that I mention still exist. And solution only to use VBoxSVGA adapter without option 3D acceletation switched on.
Looks like I would have to find a way to downgrade to 6.0.x VirtualBox release - because with current settings 3D graphics performance not good enough. I was waiting for this maintenance release with hope that problem would be solved...

This looks very much like a known problem we had (and still have to some extend) with resizing and multi-monitor handling on Linux with VMSVGA adapter. The situation has been much improved in our development branch and upcoming 6.1.x release will include these fixes. I'd suggest you try the said release once it is out. Until then there is not much you can do about it.

[hamishmb]

I have the same problem on older Ubuntu VMs on a Mint 19.3 host. Interestingly it seems to work okay with Ubuntu 20.04 (daily build), though X takes a while to start.

On older VMs I get a non-resizable 4K display that runs painfully slowly, or X doesn't start at all.

[mightbetrue]

I used the VMSVGA driver with 6.0.16, 6.1.0 and 6.1.2. I have 2x4K screens connected to my laptop and run virtualbox on both screens - works quite fast and the screens are resizable.. though, this is until the exception pops up and kills the vm.

Are you sure you installed the `xserver-xorg-video-vmware` package? If the package is not available, you could try to install the `open-vm-tools-desktop` package.

A good way to reproduce the problem of the VMSVGA implemention is to run`glmark2`. Its jellyfish animation always results in an exception and instantly killed vm for me.

[juozas]

I have the same issue when using VMSVGA with 3D acceleration enabled. The graphical mode of the OS (Ubuntu 18.04 LTS with latest updates) does not load at all when booting. Checking dmesg output I see a bunch of error messages near end of output in dmesg output, uninstalling video driver and updating OS packages to latest version doesn't help at all.

Host: Ubuntu 18.04.4 LTS, Pentium(R) Dual-Core CPU E6300 @ 2.80GHz, 2 GB Ram
Video: NVIDIA GeForce 210, Driver 340.107
VirtualBox: 6.1.4 r136177 (Qt5.9.5)

Errors like below are shown when OS tries to load graphical interface (lightdm), some times repeating.

Code: Select all

[   18.941738] [drm:vmw_kms_new_framebuffer [vmwgfx]] *ERROR* Invalid surface format for requested mode.
[   18.941777] [drm:vmw_kms_fb_create [vmwgfx]] *ERROR* failed to create vmw_framebuffer: -22

Edit: Installing xserver-xorg-video-vmware like in above suggestion solves the issue, the problem was the driver that was missing in my os installation, w/o it graphics doesn't load at all :\ Also almost no problems reinstalling the virtualbox driver on Guest, boots ok after that.

[mingle]

Hi,

Just another one with a possibly related issue using the VMSVGA Graphics Controller.

When using the VBoxSVGA Graphics Controller I can select a much larger range of graphics resolutions, including one I REALLY need to use - 1600 x 900.

However, when I select the VMSVGA Graphics Controller there's no option to select 1600 x 900, plus a bunch of other resolutions are 'missing'.

Using VirtualBox 6.1.4 on Windows 10 Pro 64-bit Host, running Linux Mint 19.2/19.3 64-bit guests.

Is this something that can bit fixed/updated in a future release?

Cheers,

Mike.

[sergiomb]

Hi,
I also have troubles with VMSVGA ( https://bugzilla.redhat.com/show_bug.cgi?id=1789545 )

even adding /etc/X11/xorg.conf.d/01-Video.conf

Code: Select all

Section "Device"
  BoardName    "VirtualBox Graphics"
  Driver       "vmware"
  Identifier   "Device[0]"
  VendorName   "Oracle Corporation"
EndSection

and running /usr/bin/VBoxClient --vmsvga

I see this errors in dmesg

[ 18.868609] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 18.868621] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.132175] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.132183] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.652622] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.652639] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.883023] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.883035] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 24.046761] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 24.046789] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 26.228232] Denying userspace vmm call type 0x000051
[ 34.667906] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 34.667914] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

[DenisF]

Hello,
Get same here with:

00:00:03.082581 VirtualBox VM 6.1.6 r137129 win.amd64 (Apr 9 2020 19:01:29) release log
00:00:03.082585 Log opened 2020-04-15T14:12:42.036836600Z
00:00:03.082585 Build Type: release
00:00:03.082590 OS Product: Windows 10
00:00:03.082591 OS Release: 10.0.18363
00:00:03.082592 OS Service Pack:

Linux Arch 5.6.4-arch1-1 #1 SMP PREEMPT Mon, 13 Apr 2020 12:21:19 +0000 x86_64 GNU/Linux
linux 5.6.4.arch1-1
linux-headers 5.6.4.arch1-1
open-vm-tools 6:11.0.1-2
plasma-wayland-session 5.18.4.1-2
sddm-kcm 5.18.4.1-1
virtualbox-guest-utils 6.1.6-1

[ 3.562485] systemd[1]: Starting Load Kernel Module drm...
[ 3.624537] systemd[1]: modprobe@drm.service: Succeeded.
[ 3.625386] systemd[1]: Finished Load Kernel Module drm.
[ 4.637264] [drm] DMA map mode: Caching DMA mappings.
[ 4.637360] [drm] Capabilities:
[ 4.637361] [drm] Cursor.
[ 4.637362] [drm] Cursor bypass 2.
[ 4.637362] [drm] Alpha cursor.
[ 4.637362] [drm] 3D.
[ 4.637363] [drm] Extended Fifo.
[ 4.637363] [drm] Pitchlock.
[ 4.637364] [drm] Irq mask.
[ 4.637364] [drm] GMR.
[ 4.637365] [drm] Traces.
[ 4.637365] [drm] GMR2.
[ 4.637365] [drm] Screen Object 2.
[ 4.637367] [drm] Max GMR ids is 8192
[ 4.637367] [drm] Max number of GMR pages is 1048576
[ 4.637368] [drm] Max dedicated hypervisor surface memory is 393216 kiB
[ 4.637368] [drm] Maximum display memory size is 131072 kiB
[ 4.637369] [drm] VRAM at 0xe0000000 size is 131072 kiB
[ 4.637370] [drm] MMIO at 0xe8400000 size is 2048 kiB
[ 4.637388] [drm] It appears like vesafb is loaded. Ignore above error if any.
[ 4.640795] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.640796] [drm] No driver support for vblank timestamp query.
[ 4.640853] [drm] Screen Objects Display Unit initialized
[ 4.640942] [drm] width 1024
[ 4.640954] [drm] height 768
[ 4.640965] [drm] bpp 32
[ 4.641193] [drm] Fifo max 0x00200000 min 0x00001000 cap 0x00000355
[ 4.641200] [drm] DX: no.
[ 4.641201] [drm] Atomic: yes.
[ 4.641201] [drm] SM4_1: no.
[ 4.641217] [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message.
[ 4.643836] [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message.
[ 4.645884] fb0: switching to svgadrmfb from EFI VGA
[ 4.646806] fbcon: svgadrmfb (fb0) is primary device
[ 4.656482] [drm] Initialized vmwgfx 2.17.0 20200114 for 0000:00:02.0 on minor 0
[ 7.100636] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 7.100647] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 7.193821] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 7.193832] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 7.614311] [drm:vmw_kms_new_framebuffer [vmwgfx]] *ERROR* Invalid surface format for requested mode.
[ 7.614318] [drm:vmw_kms_fb_create [vmwgfx]] *ERROR* failed to create vmw_framebuffer: -22
[ 8.236350] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 8.236361] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 20.312539] [drm:vmw_kms_new_framebuffer [vmwgfx]] *ERROR* Invalid surface format for requested mode.
[ 20.312564] [drm:vmw_kms_fb_create [vmwgfx]] *ERROR* failed to create vmw_framebuffer: -22
[ 20.323418] [drm:vmw_kms_new_framebuffer [vmwgfx]] *ERROR* Invalid surface format for requested mode.
[ 20.323425] [drm:vmw_kms_fb_create [vmwgfx]] *ERROR* failed to create vmw_framebuffer: -22
[ 20.875692] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 20.875704] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 21.669708] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 21.669720] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.222775] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.222787] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.453925] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.453937] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.477910] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 22.477922] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

[Ratin]

4 years later - Same issue with Virtual box 7.0 / Ubuntu 2204.4