Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#61183 - [virtualbox-guest-utils] missing dependency xf86-video-vmware

Attached to Project: Community Packages
Opened by nl6720 (nl6720) - Thursday, 27 December 2018, 08:32 GMT
Last edited by Christian Hesse (eworm) - Friday, 17 July 2020, 06:40 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No


VirtualBox 6.0 sets the Graphics Controller setting to "VMSVGA" (VMware SVGA graphic device) for Linux VMs. To use it with Xorg, the xf86-video-vmware driver is needed.
Please add xf86-video-vmware as a dependency to virtualbox-guest-utils.

From Xorg.0.log:

(EE) Failed to load module "vmware" (module does not exist, 0)

Additional info:
* package version(s)
* config and/or log files etc.
virtualbox-guest-utils 6.0.0-1

Steps to reproduce:
Try to start X with Graphics Controller set to "VMSVGA.
This task depends upon

Closed by  Christian Hesse (eworm)
Friday, 17 July 2020, 06:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  in SVN
Comment by Jakub Konior (grappas) - Sunday, 13 January 2019, 16:26 GMT
Also after installing xf86-video-vmware resolution autofit to window still doesn't seem to work.
Comment by Frank Vanderham (twelveeighty) - Thursday, 25 June 2020, 17:05 GMT
As at VirtualBox 6.1.10, xf86-video-vmware is not a dependency for using VMSVGA. The kernel's modesetting driver works "fine" (at least as tested with kernel 5.7.5). X itself runs fine and XrandR is able to change resolutions without problem.

There *is* a problem with "auto-resize Guest display" on VMSVGA, but installing xf86-video-vmware does not fix that. I don't think that's a packaging issue, but an upstream problem with either the kernel modesetting driver or VirtualBox.