Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-01-11, 12:33 PM   #1
Ranguvar
Registered User
 
Join Date: Oct 2010
Posts: 2
Default 270.18 beta driver conflicts with VMware Workstation 3D acceleration

When using the 270.18 beta driver in the host OS (in my case, Arch Linux), if you start Windows 7 as the guest in VMware Workstation (7.1.3 here), VMware will lock up towards the end of the login process. This is probably only if Aero is enabled, but perhaps not.

Using the 260.19.36 driver fixes the issue.

There's nothing in the NVIDIA or VMware logs that is helpful or remotely related, but I use an NVIDIA GeForce 9600 GT 512MB video card (64-bit OS).

As a side note, I found others with this same issue and workaround: https://bugs.launchpad.net/ubuntu/+s...rs/+bug/709331
Ranguvar is offline   Reply With Quote
Old 02-10-11, 04:44 AM   #2
named
Registered User
 
Join Date: Jan 2005
Posts: 10
Default Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

Same experience here.

Host: Gentoo 32bit, kernel 2.6.37, 8400GS (G98), 270.18 beta driver.
Guest: Windows XP 32 bit.

260.19.36 is OK.
named is offline   Reply With Quote
Old 02-15-11, 10:02 AM   #3
rg2003
Registered User
 
Join Date: Jan 2003
Posts: 18
Thumbs down Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

Same problem with 270.26. Win7 session in VMWare hangs with black screen after login prompt, and USB keyboard/mouse not responding. Does boot OK in 'safe mode'..
After hang, recovered by remote login and killing vmware-vmx, but keyboard still not responding correctly..
Reverted to 260.19.36, and everything works OK again...
dmesg output:
------
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 270.26 Sun Feb 13 22:30:06 PST
2011
/dev/vmmon[24510]: PTSC: initialized at 2399778000 Hz using TSC
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: usbfs: process 24510 (vmware-vmx) did not claim interface 0 before use
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: usbfs: process 24510 (vmware-vmx) did not claim interface 0 before use
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: usbfs: process 24510 (vmware-vmx) did not claim interface 0 before use
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: reset full speed USB device using uhci_hcd and address 6
usb 6-2: usbfs: process 24510 (vmware-vmx) did not claim interface 0 before use
-------
rg2003 is offline   Reply With Quote
Old 03-03-11, 05:26 AM   #4
kcrudup
Registered User
 
Join Date: Apr 2004
Location: Los Angeles, CA 90034
Posts: 96
Default Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

Just wanted to "Me, Three" this thread- any of the 270.* 64-bit betas on a Linux host and a WinXP VMWare 7.1.3 guest with 3D acceleration turned on will cause the XOrg input thread to lock up if after starting some programs like "Slingplayer". The system is still running, but the mouse pointer can't select anything, and you can't type. Had to SysRq-unRaw to get things back to where I could unfreeze the input layer to do a clean shutdown.

Switching to 260.19.36 (the latest stable) lets that setup run perfectly. I know, no bugreport, but 64-bit Linux, XOrg 1.7.6 kernel 2.6.37.1, VMWare 7.1.3 build-324285, GeForce 8600GS 512MB GPU RAM.
__________________
8600M GS 512MB (HP Pavilion dv9000 CTO)
kcrudup is offline   Reply With Quote
Old 03-06-11, 07:18 PM   #5
etherfish
Registered User
 
Join Date: Nov 2007
Posts: 18
Default Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

Still appears to be present in 270.30. Here's the backtrace from the vmware.log:

vmware-bug-report.log.gz attached.

Code:
Mar 05 15:38:37.694: mks| GLChain: Using GL_ARB_texture_rectangle textures
Mar 05 15:38:37.737: mks| GLHostCreateContext: Rendering is direct.
Mar 05 15:38:37.757: mks| VMGL Panic: *** Caught signal 6 in glXMakeContextCurrent() ***
Mar 05 15:38:37.757: mks| VMGL Panic: Fault occurred at 3001632165 (gsignal + 53, in /lib/libc.so.6)
Mar 05 15:38:37.757: mks| VMGL Panic: Call site at 78F5F6 ((null) + 7927286, in /usr/lib/vmware/bin/vmware-vmx)
Mar 05 15:38:37.757: mks| VMGL Panic: Backtrace from inside faulting function:
Mar 05 15:38:37.757: mks| Backtrace:
Mar 05 15:38:37.768: mks| Backtrace[0] 00007fff8dc03fb0 rip=00000000004324ac rbx=0000000000000000 rbp=00000000004322a0 r12=0000000000f40150 r13=000000000078f5f6 r14=00007fff8dc04140 r15=0000000000000007
Mar 05 15:38:37.771: mks| Backtrace[1] 00007fff8dc03fd0 rip=0000000000810878 rbx=00007fff8dc03fe0 rbp=0000000000000006 r12=0000000000f40150 r13=000000000078f5f6 r14=00007fff8dc04140 r15=0000000000000007
Mar 05 15:38:37.774: mks| Backtrace[2] 00007fff8dc03fe0 rip=0000000000720db0 rbx=0000000001558c10 rbp=0000000000000006 r12=0000000000f40150 r13=000000000078f5f6 r14=00007fff8dc04140 r15=0000000000000007
Mar 05 15:38:37.777: mks| Backtrace[3] 00007fff8dc04050 rip=00000000004a2af7 rbx=0000000000fdc430 rbp=0000000000000006 r12=00007fff8dc04270 r13=00007fff8dc04140 r14=0000000000000001 r15=0000000000000007
Mar 05 15:38:37.777: mks| Backtrace[4] 00007fff8dc04140 rip=000000300220ef60 rbx=0000000000000000 rbp=00007fff8dc04ff0 r12=0000000000000101 r13=00007fff8dc048d0 r14=000000000000006b r15=0000000000000007
Mar 05 15:38:37.777: mks| Backtrace[5] 00007fff8dc045a8 rip=0000003001632165 rbx=0000000000000000 rbp=00007fff8dc04ff0 r12=0000000000000101 r13=00007fff8dc048d0 r14=000000000000006b r15=0000000000000007
Mar 05 15:38:37.777: mks| Backtrace[6] 00007fff8dc045b0 rip=0000003001634f70 rbx=0000000000000000 rbp=00007fff8dc04ff0 r12=0000000000000101 r13=00007fff8dc048d0 r14=000000000000006b r15=0000000000000007
Mar 05 15:38:37.777: mks| Backtrace[7] 00007fff8dc046e0 rip=000000300166825b rbx=0000000000000000 rbp=00007fff8dc04ff0 r12=0000000000000101 r13=00007fff8dc048d0 r14=000000000000006b r15=0000000000000007
Mar 05 15:38:37.777: mks| Backtrace[8] 00007fff8dc05000 rip=0000003001671ab6 rbx=0000003001725f70 rbp=0000000000000003 r12=00007fff8dc05000 r13=00007fff80035fd0 r14=0000002300000022 r15=0000000000000000
Mar 05 15:38:37.777: mks| Backtrace[9] 00007fff8dc05040 rip=0000003001674b4d rbx=00007fff80000078 rbp=00007fff80000020 r12=0000002700000026 r13=00007fff80035fd0 r14=0000002300000022 r15=0000000000000000
Mar 05 15:38:37.777: mks| Backtrace[10] 00007fff8dc050e0 rip=0000003001676910 rbx=0000000001647700 rbp=00007fff80000020 r12=0000000000000020 r13=0000000000000000 r14=0000000001647774 r15=0000000000000000
Mar 05 15:38:37.777: mks| Backtrace[11] 00007fff8dc05110 rip=000000300360af19 rbx=0000000001647700 rbp=0000000000000001 r12=0000000000000001 r13=0000000000000000 r14=0000000001647774 r15=0000000000000000
Mar 05 15:38:37.777: mks| Backtrace[12] 00007fff8dc05180 rip=000000300360998d rbx=0000000001647700 rbp=0000000000000000 r12=0000000000000001 r13=0000000000000000 r14=0000000001647718 r15=0000000000000001
Mar 05 15:38:37.777: mks| Backtrace[13] 00007fff8dc051d0 rip=000000300360bb3c rbx=0000000000000bbf rbp=0000000001647700 r12=00007fff8dc05298 r13=00007fff8dc05210 r14=00000000016487b8 r15=00007fff8dc051e0
Mar 05 15:38:37.777: mks| Backtrace[14] 00007fff8dc05270 rip=0000003003a47acd rbx=00000000015928e0 rbp=00007fff8dc052f0 r12=00007fff800d8fc0 r13=00007fff800f0fe0 r14=0000000001e00022 r15=0000000001647700
Mar 05 15:38:37.777: mks| Backtrace[15] 00007fff8dc052e0 rip=000000300a478ba3 rbx=00000000015928e0 rbp=0000000000000000 r12=0000000000000087 r13=0000000000000001 r14=0000000001e00022 r15=0000000001e00022
Mar 05 15:38:37.777: mks| SymBacktrace[0] 00007fff8dc03fb0 rip=00000000004324ac in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Mar 05 15:38:37.778: mks| SymBacktrace[1] 00007fff8dc03fd0 rip=0000000000810878 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Mar 05 15:38:37.778: mks| SymBacktrace[2] 00007fff8dc03fe0 rip=0000000000720db0 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Mar 05 15:38:37.778: mks| SymBacktrace[3] 00007fff8dc04050 rip=00000000004a2af7 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Mar 05 15:38:37.778: mks| SymBacktrace[4] 00007fff8dc04140 rip=000000300220ef60 in function (null) in object /lib/libpthread.so.0 loaded at 0000003002200000
Mar 05 15:38:37.778: mks| SymBacktrace[5] 00007fff8dc045a8 rip=0000003001632165 in function gsignal in object /lib/libc.so.6 loaded at 0000003001600000
Mar 05 15:38:37.778: mks| SymBacktrace[6] 00007fff8dc045b0 rip=0000003001634f70 in function abort in object /lib/libc.so.6 loaded at 0000003001600000
Mar 05 15:38:37.778: mks| SymBacktrace[7] 00007fff8dc046e0 rip=000000300166825b in function (null) in object /lib/libc.so.6 loaded at 0000003001600000
Mar 05 15:38:37.778: mks| SymBacktrace[8] 00007fff8dc05000 rip=0000003001671ab6 in function (null) in object /lib/libc.so.6 loaded at 0000003001600000
Mar 05 15:38:37.778: mks| SymBacktrace[9] 00007fff8dc05040 rip=0000003001674b4d in function (null) in object /lib/libc.so.6 loaded at 0000003001600000
Mar 05 15:38:37.778: mks| SymBacktrace[10] 00007fff8dc050e0 rip=0000003001676910 in function __libc_malloc in object /lib/libc.so.6 loaded at 0000003001600000
Mar 05 15:38:37.778: mks| SymBacktrace[11] 00007fff8dc05110 rip=000000300360af19 in function (null) in object /usr/lib/libxcb.so.1 loaded at 0000003003600000
Mar 05 15:38:37.778: mks| SymBacktrace[12] 00007fff8dc05180 rip=000000300360998d in function (null) in object /usr/lib/libxcb.so.1 loaded at 0000003003600000
Mar 05 15:38:37.778: mks| SymBacktrace[13] 00007fff8dc051d0 rip=000000300360bb3c in function xcb_wait_for_reply in object /usr/lib/libxcb.so.1 loaded at 0000003003600000
Mar 05 15:38:37.778: mks| SymBacktrace[14] 00007fff8dc05270 rip=0000003003a47acd in function _XReply in object /usr/lib/libX11.so.6 loaded at 0000003003a00000
Mar 05 15:38:37.778: mks| SymBacktrace[15] 00007fff8dc052e0 rip=000000300a478ba3 in function (null) in object /usr/lib/libGL.so.1 loaded at 000000300a400000
Mar 05 15:38:37.778: mks| MKS: glXMakeContextCurrent() failed! (0:no error).
Mar 05 15:38:37.778: mks| MKS: glXMakeContextCurrent() failed! (0:no error).
Mar 05 15:38:37.784: mks| GLShaderCreateInternalProgram: Shader compile error
Mar 05 15:38:37.784: mks| GLShaderCreateInternalProgram: Shader compile error
Mar 05 15:38:37.784: mks| MKS: glXMakeContextCurrent() failed! (0:no error).
Mar 05 15:38:37.784: mks| MKS: glXMakeContextCurrent() failed! (0:no error).
Mar 05 15:38:37.784: mks| GLShader_InitContext: Can't bind FBO
Mar 05 15:38:37.784: mks| MKS: glXMakeContextCurrent() failed! (0:no error).
Mar 05 15:38:37.784: mks| MKS: glXMakeContextCurrent() failed! (0:no error).
Attached Files
File Type: gz nvidia-bug-report.log.gz (67.5 KB, 74 views)
etherfish is offline   Reply With Quote
Old 03-09-11, 01:22 AM   #6
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

NVIDIA internally filed a bug to track this issue Bug ID: 800961 . We will try to repro this issue in house and let you know the updates.
sandipt is offline   Reply With Quote
Old 03-26-11, 06:05 AM   #7
Txema
Registered User
 
Join Date: Aug 2008
Posts: 50
Default Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

Oh my god, i was going crazy, i've been a week looking for the reason of crashes and here it is, thanks to you i can use now vmware ^^

I'll be waiting for a fix

P.S: to reproduce it you only need to execute dxdiag.exe and run de direct3D test
Txema is offline   Reply With Quote
Old 03-31-11, 02:30 PM   #8
jjoel
Registered User
 
Join Date: Mar 2011
Posts: 1
Default Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

VMware Workstation version 7.1.4 was just released and includes a fix for this issue.
jjoel is offline   Reply With Quote

Old 03-31-11, 06:30 PM   #9
Txema
Registered User
 
Join Date: Aug 2008
Posts: 50
Default Re: 270.18 beta driver conflicts with VMware Workstation 3D acceleration

Confirmed, version 7.1.4 works

Thanks
Txema is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 05:26 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.