Bug 1077453 - No render acceleration with vmware driver
Summary: No render acceleration with vmware driver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vmware
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-18 03:40 UTC by Jacob Swanson
Modified: 2014-07-16 08:09 UTC (History)
13 users (show)

Fixed In Version: xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20
Clone Of:
Environment:
Last Closed: 2014-06-22 23:55:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jacob Swanson 2014-03-18 03:40:05 UTC
Description of problem:
Render acceleration is not working for VMware Player guest.

Version-Release number of selected component (if applicable): 20


How reproducible:
Very easy

Steps to Reproduce:
1. Install Fedora 20
2. Login

Actual results:
Software rendering is used instead of accelerated rendering.

Expected results:
Render acceleration is used.

Additional info:
Snippet of Xorg.0.log that appears to be relevant.
[     6.366] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[     6.432] (II) vmware(0): Gallium3D XA version: 2.0.0.
[     6.432] (WW) vmware(0): Expecting 1.0.x >= XA version < 2.0.0.
[     6.432] (WW) vmware(0): No render acceleration available.
[     6.433] (WW) vmware(0): Skipped initialization of direct rendering due to lack of render acceleration.
[     6.433] (--) vmware(0): Render acceleration is disabled.
[     6.433] (==) vmware(0): Rendercheck mode is disabled.
[     6.433] (--) vmware(0): Direct rendering (3D) is disabled.
[     6.433] (==) vmware(0): Backing store disabled
[     6.433] (==) vmware(0): Silken mouse enabled
[     6.433] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[     6.435] (==) vmware(0): DPMS enabled
[     6.435] (II) vmware(0): No 3D acceleration. Not setting up textured video.

Comment 1 Kevin Cameron 2014-03-21 22:56:51 UTC
The same issue is occurring with VMware Workstation 10 as well. Render acceleration works again after downgrading xorg-x11-drv-vmware to 13.0.1-2.fc20 and mesa-libxatracker to 9.2.3-1.20131114.fc20.

Comment 2 P.J. Hinton 2014-03-27 00:33:10 UTC
Observed with VMWare Player 6.0.1 build-1379776 and Fedora 20 with latest RPM updates as of 2014-03-26:

Version of driver RPM: 

xorg-x11-drv-vmware-13.0.1-3.20131207gita40cbd7b.fc20.x86_64 

Excerpt from Xorg.0.log:

[    55.108] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[    56.321] (II) vmware(0): Gallium3D XA version: 2.0.0.
[    56.321] (WW) vmware(0): Expecting 1.0.x >= XA version < 2.0.0.
[    56.321] (WW) vmware(0): No render acceleration available.
[    56.323] (WW) vmware(0): Skipped initialization of direct rendering due to lack of render acceleration.
[    56.323] (--) vmware(0): Render acceleration is disabled.
[    56.323] (==) vmware(0): Rendercheck mode is disabled.

There is also a thread at fedoraforum.org where others have experienced this problem.

http://forums.fedoraforum.org/showthread.php?t=298015

This problem manifests itself in GNOME with sluggish GUI responsiveness and very high CPU usage for the gnome-shell process.

Comment 3 Sitsofe Wheeler 2014-04-18 04:08:37 UTC
I'm seeing this too and as stated above it happened after an update a few months ago. The above excerpt makes it look like the mesa-libxatracker version is out of sync with the xorg-x11-drv-vmware version. Here are the rpms on my system at the moment:

mesa-libxatracker-10.0.4-1.20140312.fc20.x86_64
xorg-x11-xauth-1.0.7-4.fc20.x86_64
xorg-x11-drv-vesa-2.3.2-10.fc20.x86_64
xorg-x11-server-common-1.14.4-7.fc20.x86_64
xorg-x11-drv-vmmouse-13.0.0-6.fc20.x86_64
xorg-x11-font-utils-7.5-18.fc20.x86_64
xorg-x11-drv-modesetting-0.8.0-2.fc20.x86_64
xorg-x11-proto-devel-7.7-9.fc20.noarch
xorg-x11-drv-vmware-13.0.1-3.20131207gita40cbd7b.fc20.x86_64
xorg-x11-xkb-utils-7.7-8.fc20.x86_64
xorg-x11-utils-7.5-12.fc20.x86_64
xorg-x11-drv-synaptics-1.7.4-6.fc20.x86_64
xorg-x11-xinit-1.3.2-9.fc20.x86_64
xorg-x11-drv-fbdev-0.4.3-10.fc20.x86_64
xorg-x11-drv-evdev-2.8.2-1.fc20.x86_64
xorg-x11-fonts-Type1-7.5-9.fc20.noarch
xorg-x11-glamor-0.5.1-3.20140115gitfb4d046c.fc20.x86_64
xorg-x11-drv-qxl-0.1.1-3.fc20.x86_64
xorg-x11-server-Xorg-1.14.4-7.fc20.x86_64
xorg-x11-server-utils-7.7-2.fc20.x86_64

This bug is probably related to Bug #1081563 . There's a link there to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1271186 that suggests a newer xserver-xorg-video-vmware (Debian/Ubuntu's package name) resolved the problem in Ubuntu 14.04.

Peter:
Any ideas on this one?

Comment 4 Sitsofe Wheeler 2014-04-24 15:34:45 UTC
(It's worth noting that
yum downgrade mesa-libxatracker xorg-x11-drv-vmware
works around the problem by using an older driver that doesn't have this particular problem (but may have other problems of its own))

Comment 5 Sitsofe Wheeler 2014-05-15 08:16:51 UTC
(Downgrading is now a more painful after the latest round of updates. Something like
yum downgrade mesa-libxatracker.x86_64 xorg-x11-drv-vmware mesa-dri-drivers llvm-libs llvm clang
was needed for me...)

Comment 6 agilmore2 2014-05-19 12:50:04 UTC
Also failing for me. yum downgrade as above allows for accelerated rendering once more.

Comment 7 Darren Hart 2014-05-20 22:13:15 UTC
I thought this might be related to Bug 1044118. I downgraded mesa-libxatracker-devel and friends to 9.x which allowed me to build a more recent xorg-x11-drv-vmware package, but it didn't help. I can verify that with the newer package the acceleration is enabled, but the background corruption and general sluggishness persists.

$ sudo yum downgrade  mesa-libxatracker llvm-libs mesa-dri-drivers xorg-x11-drv-vmware mesa-libxatracker-devel

Then I grabbed the srcrpm and built from a more recent version:
[dvhart@localhost SPECS]$ diff xorg-x11-drv-vmware.spec.orig xorg-x11-drv-vmware.spec
4,5c4,5
< %define gitdate 20131207
< %define gitversion a40cbd7b
---
> %define gitdate 20140115
> %define gitversion 8da981712f62050076cff53e1b40ed1e307fcca8

After installing that version, accel is enabled:

[    16.567] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[    16.578] (II) vmware(0): Gallium3D XA version: 1.0.0.
[    16.579] (II) vmware(0): Path of drm device is "/dev/dri/card0".
[    16.579] (II) vmware(0): [DRI2] Setup complete
[    16.579] (II) vmware(0): [DRI2]   DRI driver: vmwgfx
[    16.579] (--) vmware(0): Render acceleration is enabled.
[    16.579] (==) vmware(0): Rendercheck mode is disabled.
[    16.579] (--) vmware(0): Direct rendering (3D) is enabled.
[    16.579] (==) vmware(0): Direct presents are disabled.
[    16.579] (==) vmware(0): Hardware only presents are disabled.
[    16.579] (==) vmware(0): Backing store disabled
[    16.579] (==) vmware(0): Silken mouse enabled
[    16.579] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.

But, as stated in the other bug, I still see the background not getting redrawn and the display responding very slowly.

Comment 8 Darren Hart 2014-05-20 22:22:31 UTC
Building 13.0.2 of xorg-x11-drv-vmware with the same mesa-libxatracker-devel downgrade doesn't help either.

I'm happy to help test or try building different combinations of things.

It seems the mesa-libxatracker in Fedora 20 is too new to build the latest vmware driver, but even built with the older version, the driver has some serious usability bugs that make Fedora 20 a bad choice for a vmware fusion (and I believe Workstation) guest.

Comment 9 Sitsofe Wheeler 2014-05-23 04:24:24 UTC
Darren:
At this stage we're almost certainly better off filing a bug against the upstream xorg vmware saying that it is not possible to have a new mesa-libxatracker with xorg-x11-drv-vmware...

Comment 10 Hans de Goede 2014-06-09 13:36:32 UTC
Please don't put bugs in needinfo with the generic xgl-maint alias.

Comment 11 Sitsofe Wheeler 2014-06-09 18:55:33 UTC
Sorry Hans - I only did that because that was who it was assigned to and there hadn't been a reply from a Red Hat employee until yours.

I actually filed this upstream yesterday (https://bugs.freedesktop.org/show_bug.cgi?id=79785 ) and here's the reply:

"[...]to build with fedora 20 which uses the old XWayland code, you'll need the very latest xf86-video-vmware git master

If that doesn't work for you, please report back."

Could we have a git build of xorg-x11-drv-vmware to test?

Comment 12 Hans de Goede 2014-06-13 11:39:51 UTC
Here is a scratch build of the latest git master code for F-20:
http://koji.fedoraproject.org/koji/taskinfo?taskID=7042745

Note currently it is still building, should be ready in 15 minutes or so.

Please let me know if this fixes things then I'll create an official update bumping the driver to the latest upstream.

Comment 13 Sitsofe Wheeler 2014-06-13 16:50:55 UTC
I actually built a driver from 4e378a730d2d2deffc915af2a3d013d2a994a1b0 yesterday which worked so I have high hopes for the scratch build...

Comment 14 Sitsofe Wheeler 2014-06-13 17:10:08 UTC
https://kojipkgs.fedoraproject.org//work/tasks/2746/7042746/xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20.x86_64.rpm works for me and has acceleration (a brief reboot test has been done). WebGL is a bit flakey but that may have always been the case. What are the results for others?

Comment 15 Hans de Goede 2014-06-13 18:22:14 UTC
Thanks for the test, that is good enough for me, I'm preparing an official update to the latest git to fix this.

Comment 16 Fedora Update System 2014-06-13 18:23:21 UTC
xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20

Comment 17 Fedora Update System 2014-06-15 01:51:24 UTC
Package xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7390/xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20
then log in and leave karma (feedback).

Comment 18 Fedora Update System 2014-06-22 23:55:15 UTC
xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 19 Carlo Papaleo 2014-06-23 07:52:07 UTC
Problem still seem to persist on my system

Comment 20 Carlo Papaleo 2014-06-23 07:56:07 UTC
Must I do something else beside updating the system package with yum update? (and rebooting)

Comment 21 Sitsofe Wheeler 2014-06-23 09:58:09 UTC
Carlo:
At a bare minimum you would need to know that
rpm -q xorg-x11-drv-vmware
is producing the version number of the updated package reported in this bug. If it is not then it could simply be the mirror your updates arrived from has not updated yet...

Comment 22 Carlo Papaleo 2014-06-23 21:38:50 UTC
Sitsofe: I know, in fact it says: xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20.x86_64

Comment 23 Sitsofe Wheeler 2014-06-24 05:53:56 UTC
Carlo:
Can you attach your Xorg.0.log?

Comment 24 Carlo Papaleo 2014-06-24 09:40:28 UTC
Sure! Here you go:
http://paste.fedoraproject.org/112522/02757140

Comment 25 Sitsofe Wheeler 2014-06-24 14:56:23 UTC
Carlo:
Your graphics card is an AMD/ATI of some description:
[     7.884] (II) RADEON: Driver for ATI Radeon chipsets:
        ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),

so this particular bug (1077453 which is only for VMware guests) is not for you I'm afraid...

Comment 26 Carlo Papaleo 2014-06-24 15:18:52 UTC
It's a (msi) AMD Readon HD 6850... Why do you say it is not for me? I'm expecting problems of No hardware acceleration while opening VMWare machines... isn't this the issue?

Comment 27 Carlo Papaleo 2014-06-24 15:20:05 UTC
(In particular I'm referring to Windows 7 virtual machines)

Comment 28 Carlo Papaleo 2014-06-24 15:23:40 UTC
(sorry for multiple posts) Maybe you needed the Xorg.0.log of the virtual machine? Being Windows 7 installed in it, it obviously isn't there in that case... I sent you the one from the host system

Comment 29 Sitsofe Wheeler 2014-06-24 17:37:01 UTC
Carlo:
Yes, your host is the one running Linux. This issue is about Linux running as a VMware guest...

Comment 30 Carlo Papaleo 2014-06-24 21:32:50 UTC
Oh OK, sorry...

Comment 31 martin.forstner 2014-07-15 14:39:28 UTC
same here. just upgraded from fc18 to fc20. using VMWare. having up to 100% cpu usage doing only typing. :(

Comment 32 Sitsofe Wheeler 2014-07-16 08:07:44 UTC
Martin:
Please attach (don't paste into the comment box!) your Xorg.0.log.

Comment 33 martin.forstner 2014-07-16 08:09:31 UTC
Sitsofe:
Sorry, problem solved. Installing "xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc2" helped. Thnx


Note You need to log in before you can comment on or make changes to this bug.