It turns out that there is a single line that has to be changed in the vmnet module in order for VMWare to be runnable again. So, here are the steps you have to do in order to patch the file:
- Create temporary directory, e.g. /tmp/vmware and position yourself in that directory.
- Create a file named vmnet.patch and put into it the following content:
diff -ur vmnet-only.a/netif.c vmnet-only/netif.c --- vmnet-only.a/netif.c 2014-10-10 03:23:08.585920012 +0300 +++ vmnet-only/netif.c 2014-10-10 03:23:09.245920008 +0300 @@ -149,7 +149,7 @@ memcpy(deviceName, devName, sizeof deviceName); NULL_TERMINATE_STRING(deviceName); - dev = alloc_netdev(sizeof *netIf, deviceName, VNetNetIfSetup); + dev = alloc_netdev(sizeof *netIf, deviceName, NET_NAME_UNKNOWN, VNetNetIfSetup); if (!dev) { retval = -ENOMEM; goto out;
- Unpack /usr/lib/vmware/modules/source/vmnet.tar in the current directory (/tmp/vmware):
tar xf /usr/lib/vmware/modules/source/vmnet.tar
- Patch the module:
cd vmnet-only; patch -p1 < ../vmnet.patch; cd ..
- Make a copy of old, unpatched, archive:
mv /usr/lib/vmware/modules/source/vmnet.tar /usr/lib/vmware/modules/source/vmnet.tar.SAVED
- Create a new archive:
tar cf /usr/lib/vmware/modules/source/vmnet.tar vmnet-only
- Start vmware configuration process:
vmware-modconfig --console --install-all
Old instructions (not valid any more!)
Well, here we go again. After recent update which brought kernel 3.17 to Fedora 20, VMWare Workstation 10.0.4 had problems with kernel modules. Luckily, after some short googling I found a solution. That solution works. There are two things that might confuse you though:- After cd command and before for loop you have to switch to root account (that is indicated by prompt sign change from $ to #).
- The substring kernel-version in patch command should be replaced with a string "3.17". That is actually the name you gave to a file while executing curl command at the beginning of the process.
Anyway, that's it.
No comments:
Post a Comment