I've got the same situation with a similar environment: a NVidia card (Nouveau driver) on Fedora 16 / x86_64.

Fedora 16 is explicitly listed as a supported platform.  I do have 3D capacilities (per glxinfo, and the KDE desktop), yet VMware Workstation complains.

The 3D acceleration doesn't work for me also in the guest. Host: CentOS 6.3 x64, NVidia GT440 (with a driver from nvidia website), guest CentOS 6.3 x64.

vmware-tools installed in the guest, but the tools installer doesn't install any driver for xorg (version 1.10.6):

Distribution provided drivers for Xorg X server are used.

 

Skipping X configuration because X drivers are not included.

--clobber-xorg-modules option also ineffective. xorg using the vmwlegacy driver after a warning:

[    31.808] (II) LoadModule: "vmwgfx"
[    31.808] (WW) Warning, couldn't open module vmwgfx
[    31.808] (II) UnloadModule: "vmwgfx"
[    31.808] (II) Unloading vmwgfx
[    31.808] (EE) Failed to load module "vmwgfx" (module does not exist, 0)
[    31.808] (EE) vmware: Please ignore the above warnings about not being able to to load module/driver vmwgfx
[    31.808] (II) vmware: Using vmwlegacy driver everything is fine.
[    31.808] (II) LoadModule: "vmwlegacy"

I actually got 3D working in VMware Workstation 8.x and Player 4.x...but not with WS9/Player5.

I have almost the same harware as you:

- Optimus Intel HD3000/NVidia combo.

- Ubuntu 12.04 x64

To get 3D support with WS8...I had ti install the following:

- nvidia-current driver

- bumblebee

- driconf

Was able achive 3D support...including Aero working in a Windows 7 VM.

BUT....this combo does not work with WS9...... >:(

Anyone know how to get 3D back in WS9 for my VM's???

Thanks.

Hi. I have got:

- The infamous Combo nVIDIA Optimus / Intel cards (in a ASUS N55SF S1284V)

- Ubuntu 12.04

- VMware Workstation 9

- Bumblebee (and, as Bumblebee installer says, I do "sudo apt-get purge nvidia-current" and "sudo add-apt-repository ppa:ubuntu-x-swat/x-updates". This use newer nVIDIA drivers)

I think if Bumblebee is installed or not does not matter to VMware. But the nVIDIA drivers that Bumblebee install are important for VMware Workstation 9. Anyway you can install these drivers from Synaptic...

The following works for me and, sooner or later... crash:

1.- Add the following to the .vmx file:

mks.gl.allowBlacklistedDrivers = TRUE

(this tells VMware: yes, my card is actually good)

2.- Install from Synaptic::

libtxc-dxtn-s2tc-bin

libtxc-dxtn-s2tc0

This is a free S3 implementation of texture compression library for Mesa

3.- Open VMware Workstation 9 and run a Windows 7 VM, for example.

This works fine... until it breaks with the message:

"VMware Workstation unrecoverable error (svga):

Unexpected signal: 11.

A log file is available in blah, blah, blah..."

I correct myself:

I had forgotten to run VMware with optirum option (i.e. Bublebee): 

optirun /usr/bin/vmware

Now, runing VMware and Bumblebee, it seems to work. At least takes several minutes without breaking.

If this works, I may have found a solution! We will touch wood...

UPDATE:

Update: It also breaks running with optirun option

The "unrecoverable error" is now: (vcpu-2)

I'm on the same boat. Well technically not the same, but pretty close.

I'm running Debian on an optimus laptop, and 3d acceleration worked fine on workstation 8, but now it's broken.

I tried the

mks.gl.allowBlacklistedDrivers = "TRUE"

trick, but it failed. Workstation crashes.

I then (removed that non-working "fix" and) tried to run vmware using optirun, assuming it would then use the nvidia card and work fine.

That is still not the case. I still complains and disables 3d acceleration.

Log file attached.

Revelant messages:

2012-09-09T17:29:43.913Z| vmx| I120: DICT              mks.enable3d = TRUE

 

2012-09-09T17:29:44.227Z| vmx| I120: VMIOP: unable to find plugin "svga3d"

 

2012-09-09T17:29:44.234Z| mks| I120: Disabling 3D on this host due to presence of Mesa DRI driver.  Set mks.gl.allowBlacklistedDrivers = TRUE to override.
2012-09-09T17:29:44.462Z| mks| I120: GLXCreateContext Couldn't find a suitable FBConfig while creating context.
2012-09-09T17:29:44.465Z| mks| I120: Disabling 3D on this host due to presence of Mesa DRI driver.  Set mks.gl.allowBlacklistedDrivers = TRUE to override.
2012-09-09T17:29:44.466Z| mks| W110: GL-Backend: Failed to start GLBackend's screen compositor, GLBackend will stop working!
2012-09-09T17:29:44.466Z| mks| W110: MKS-RenderMux: Backend GLBackend<7F3D4C05C940> failed to start. Disabling.
2012-09-09T17:29:44.466Z| mks| I120: MKS-SLC: failed to start svga3d vmiop to render 3d.

 

2012-09-09T17:29:44.790Z| vmx| I120: Msg_Post: Warning
2012-09-09T17:29:44.790Z| vmx| I120: [msg.glX.noHardwareAccel] Hardware graphics acceleration is not available. As a result, this virtual machine may experience very low graphics performance. Follow the instructions provided by your graphics card vendor or Linux distribution in order to update your computer's OpenGL drivers.
2012-09-09T17:29:44.790Z| vmx| I120: ----------------------------------------
2012-09-09T17:29:44.841Z| vmx| I120: Msg_Post: Warning
2012-09-09T17:29:44.841Z| vmx| I120: [msg.mks.no3D] No 3D support is available from the host. The 3D features of the virtual machine will be disabled.
2012-09-09T17:29:44.842Z| vmx| I120: ----------------------------------------

 

2012-09-09T17:29:45.396Z| mks| I120: Disabling 3D on this host due to presence of Mesa DRI driver.  Set mks.gl.allowBlacklistedDrivers = TRUE to override.

 

2012-09-09T17:29:53.247Z| vcpu-0| I120: SVGA: Unregistering IOSpace at 0x10f0
2012-09-09T17:29:53.247Z| vcpu-0| I120: SVGA: Unregistering MemSpace at 0xd0000000(0xd0000000) and 0xc8800000(0xc8800000)
2012-09-09T17:29:53.248Z| vcpu-0| I120: SVGA: Registering IOSpace at 0x10f0
2012-09-09T17:29:53.248Z| vcpu-0| I120: SVGA: Registering MemSpace at 0xd0000000(0xd0000000) and 0xc8800000(0xc8800000)
2012-09-09T17:29:53.249Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA Driver Version: 11.09.01.0000 - build-745082
2012-09-09T17:29:53.249Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA Caps: 0x007fc3e2 (3D, EXTENDED FIFO, GMR, GMR2)
2012-09-09T17:29:53.249Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA VRAM: 134217728, FIFO: 2097152
2012-09-09T17:29:53.249Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA Using GMR2, max pages=196608
2012-09-09T17:29:53.250Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA GMR: max IDs=64, max desc length=4096
2012-09-09T17:29:53.251Z| vcpu-0| I120: Guest: SVGA_MINI: MULTIMON: Pitch lock set to 15360

 

2012-09-09T17:29:54.320Z| vcpu-0| I120: Guest: SVGA_MINI: VMXInitialize
2012-09-09T17:29:54.321Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA FIFO Caps: 0x00000000
2012-09-09T17:29:54.321Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA FIFO HW Version: host 0x00000000, guest 0x00020001
2012-09-09T17:29:55.192Z| vcpu-0| I120: Guest: SVGA_MINI: IOCTL_VIDEO_SWITCH_DUALVIEW: id=0, enable=1, numDisplays=2
2012-09-09T17:29:55.192Z| vcpu-0| I120: Guest: SVGA_MINI: IOCTL_VIDEO_SWITCH_DUALVIEW: id=1, enable=0, numDisplays=2
2012-09-09T17:29:55.192Z| vcpu-0| I120: Guest: SVGA_MINI:    SECONDARY MONITOR enabled=0
2012-09-09T17:29:55.246Z| vcpu-0| I120: Guest: vmx_fb: tap: init
2012-09-09T17:29:55.254Z| vcpu-0| I120: Guest display topology changed: numDisplays 1
2012-09-09T17:29:55.254Z| vcpu-0| I120: SVGA enabling SVGA
2012-09-09T17:29:55.307Z| vcpu-0| I120: Guest: SVGA_MINI: SVGA Display Topology: SVGA enabled, FB size=12288000, topology=TRUE
2012-09-09T17:29:55.307Z| vcpu-0| I120: Guest: SVGA_MINI: numDisplayActive=1, Max: wxh=1280x800, pitchlock=15360
2012-09-09T17:29:55.307Z| vcpu-0| I120: Guest: SVGA_MINI: Offscreen: offset=0xbb8000, size=121929728
2012-09-09T17:29:55.307Z| vcpu-0| I120: Guest: SVGA_MINI:    DisplayId=0, primary=TRUE, screen object=UNUSABLE
2012-09-09T17:29:55.308Z| vcpu-0| I120: Guest: SVGA_MINI:    Display: offset=0x0, size=12288000, pitch=15360
2012-09-09T17:29:55.308Z| vcpu-0| I120: Guest: SVGA_MINI:    Backing Store: offset=0x0, size=0
2012-09-09T17:29:55.308Z| vcpu-0| I120: Guest: SVGA_MINI:       xy=0, 0
2012-09-09T17:29:55.309Z| vcpu-0| I120: Guest: SVGA_MINI:       wxhxd=1280x800x32
2012-09-09T17:29:55.310Z| vcpu-0| I120: Guest: vmx_fb: This is the primary surface: PPDEV e1883010
2012-09-09T17:29:55.310Z| vcpu-0| I120: Guest: vmx_fb: Display driver is out of sync with virtual hardware.  Disabling 3d.
2012-09-09T17:29:55.310Z| vcpu-0| I120: Guest: vmx_fb:   Current hardware revision: 0.0.
2012-09-09T17:29:55.311Z| vcpu-0| I120: Guest: vmx_fb:   Driver compiled against:   2.1.
2012-09-09T17:29:55.311Z| vcpu-0| I120: Guest: vmx_fb: Display Acceleration: DirectDraw:ok, Direct3D:disabled.
2012-09-09T17:29:55.311Z| vcpu-0| I120: Guest: vmx_fb:   Current hardware revision: 0.0.
2012-09-09T17:29:55.311Z| vcpu-0| I120: Guest: vmx_fb:   Driver compiled against:   2.1.
2012-09-09T17:29:55.311Z| vcpu-0| I120: Guest: vmx_fb: DrvGetDirectDrawInfo: Overlay flags set
2012-09-09T17:29:55.311Z| vcpu-0| I120: Guest: vmx_fb: DrvGetDirectDrawInfo: offset=0x0, wxh=1280x800, bpp=32, pitch=15360
2012-09-09T17:29:55.312Z| vcpu-0| I120: Guest: vmx_fb: This is the primary surface: PPDEV e1883010
2012-09-09T17:29:55.312Z| vcpu-0| I120: Guest: vmx_fb: Display driver is out of sync with virtual hardware.  Disabling 3d.
2012-09-09T17:29:55.312Z| vcpu-0| I120: Guest: vmx_fb:   Current hardware revision: 0.0.
2012-09-09T17:29:55.312Z| vcpu-0| I120: Guest: vmx_fb:   Driver compiled against:   2.1.
2012-09-09T17:29:55.312Z| vcpu-0| I120: Guest: vmx_fb: Display Acceleration: DirectDraw:ok, Direct3D:disabled.
2012-09-09T17:29:55.312Z| vcpu-0| I120: Guest: vmx_fb:   Current hardware revision: 0.0.
2012-09-09T17:29:55.313Z| vcpu-0| I120: Guest: vmx_fb:   Driver compiled against:   2.1.
2012-09-09T17:29:55.313Z| vcpu-0| I120: Guest: vmx_fb: DrvGetDirectDrawInfo: GMR DX heap disabled, size 0, available memory 805306368
2012-09-09T17:29:55.313Z| vcpu-0| I120: Guest: vmx_fb: DrvGetDirectDrawInfo: Overlay flags set
2012-09-09T17:29:55.313Z| vcpu-0| I120: Guest: vmx_fb: DrvGetDirectDrawInfo: offset=0x0, wxh=1280x800, bpp=32, pitch=15360
2012-09-09T17:29:55.314Z| vcpu-0| I120: Guest: vmx_fb: Caps_GetDeviceD3DCaps: CANAUTOGENMIPMAP off (0, HW v0 131073)
2012-09-09T17:29:55.314Z| vcpu-0| I120: Guest: vmx_fb: Caps_GetDeviceD3DCaps: MaxActiveLights=8
2012-09-09T17:29:55.314Z| vcpu-0| I120: Guest: vmx_fb: Caps_GetDeviceD3DCaps: MaxActiveLights=8
2012-09-09T17:29:57.624Z| vcpu-0| I120: HgfsChannelVmciConnectInternal: VMCI HGFS server session init complete and opened.

 

 

I don't understand why it still mentions the mesa driver. It should be using nvidia gl driver.

Any way to fix this and get 3D working?!

I guess I should have bought workstation 8. At least that one worked. Now I'm stuck.

bumping for a solution

Found a bit more info, but still no working solution for me

http://askubuntu.com/questions/181829/how-to-fix-opengl-error-for-vmware-workstation-9

mks.gl.allowBlacklistedDrivers = TRUE

And then also install the Mesa-libtxc_dxtn1 (aka the S3 texture compression)

(tried it and it didn't work for me)

http://unixblogger.wordpress.com/2012/09/06/vmware-workstation-9-is-out-and-it-doesnt-work-for-me/

I’ve downloaded the kernel packages for the latest Ubuntu 12.10 development release and installed it. [that has kernel 3.5]

 

Well, now I’m able to use my Fn keys and even my NVidia graphic card without any problems. But now, while I’m useing a 3.5 kernel, VMWare Workstation 9 refuses to starting up. I’m able to install, compile the modules and enter the licence key, but shortly after trying to work or to start a VM, I get a “stack trace flood” which causes my X Server to freeze.

 

I’ve tested the new submitted patch for kernel 3.5 and Workstation 9 on myself, but it doesn’t help for me, too. I always get the “stack trace flood” recently, after I started a virtual machine.

(I haven't tried this one)

It's very frustrating that I had WS 8 working but now WS 9 is completely foobared in Linux.

And still another problem:

I do not know if this is caused also by Optimus issue, but now (unlike with Workstation 8) constantly asks me to install the VMware Tools (well. .. I can't install something that is already installed, I simply "Repair" the previous VMWare Tools installation). This is quite annoying, and it happens in all the guests.

Are you this happens to you too?

Yes, that happens too.

But you can simply ignore it.

If the vmtools weren't working, then you would be limited to 640x480, but you don't (well at least I don't.  I can use any resolution I want in the windows xp guest).

The reply by ninjacoding, includes my reply on the ubuntu forum, i was hoping to get 3d acceleration in windows guest on a linux host.

I'm not sure what the issue is but mac os have had 3d acceleration in vmware for windows guests for quite sometime.

Anyone come across a solution for this? I'm tryin to get this working but it doesn't appear vmware gives a sh!t. They are happy to take from the open soucre community but don't give much back.

i've added the log file

rashm2k wrote:

 

The reply by ninjacoding, includes my reply on the ubuntu forum, i was hoping to get 3d acceleration in windows guest on a linux host.

I would suggest you install Workstation 8.x then...the Guest 3D support works fine with version 8.x on a Linux host.

The issues with 3D Guest support is with Workstation 9....

Good Luck.

I would suggest you install Workstation 8.x then...the Guest 3D support works fine with version 8.x on a Linux host.

The issues with 3D Guest support is with Workstation 9....

Good Luck.

Install Vmware Workstation 8 may be the solution, yes... but after paying over 100 € for the update, gives very bad feeling.

Anyway, by registering a new updated VMware Workstation, you lose the previos license (I understand...)

I hope (I want to believe, in other words...) there will soon be a patch that fixes the problem. There are many new laptops with nVIDIA Optimus + Linux: This is a significant percentage of the immediate future (this is not a "rare" configuration). Anyway... does anyone know if there is any way to know if the VMware team is working on a solution? It would be interesting to know.

Hopefully VMware does not delay the new patch, waiting for the hypothetical nVIDIA driver for Optimus/Linux. Where once worked Workstation 8 (i.e. Intel integrated graphics), now Workstation 9 should do it. The problem is that Workstation 8 on Linux worked best in the graphic field than Workstation 9 on Linux.

I dislike the feeling of having paid to have problems I did not have before.