Fedora 17 is in Beta and Red Hat included the Open vSwitch in this distribution. So, I wanted to test it out.
The Fedora Beta installation process does not provide as many module installation options as a standard Red Hat Install does. So, the VMware Tools installation proved to be a little tricky…
The following packages will be required for you to complete the VMware Tools Installation:
I recommend using yum instead of rpm to install these packages. If your Linux Kung Fu is strong, by all means, use rpm -ivh <package name> and install all the dependencies manually.
If you would rather have an easier time, use the following workflow:
1. Run the VMware Tools installation. This will mount the ISO that contains the installation file (ex: VMwareTools-8.6.5-621624.tar.gz). Copy the file to a temporary location. Indicate to the vSphere client that the Tools installation is complete so that it will unmount the ISO.
2. Verify your yum configuration settings
There are three .repo files in /etc/yum.repos.d
yum would not execute properly until I made changes in all three.
In each file, the baseurl and mirror values may be incorrect, or your server may not be able to resolve the default YUM repository http://download.fedoraproject.org
I commented out the existing baseurl and mirror statements with a “#” and added a corrected baseurl line
There are 2 possible ways to resolve this:
a. In your host computer’s web browser, find out which mirror site that http://download.fedoraproject.org resolves to create the baseurl entry accordingly.
In my case, it was baseurl=http://mirrors.rit.edu/fedora/linux/releases/test/17-Beta/Fedora/x86_64/os/
b. Mount your Fedora 17 Beta ISO to a folder and use the mount path in your baseurl setting (ex: baseurl=file:///your-mount-path)
3. Install the packages listed above (ex: yum install tar)
4. Go to the temp location where you copied the VMware Tools gzip file and unzip it (ex: tar -xvzf VMwareTools-8.6.5-621624.tar.gz)
5. Run the installation perl script (ex: vmware-install.pl)
NOTE: You may get some errors related to the fast network device (vmxnet). However, as long as you can access the network properly, you can ignore it…at least I have not encountered any unfavorable behaviors, yet 🙂
Let me know what your experience is like in the comments section below.