Hi all -
For those who have been left wondering - here is instructions for installing VMWare Tools.
*Stolen From: VMWare Communities
4: Now, using the vSphere Client, do the "Guest -> Install Vmware tools" fun stuff...
5: Returning back to the SSH / vSphere console session:
There is a bug with VMXNET module under CentOS - patch is as follows:
Comment out the line as per: http://bugs.centos.org/view.php?id=3977
(add a /* before, and a */ after
Before:
So it will look like this:
Now, hit CTRL-O to save, and CTRL-X to exit nano
copy patched module back to sources dir
and complete the install of vmware tools
For those who have been left wondering - here is instructions for installing VMWare Tools.
*Stolen From: VMWare Communities
yum upgrade
yum install gcc kernel-devel
uname -r
rpm -q kernel-devel
(make sure the versions of the above two match exactly)
4: Now, using the vSphere Client, do the "Guest -> Install Vmware tools" fun stuff...
5: Returning back to the SSH / vSphere console session:
mkdir /mnt/cdrom
mount /dev/cdrom /mnt/cdrom/
cd /mnt/cdrom/
cp -rp VM*.tar.gz /tmp
cd /tmp
tar -zxvf VMwareTools-xxxxxxxx(your.ver).tar.gz,
There is a bug with VMXNET module under CentOS - patch is as follows:
cd /tmp/vmware-tools-distrib/lib/modules/source/
mkdir 1
cp vmxnet.tar 1
cd 1
tar -xvf vmxnet.tar
nano -w vmxnet-only/compat_netdevice.h
Comment out the line as per: http://bugs.centos.org/view.php?id=3977
(add a /* before, and a */ after
Before:
struct napi_struct {
int dummy;
};
So it will look like this:
/*
struct napi_struct {
int dummy;
};
*/
Now, hit CTRL-O to save, and CTRL-X to exit nano
copy patched module back to sources dir
rm vmxnet.tar
tar -cvf vmxnet.tar vmxnet-only/
mv vmxnet.tar
and complete the install of vmware tools
cd /tmp/vmware-tools-distrib/
./vmware-install.pl --default
And that will build the tools - with all the default choices...
Share this post:
Responses (11)
-
Accepted Answer
Looks like the relevant section of code is #ifdef'd out these days - any confirmation that the CentOS/vmw-tools bug is gone?
Also, in the original post exists a very slight typo, or perhaps a change since the original post was written. The line where you actually edit the file is missing the intermediate 'shared' directory. The below change to the line will fix the issue.
nano -w vmxnet-only/shared/compat_netdevice.h
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
I found that the bug is not present in the vSphere 5 tools. I downloaded the ISO file from VMWare, transferred it over to my ClearOS and installed it from there. The commands went something like:
yum update
mkdir /mnt/cdrom
yum install gcc kernel-devel
mount -o loop /root/VMware-tools-linux-your_version.iso /mnt/cdrom/
tar -xzvf /mnt/cdrom/VMwareTools-xxxxxxxx(your.ver).tar.gz -C /tmp
cd /tmp/vmware-tools-distrib/
./vmware-install.pl --default
FYI: The installer may look like it is waiting for a response, but don't press any keys. Doing so may cause the installer to endlessly echo out letters (if it does this, just CTRL+C out of the install, and restart it). -
Accepted Answer
I'm Installing ClearOS 5.2 SP1 on Vmware ESXi 5.0. I got the scrambled screen, so I'm installing the VMware tools. However the section that pertains to "There is a bug with VMXNET module under CentOS - patch is as follows:" didn't work. Either the new Vmware tools is slightly different, or I miss understood. I was unable to find the file "vmxnet-only/compat_netdevice.h" to edit. I just skipped this part of the install. After rebooting, the Screen scrambling was fixed. I could also see it loading the Vmware Tools Daemons during boot. I use all
Thank you for this walk-through. -
Accepted Answer
-
Accepted Answer
Luke,
Thanks so much for posting this info. I was stuck with the "can't find the gcc lib" message when I ran the vmware-install.pl on an ESXi 4.1 VM.
After running the following (as you suggested)
yum upgrade
yum install gcc kernel-devel
the install script found the gcc lib and proceeded to completion.
Re the garbled video (when Tools is not installed): I found that, in the virtual machine video card settings, specifying the "Auto-detect video settings" corrected the display problem.
I agree with you that a major advantage of installing Tools is the ability to restart or shutdown from the VMware menu (either Workstation or vSphere Client):
If the clearOS GUI gets frozen, having these VMware power settings available allows you to recover gracefully. -
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »