I have been
using VMware for a few weeks now. While it ran without glitches in
Windows 7 and previous versions of Ubuntu, after upgrading, I ran into
trouble when I tried to start VMware workstation 7. It kept giving me
the error
using VMware for a few weeks now. While it ran without glitches in
Windows 7 and previous versions of Ubuntu, after upgrading, I ran into
trouble when I tried to start VMware workstation 7. It kept giving me
the error
Failed to compile module vmmon!
After
much googling I was able to find a blog by Ved Antani which had the
detailed steps how to get past the annoying error. I am summarising the
steps below
You will have to drop to root to carry out the following steps
mkdir /tmp/vmware && cd /tmp/vmware
cp -R /usr/lib/vmware/modules/source/ .
cd /tmp/vmware/source
wget http://linux-knowledgebase.com/userFiles/files/vmware2_6_39patchv3.tar.bz2
mv vmware2_6_39patchv3.tar.bz2 vmware2.6.39patchv3.tar.bz2
tar -jxvf vmware2.6.39patchv3.tar.bz2
for i in ./*.tar; do tar -xf $i; done
for i in ./*.tar; do mv $i $i.orginal; done
patch -t -f -p1 < vmware2.6.39fixedv3.patch
tar cf vmblock.tar vmblock-only
tar cf vmci.tar vmci-only
tar cf vmmon.tar vmmon-only
tar cf vmnet.tar vmnet-only
tar cf vsock.tar vsock-only
cp -vf *.tar /usr/lib/vmware/modules/source/
tar -jxvf vmware2.6.39patchv3.tar.bz2
for i in ./*.tar; do tar -xf $i; done
for i in ./*.tar; do mv $i $i.orginal; done
patch -t -f -p1 < vmware2.6.39fixedv3.patch
tar cf vmblock.tar vmblock-only
tar cf vmci.tar vmci-only
tar cf vmmon.tar vmmon-only
tar cf vmnet.tar vmnet-only
tar cf vsock.tar vsock-only
cp -vf *.tar /usr/lib/vmware/modules/source/
Once done, Run VMware workstation.
Thanks to Ved Antani
After much googling I came across this solution to the increasingly famous problem about VMware compiling the kernel in ubuntu 11.10.
I tried to follow the steps but at one point I have the following output :
root@liviux-laptop:/tmp/vmware/source# patch -t -f -p1 < vmware2.6.39fixedv3.patch
patching file vmblock-only/linux/dentry.c
Hunk #1 FAILED at 104.
1 out of 1 hunk FAILED — saving rejects to file vmblock-only/linux/dentry.c.rej
patching file vmblock-only/linux/filesystem.c
Hunk #1 FAILED at 44.
Hunk #2 FAILED at 66.
Hunk #3 FAILED at 336.
Hunk #4 FAILED at 533.
Hunk #5 FAILED at 552.
Hunk #6 succeeded at 595 with fuzz 2 (offset 32 lines).
5 out of 6 hunks FAILED — saving rejects to file vmblock-only/linux/filesystem.c.rej
can't find file to patch at input line 109
Perhaps you used the wrong -p or –strip option?
The text leading up to this was:
————————–
|diff -u -r source-orig/vmci-only/linux/driver.c source/vmci-only/linux/driver.c
|— source-orig/vmci-only/linux/driver.c 2011-03-26 06:37:32.000000000 +0100
|+++ source/vmci-only/linux/driver.c 2011-04-02 13:32:12.000000000 +0200
————————–
No file to patch. Skipping patch.
1 out of 1 hunk ignored
patching file vmmon-only/linux/driver.c
Hunk #1 FAILED at 780.
Hunk #2 FAILED at 1041.
2 out of 2 hunks FAILED — saving rejects to file vmmon-only/linux/driver.c.rej
patching file vmmon-only/linux/hostif.c
Hunk #1 FAILED at 46.
1 out of 1 hunk FAILED — saving rejects to file vmmon-only/linux/hostif.c.rej
patching file vmmon-only/linux/iommu.c
Hunk #1 FAILED at 44.
1 out of 1 hunk FAILED — saving rejects to file vmmon-only/linux/iommu.c.rej
can't find file to patch at input line 165
Perhaps you used the wrong -p or –strip option?
The text leading up to this was:
————————–
|diff -u -r source-orig/vmnet-only/driver.c source/vmnet-only/driver.c
|— source-orig/vmnet-only/driver.c 2011-03-26 06:37:29.000000000 +0100
|+++ source/vmnet-only/driver.c 2011-04-02 14:14:57.000000000 +0200
————————–
No file to patch. Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 219
Perhaps you used the wrong -p or –strip option?
The text leading up to this was:
————————–
|diff -u -r source-orig/vmnet-only/filter.c source/vmnet-only/filter.c
|— source-orig/vmnet-only/filter.c 2011-03-26 06:37:29.000000000 +0100
|+++ source/vmnet-only/filter.c 2011-04-02 14:16:50.000000000 +0200
————————–
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 231
Perhaps you used the wrong -p or –strip option?
The text leading up to this was:
————————–
|diff -u -r source-orig/vmnet-only/hub.c source/vmnet-only/hub.c
|— source-orig/vmnet-only/hub.c 2011-03-26 06:37:29.000000000 +0100
|+++ source/vmnet-only/hub.c 2011-04-02 14:15:56.000000000 +0200
————————–
No file to patch. Skipping patch.
1 out of 1 hunk ignored
patching file vsock-only/linux/af_vsock.c
Hunk #1 FAILED at 102.
1 out of 1 hunk FAILED — saving rejects to file vsock-only/linux/af_vsock.c.rej
patching file vsock-only/linux/util.c
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED — saving rejects to file vsock-only/linux/util.c.rej
root@liviux-laptop:/tmp/vmware/source# tar cf vmblock.tar vmblock-only
root@liviux-laptop:/tmp/vmware/source# tar cf vmci.tar vmci-only
tar: vmci-only: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
Does anybody know why?
Thank you
Livio
Hi Livio,
This may sound stupid, but did you check if you are in the right folder? or are you giving the right path? i have encountered something like this if i end up with wrong files to patch. Also, just to be on the safe side make sure you have all the development packages are up-to-date.
Hi and thanks for your reply.
I did check the path. When I launch the "patch" command that give me the error on the previous post, I'm in /tmp/vmware/source.
The content of the folder is the following:
root@liviux-laptop:/tmp/vmware/source# lspatch-modules_2.6.39.sh vmmon-only vmware2.6.39patchv3.tar.bz2vmblock-only vmmon.tar vsock-onlyvmblock.tar vmmon.tar.orginal vsock.tarvmblock.tar.orginal vmnet.tar vsock.tar.orginalvmci.tar vmnet.tar.orginalvmci.tar.orginal vmware2.6.39fixedv3.patch
So I guess it's supposed to be the right folder.
Thanks!!
Awesome Thanks!
my hero!! this worked perfectly, thanks!!!!!
welcome! 🙂
Exactly what i was looking for… thanks for posting!!