How-To's‎ > ‎IT‎ > ‎Linux‎ > ‎Fedora 20‎ > ‎


Correct problems arising from abruptly stopping Vmware

If by mistake you close vmware before shutting down the computer, starting again windows normally may result in a memory hog, that is, the guest windows will leak continually leak memory and take over the whole physical RAM. To prevent this, log in Windows safe mode, then restart.

Patching after Fedora 20 kernel update

Note: The instructions below (and file were also valid after I updated to kernel 3.17.4 and vmware version 6.0.4

VMware failed to compile after Fedora Kernel update 3.17.3-200.fc20.x86_64. It reported two errors:
/lib/modules/3.17.3-200.fc20.x86_64/build/include/linux/version.h not found
Failed to build vmnet.  Failed to execute the build command
The first error is corrected with a symbolic link
cd /lib/modules/3.17.3-200.fc20.x86_64/build/include/linux/
sudo ln -s /usr/include/linux/version.h
The second error requires application of a path file
sudo mkdir -p /tmp/vmware/source
cd /tmp/vmware/source
sudo cp -R /usr/lib/vmware/modules/source/* .
for i in ./*.tar; do sudo tar -xf $i; done
for i in ./*.tar;do sudo mv $i $i.orginal; done
# download the patch file to directory /tmp/vmware/source
sudo unzip ./
sudo patch -p1 < vmware-for-3.17.patch
sudo tar -cf vmnet.tar vmnet-only/
sudo mv -vfi ./vmnet.tar /usr/lib/vmware/modules/source/
After this, run vmware again and proceed to click in the "Install" button when prompted to recompile.

Installing for the first time in Fedora 20

Note: The following bullet points were my unsuccessful efforts to install and build vmware 5.0.3. It seems this version does not support kernel 3.14. However, some of the configuration hacks that I did may have been necessary for the following successful installation and configuration of vmware 6.0.2
  • We had version 5.0.3 installed in Ubuntu, thus we download version 5.0.3 from the vmware download page.
  • sudo mv VMware-Player-5.0.3-1410761.x86_64.bundle /opt/.
  • sudo chown root:root VMware-Player-5.0.3-1410761.x86_64.bundle.
  • sudo chown root:root VMware-Player-5.0.3-1410761.x86_64.bundle.
  • sudo chown root:root VMware-Player-5.0.3-1410761.x86_64.bundle. The installation GUI starts.
  • Select No in "Would you like to check for product updates on startup?"
  • After installation is complete, copy directory vmware/ from the external disk to the home directory. Do not start vmware yet.
  • Open vmware. It will complain that it cannot find the header files for the kernels. One possible reason is that the Fedora repository hosted at ORNL is out of sync with the parent repository, so that the kernel headers have not been installed. To install the kernels headers, follow the steps described in section "ORNL Fedora repository out of Sync with Fedora Parent" under page Linux. Then, issue sudo yum install kernel-headers and sudo yum install kernel-devel.
  • Open vmware again. If it continues complaining that it cannot find the header files, then take the following steps:
    • cd /lib/modules/$(uname -r)/build/include/linux                                                              
    • sudo ln -s ../generated/utsrelease.h                                                                         
    • sudo ln -s ../generated/autoconf.h                                                                           
    • sudo ln -s ../generated/uapi/linux/version.h
    • sudo cp /usr/include/linux/version.h /lib/modules/$(uname -r)/build/include/linux/
    • sudo ln -s  /usr/src/kernels/$(uname -r)/include/generated/uapi/linux/version.h  /usr/src/kernels/$(uname -r)/include/linux/version.h
    • After adding the symlink, the path to the kernel headers is /usr/src/linux-headers-$(uname -r)/include.
    • For good measure, uninstall vmware player, then reinstall:
      • cd /opt/
      • sudo ./VMware-Player-5.0.3-1410761.x86_64.bundle -u vmware-player
      • sudo ./VMware-Player-5.0.3-1410761.x86_64.bundle and follow the instructions
After these efforts I still could not get it to work. Thus, I uninstalled this 5.0.3 version and proceeded to install the latest version
  • cd /opt/
  • sudo ./VMware-Player-5.0.3-1410761.x86_64.bundle -u vmware-player
  • sudo ./VMware-Player-6.0.2-1744117.x86_64.bundle
  • After installation, I started vmware player. It complained GCC was not found and in fact, it wasn't installed. I used yumex to install packages for GCC as well as support for C++ and fortran.
  • After GCC installation, I reopened vmware and it successfully compiled!!!!

I opened vmware, then navigated to my virtual Windows 7 file (under directory /home/jbq/vmware/Windows7/) and loaded it. Then

  • A warning informing me that the virtual machine was in use and whether I wanted to take ownership. I did take ownership
  • Warnings that there was no graphics support. I ignored those
  • Offer to download and  install vmware tools, which I took. This should solve the problem of no graphics support.
  • Silly windows started but decided to scan the whole "hard drive". I waited paitiently

Update after Kernels of Ubuntu Host are Updated

Unfortunately, every time there is an update of the kernels in the Ubuntu host, vmware-player must be built and the tools reinstalled in my Windows 7 guest. If I fail to do this, the performance of both the guest and host systems will drop to an abysmal snail pace. There are the steps for a Ubuntu 12.04 host and a Windows 7 guest.

    The Easy Way

You start vmware-player and it will automatically build. Afterwards, start the virtual windows machine and update the vmware-tools. In the "Virtual Machine" tab of the Vmware window application:
Virtual Machine --> Reinstall Vmware-Tools...
The CD-ROM of the Window guest will contain now the neccessary files for installation of the Vmware Tools. Navigate to the folder and run setup64.exe.  You will be asked to enter administrator credentials. After this, choose Repair the installation.

    Error Message: "Cannot find component on update server..."

When running
Virtual Machine --> Reinstall Vmware-Tools..., this message may arise for a number of reasons, but the first one is that the vmware player did not build. Thus, we have to build from the command line:
0. If you did not restart you Linux host after updating the kernels, do so.
1. Shut down the virtual machine and vmware player, if open.
2. On a terminal in the Linux host, type sudo vmware-modconfig --console --install-all. This command will build vmware player.
3. Restart the Windows guest and try again to update vmware-tools with Virtual Machine --> Reinstall Vmware-Tools...
4. If the error message "Cannot find component on update server..." does not show up this time, then proceed to reinstall Vmware-Tools the easy way. See the previous section "The Easy Way" on how to reinstall Vmware-Tools.
5. If the error message "Cannot find component on update server..." persists, then we have to install Vmware Tools manually. See the next section for this.

Manually Installing Vmware Tools

1. Open Vmware and in the "Help" tab of the Vmware window application, look in "About Vmware Player" and write down the Vmware version that you have.
2. Uninstall the current Vmware Tools. In the Windows 7 guest, open the "Control Center", then "Programs", "Programs and Features", then "Uninstall a Program", then select "Vmware Tools". you will need administrator credentials for the uninstall.
3. Shut down the Windows guest and vmware.
4. Go to and download the package appropriate for your Vmware version that you have installed. In my particular case, it was
5. Untar the downloaded file. I typed in a terminal of the Linux host tar xf vmware-tools-linux-9.2.4-1410761.x86_64.component.tar
6. Install the component file. In my particular case, I used the following command in a terminal of the Linux host:
    sudo vmware-installer --console --install-component=vmware-tools-linux-9.2.4-1410761.x86_64.component
6. Restart vmware and the Windows guest. You should be all set.