In the above example, the VM log file is at C:\Users\...\Ubuntu\vmware.log. When the Ubuntu is hangs, at the end of the VM log file, I saw some log messages similar to the below,
2014-07-22T19:21:19.299-04:00| vmx| I120: GuestRpcSendTimedOut:
message to toolbox timed out. 2014-07-22T19:21:19.299-04:00| vmx| I120: Vix: [5648 guestCommands.c:1924]:
Error VIX_E_TOOLS_NOT_RUNNING in VMAutomationTranslateGuestRpcError(): VMware Tools are not running in the guest 2014-07-22T19:21:25.635-04:00| vmx| I120: USBGW: Write arbitrator op:13 len:11
My guess is that the VMware Tools is not installed and configured properly for the new Linux kernel. The solution would to reinstall the VMware Tools. Since the Ubuntu guest hangs during boot, I have to find an alternate to do it. Luckily, I can boot the Ubuntu guest into the "Recovery Mode" with the problematic Linux kernel via the "Advanced Option" during boot.
I observed two difficulties when I tried to reinstall the VMware Tools in the "Recovery Mode".
- When I tried to install the VMware Tools when I switched to shell in the "Recovery Mode" by running <code>sudo ./vmware-install.pl</code>, I observed many warning messages similar to below,
The /tmp directory may be under attack
- You may have to download the VMware Tools, for which, we need to enable network in the "Recovery Mode".
To address the above difficulties, my solutions is,
- In the "Recovery Mode", first enable "network" from the list of options.
- Then go to shell (by choosing "Drop to root shell prompt").
- Start the
sshd. This is a two-step procedure.
mkdir /var/run/sshd /usr/sbin/sshd
- Now, figure out the IP address of the guest (e.g., using ifconfig)
- Log onto the virtual machine using a Secure Shell client as a regular user with
- Install the VMware player as the regular user using
- Reboot. The the problem went away.