As I expected a new system means a new set of problems. The first application that encounter problem with Pangolin is VMWare Player 4.0.3. The installation of VMWare Player was smooth though, there was no problem occurred. For a while I felt relief, “yes, I can use VMWare Player tomorrow”. The problem showed when I tested to open one of the VMWare image. The VMWare was trying to install additional functions, and it failed.
- Un-tar /usr/lib/vmware/modules/source/vmnet.tar to a directory you can write to (eg /tmp, /var/tmp or your desktop or home directory) – this creates a directory vmnet-only
- Apply the attached patch to the un-tarred source (run patch in the directory from step 1 – the patch file was created from the parent directory of vmnet-only)
- Save the original source tar file as /usr/lib/vmware/modules/source/vmnet.tar.orig
- create a new /usr/lib/vmware/modules/source/vmnet.tar from the patched source (with ‘sudo tar cf /usr/lib/vmware/modules/source/vmnet.tar vmnet-only’ in the directory from step 1)
- Start the vmware player/workstation/….
So, these were what I did.
I extracted the “/usr/lib/vmware/modules/source/vmnet.tar” to “/tmp” folder.
tar xvf /usr/lib/vmware/modules/source/vmnet.tar -C /tmp
Copy the patch file (vmnet.diffs) to “/tmp” folder and then apply the patch.
patch -p0 < vmnet.diffs
Back up the original “vmnet.tar” as “vmnet.tar.orig”.
sudo cp vmnet.tar vmnet.tar.orig
Create a new “vmnet.tar” from “/tmp” folder.
sudo tar cvf /usr/lib/vmware/modules/source/vmnet.tar vmnet-only
Trigger the kernel update by trying to open a VMWare image again. At this time the update went smoothly, and the image was opened.