Hi,
The thing from what you write down here that appears to be the initial cause of concern is:
libGL error: failed to load driver: nouveau
libGL error: unable to load driver: nouveau_dri.so
Player is trying to load a 3D driver for your nvidia card (nouveau) and if your windows VM has 3D enabled than that might be what you are bumping into.
Nouveau is the open source driver and frankly I doubt it is sufficient for full 3D support, so instead I suggest to download the drivers for your OS from the nvidia website and install them.
Then try again.
--
Wil
Hi,
You are still just getting the "please wait loading driver" screen and that's it?
I'm afraid your excerpts on the vmware.log file are not very helpful.
I need to see the whole log (attached as a file, not copy & paste content!) in order to at least get some idea.
Installing VMware Tools in the guest only works when the guest actually runs, you can't install it before the guest has booted.
What you have installed from the sounds of it is the VMware Tools .iso image into the VMware Workstation setup.
FWIW, VMware Tools installed or not would not normally stop you from booting a VM, it just makes things better (adds integrated clipboard management, shared folders, more performant drivers etc..)
One thing you could try is to login remotely via RDP.
In regards to the 3D / not 3D issue, I personally would try to boot the guest without 3D enabled, with the nouveau errors that part suggests it would not work anyways at this moment.
Of course the full disk encryption part using a driver is suspect as well, especially as that appears to be the last thing you see the VM do.
However if it works in Workstation 6 then I would expect it to work in Workstation 12.
If that part is causing you the trouble then you could try with a fresh copy of the VM, if available, and make sure that it hasn't upgraded its virtual hardware when you boot. Preferably even switch off the auto-upgrade of the virtual hardware.
--
Wil
Hi,
Seems you only waited 2 minutes on the player 12 one before a shut down.
2016-11-23T18:02:45.281Z| vcpu-0| I125: BIOS-UUID is 56 4d 6a 06 fd 3f 8c 2a-de ad 93 bd 6e 2e 99 db
2016-11-23T18:02:58.066Z| vcpu-0| I125: DDB: "longContentID" = "a94074c62f59fa37aa93b170835829d3" (was "4a6dbe2440b950c3c6bc562e4b3979e6")
2016-11-23T18:03:43.925Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
2016-11-23T18:05:39.046Z| vmx| I125: VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOff without reset, soft, softOptionTimeout: 20000000.
I guess you waited longer before, it is more of an observation as anything else. I would have waited longer to see what would be written in the logs.
However the most interesting (puzzling?) part I see in your logs is that it appears that you have BOTH vmware Player 6 as well as Player 12 installed at the same host at the same time?
At least the hostname is the same, the processor looks like it is the same and the logs are only 4 minutes apart from each other which seems a bit fast for a complete uninstall/reboot/install. Even location UUID of the VM matches which really makes me believe it is the same host.
If that's the case then I'm not surprised on one of them not working as you can't have both products installed at the same time.
The products depend on kernel modules and they both need a different set and those kernel modules need to be properly loaded/unloaded. You could do that manually, but I'm not 100% sure that the installer does, so my suggestion is to reboot between installs.
I'm a bit confused as your initial post is about uninstalling 6.0.6 and subsequently installing Player 12.x, but now it looks like Player 6 is installed next to Player 12.x
--
Wil