VMware Tools
Purpose
This document describes the installation of the VMware Tools on a SME guest running on a VMware Server or an ESX Server.
Mount the installation CDROM image
This is not required on ESXi 4!
ESX 3.5
Start the Virtual Infrastructure Client. Make sure that you have added a virtual CDROM device to the SME VM. Power on the SME VM.
Right click in the SME VM and select 'Install/Upgrade VMware Tools'.
VMware Server
Start the VMware Server Console. Make sure that you have added a virtual CDROM device to the SME VM. Power on the SME VM.
Select the SME VM, then select menu 'VM'=>'Install VMware Tools...'.
Installation
SME Server 8 and 7.4 Guests on VMWare Server 2
Log into SME as user root on the local console.
mkdir -p /mnt/cdrom mount /dev/cdrom /mnt/cdrom rpm -ivh /mnt/cdrom/VMwareTools*i386.rpm vmware-config-tools.pl ln -fs /etc/rc.d/init.d/vmware-tools /etc/rc7.d/S90vmware-tools reboot
SME Server 7.3 and 7.4 Guests on ESXi 3.5
Log into SME as user root on the local console.
mkdir -p /mnt/cdrom mount /dev/cdrom /mnt/cdrom rpm -ivh /mnt/cdrom/VMwareTools*i386.rpm
Edit the file /etc/rc.d/init.d/vmware-tools and delete the following 2 lines:
939: vmware_exec 'Guest vmxnet fast network device:' vmware_stop_vmxnet 940: exitcode=$(($exitcode + $?))
Edit the file /usr/bin/vmware-config-tools.pl and search for the following line
$gSystem{'version_integer'} != kernel_version_integer(2, 4, 9)) {
and change it to
$gSystem{'version_integer'} != kernel_version_integer(2, 6, 9)) {
On ESXi 3.5.0 Build-123629 it is line #3565, on ESXi 3.5.0 Build-10271 it is line #3545.
Run the configuration script
vmware-config-tools.pl
and link the start script to run level 7
ln -fs /etc/rc.d/init.d/vmware-tools /etc/rc7.d/S90vmware-tools reboot
SME Server 7.4 Guest on ESXi 4.0
Download the required packages
wget http://packages.vmware.com/tools/esx/4.0/rhel4/i686/vmware-open-vm-tools-kmod-8.0.0-164009.165940.el4.i686.rpm wget http://packages.vmware.com/tools/esx/4.0/rhel4/i686/vmware-open-vm-tools-common-8.0.0-164009.165940.el4.i686.rpm wget http://packages.vmware.com/tools/esx/4.0/rhel4/i686/vmware-open-vm-tools-nox-8.0.0-164009.165940.el4.i686.rpm
Install the packages and dependencies
/usr/bin/yum localinstall \ vmware-open-vm-tools-kmod-8.0.0-164009.165940.el4.i686.rpm \ vmware-open-vm-tools-common-8.0.0-164009.165940.el4.i686.rpm \ vmware-open-vm-tools-nox-8.0.0-164009.165940.el4.i686.rpm
Link the start script to run level 7
ln -fs /etc/rc.d/init.d/vmware-tools /etc/rc7.d/S90vmware-tools
Start the service
service vmware-tools start
SME Server 7.4 Guest on ESXi 4.0 Update 1
Download the required packages
wget http://packages.vmware.com/tools/esx/4.0u1/rhel4/i686/vmware-open-vm-tools-kmod-8.0.2-208167.el4.i686.rpm wget http://packages.vmware.com/tools/esx/4.0u1/rhel4/i686/vmware-open-vm-tools-common-8.0.2-208167.el4.i686.rpm wget http://packages.vmware.com/tools/esx/4.0u1/rhel4/i686/vmware-open-vm-tools-nox-8.0.2-208167.el4.i686.rpm
Install the packages and dependencies
/usr/bin/yum localinstall \ vmware-open-vm-tools-kmod-8.0.2-208167.el4.i686.rpm \ vmware-open-vm-tools-common-8.0.2-208167.el4.i686.rpm \ vmware-open-vm-tools-nox-8.0.2-208167.el4.i686.rpm
Link the start script to run level 7
ln -fs /etc/rc.d/init.d/vmware-tools /etc/rc7.d/S90vmware-tools
Start the service
service vmware-tools start
SME Server 8.0 Guest on ESXi 4.0 Update 1
Download the required packages
wget http://packages.vmware.com/tools/esx/4.0u1/rhel5/i686/vmware-open-vm-tools-kmod-8.0.2-208167.el5.i686.rpm wget http://packages.vmware.com/tools/esx/4.0u1/rhel5/i686/vmware-open-vm-tools-common-8.0.2-208167.el5.i686.rpm wget http://packages.vmware.com/tools/esx/4.0u1/rhel5/i686/vmware-open-vm-tools-nox-8.0.2-208167.el5.i686.rpm
Install the packages and dependencies
/usr/bin/yum localinstall \ vmware-open-vm-tools-kmod-8.0.2-208167.el5.i686.rpm \ vmware-open-vm-tools-common-8.0.2-208167.el5.i686.rpm \ vmware-open-vm-tools-nox-8.0.2-208167.el5.i686.rpm
Link the start script to run level 7
ln -fs /etc/rc.d/init.d/vmware-tools /etc/rc7.d/S90vmware-tools
Start the service
service vmware-tools start
SME Server 8.0 Guest on ESXi 5.0
Install the relevant repository
db yum_repositories set vmware-tools repository \ Name 'VMWare Tools' \ BaseURL 'http://packages.vmware.com/tools/esx/5.0/rhel5/$basearch' \ EnableGroups no \ GPGCheck yes \ GPGKey http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-DSA-KEY.pub \ Visible no \ status disabled
Make the relevant changes stick
signal-event yum-modify
Import the VMWare RSA key (not sure if this could be done via the db mechanism)
rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub
Update server to latest packages
yum update
Now, installing VMWare tools involves knowing which type of kernel you have, PAE or non-PAE. To check, do a
uname -r
If the output of the command mentioned above contains PAE, then you have a PAE kernel and the following command should be used to install VMWare Tools
yum --enablerepo=vmware-tools install vmware-tools-esx-kmods-PAE vmware-tools-esx-nox
Otherwise, you don't have a PAE kernel and the relevant command to install VMWare Tools is
yum --enablerepo=vmware-tools install vmware-tools-esx-kmods vmware-tools-esx-nox
Link the start script to run level 7
ln -s /etc/init.d/vmware-tools-services /etc/rc7.d/S90vmware-tools-services
Start the service
/etc/init.d/vmware-tools-services start
Everything should be ok now, just restart the machine. If you by any chance wish to use the vmxnet2 adapter instead of the lance, then shutdown the VM, delete the "Flexible"/"Lance" network adapter and add "vmxnet2" in its place. Start the VM. If all goes ok, you'll now have the improved vmxnet NIC.
SME Server 8.0 Guest on ESXi 5.0 Update 1
Install the relevant repository
db yum_repositories set vmware-tools repository \ Name 'VMWare Tools' \ BaseURL 'http://packages.vmware.com/tools/esx/5.0u1/rhel5/$basearch' \ EnableGroups no \ GPGCheck yes \ GPGKey http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-DSA-KEY.pub \ Visible no \ status disabled
Make the relevant changes stick
signal-event yum-modify
Import the VMWare RSA key (not sure if this could be done via the db mechanism)
rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub
Update server to latest packages
yum update
Now, installing VMWare tools involves knowing which type of kernel you have, PAE or non-PAE. To check, do a
uname -r
If the output of the command mentioned above contains PAE, then you have a PAE kernel and the following command should be used to install VMWare Tools
yum --enablerepo=vmware-tools install vmware-tools-esx-kmods-PAE vmware-tools-esx-nox
Otherwise, you don't have a PAE kernel and the relevant command to install VMWare Tools is
yum --enablerepo=vmware-tools install vmware-tools-esx-kmods vmware-tools-esx-nox
Link the start script to run level 7
ln -s /etc/init.d/vmware-tools-services /etc/rc7.d/S90vmware-tools-services
Start the service
/etc/init.d/vmware-tools-services start
Everything should be ok now, just restart the machine. If you by any chance wish to use the vmxnet2 adapter instead of the lance, then shutdown the VM, delete the "Flexible"/"Lance" network adapter and add "vmxnet2" in its place. Start the VM. If all goes ok, you'll now have the improved vmxnet NIC.
SME Server 9 Alpha3 Guest on ESXi 5.1
Install repo key
rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub
create yum repo
db yum_repositories set vmware-tools repository \ Name 'VMWare Tools' \ BaseURL 'http://packages.vmware.com/tools/esx/5.1/rhel6/$basearch' \ EnableGroups no \ GPGCheck yes \ GPGKey http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-DSA-KEY.pub \ Visible no \ status disabled
Update yum.conf
expand-template /etc/yum.smerepos.d/sme-base.repo
check for PAE vs non-PAE kernel
uname -r
Install NON-PAE tools if "PAE" is not contained in the output from "uname -a"
uname -a |grep PAE || yum --enablerepo=vmware-tools install vmware-tools-esx-kmods vmware-tools-esx-nox
Install PAE tools if "PAE" is contained in the output from "uname -a"
uname -a |grep PAE && yum --enablerepo=vmware-tools install vmware-tools-esx-kmods-PAE vmware-tools-esx-nox
There was no action required to cause the vmware tools to start at boot. Verify tools are running with
/etc/vmware-tools/init/vmware-tools-services status
SME Server 9 Guest on ESXi 5.5
Install repo key
rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub
create yum repo
db yum_repositories set vmware-tools repository \ Name 'VMWare Tools' \ BaseURL 'http://packages.vmware.com/tools/esx/5.5latest/rhel6/$basearch' \ EnableGroups no \ GPGCheck yes \ GPGKey http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-DSA-KEY.pub \ Visible no \ status disabled
Update yum.conf
expand-template /etc/yum.smerepos.d/sme-base.repo
check for PAE vs non-PAE kernel
uname -r
Install NON-PAE tools if "PAE" is not contained in the output from "uname -a"
uname -a |grep PAE || yum --enablerepo=vmware-tools install vmware-tools-esx-kmods vmware-tools-esx-nox
Install PAE tools if "PAE" is contained in the output from "uname -a"
uname -a |grep PAE && yum --enablerepo=vmware-tools install vmware-tools-esx-kmods-PAE vmware-tools-esx-nox
There was no action required to cause the vmware tools to start at boot. Verify tools are running with
/etc/vmware-tools/init/vmware-tools-services status
SME Server 10 as Guest
Installation of vmware tools on SME 10 is a bit different. For example, no special repository is now needed. But we do have configure some files. Start by downloading the open-vm-tools package:
yum install open-vm-tools
Set a config key for SME to recognise the service:
config set vmtoolsd service status enabled access private
We will need to create a directory and then a file in it:
mkdir -p /usr/lib/systemd/system/vmtoolsd.service.d nano /usr/lib/systemd/system/vmtoolsd.service.d/50koozali.conf
Contents of 50koozali.conf should be:
[Install] WantedBy=sme-server.target
Reconfigure and reboot:
signal-event post-upgrade; signal-event reboot
That should do it! Check that the service is running alright:
systemctl status vmtoolsd
Also check that the hypervisor (ESXi/VMWare workstation or other) detects the vmware tools as running.
