-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vmplayer 12 issues with latest vmware-bumblebee on Debian #12
Comments
Here's the output of bash -x ./vmplayer. I'm using VMWare Workstation 12 Player, standalone.
Without the vmware-bumbebee script, I get hardware acceleration w/ the integrated intel card, but with the script I get no hardware acceleration at all, and no processes show up in the output of |
That's not right. Did you run "sudo vmware -i" first ? |
I think I had run the installer a while ago, and I broke a couple of things (I think the installer didn't run correctly). I've completely reinstalled vmplayer to try to start on everything again. (Also I've gotten some of the library paths wrong, I'll submit a patch once this is figured out to fix this). This is the output I get when running the install script on a fresh install
Something seems to be wrong with the vmware-vmx binary (it shows up as red in my ls output?). This is what I get for the permissions of that folder (after running the script).
When I run the vmware-vmx file nothing seems to happen? I'm not sure what I'ts supposed to do. |
Ah I think I've gotten something better, give me a little bit to debug some more. I just needed to move the part where |
I think I've got vmplayer to start w/ primus. It seems to crash after a bit, but I'll submit what I have as a PR and keep you updated on my process of debugging that. |
Give me a second to fix up the install routine for the error you ran into. The flow of the script is as follows: the "vmware" that you call (that is this script) determines whether or not to launch everything under primusrun, which requires that it be run as root. That sets a bunch of variables, and calls the "gksu /usr/lib/vmware/bin/vmware-vmx". Vmware-vmx is another script that the installer installs, that then, running as root, launches each of the VMs under primusrun. Because the Window that VMWare runs in is a separate process from each VM, so each VM needs to be properly launched with primusrun as well, or you don't get 3d accelleration from NVidia. So let's first look at the installer of the 2nd script as the likely culprit. :) |
First, there's a bug in the installer getting even vmware to work. When I get home tonight I'll check in that fix. That will solve the $ULIB problems you're working around with hardcoded paths, as well as the installer not doing the "sed" on the /usr/bin/vmplayer script properly. I'm getting a segfault in Windows 8 when the GUI loads though, so this upcoming fix might NOT be the right thing. I might be able to get a case open though. |
I'm getting that same segfault (I think), although I'm not sure what is causing it. I could be doing something wrong when setting the paths I guess. Keep me updated on what you find out! |
I forked off vmware12 branch to try to solve this, and still haven't been able to get around that segfault myself. I might hit one of the Workstation Devs up on Twitter to see if there's something we've got fundamentally wrong, because I can't read the trace that results from that segfault. |
@jgkamat says: I still have issues running vmplayer though (it runs, but w/o the nvidia card). It may be because I'm using the latest version of vmplayer, but this patch at least makes it stop erroring out for me.
The text was updated successfully, but these errors were encountered: