Topic: ESXi 5 / SME Server 8 howto: VMWare Tools Installation

[Michail Pappas]

One should definitely share info, instead of only asking for it
 
The following are some steps taken to install vmware tools corresponding to ESXi 5, on SME 8. The steps are similar to the  FAQ at http://wiki.contribs.org/VMware_Tools and can be found  here and here for manual selection of the proper vmware installation commands.

My approach is a mix of http://packages.vmware.com/tools/docs/manuals/osp-esxi-50-install-guide.pdf and http://wiki.contribs.org/VMware_Tools . That is, the reasoning is to cater for vmware tools updates, via "yum update" commands.

Install the relevant repository:

Code: [Select]

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 enabled

Make the relevant changes:

Code: [Select]

signal-event yum-modify

(At this point I could not immediately call "yum install ..." for some reason. Just wait a bit if this happens.

Import the VMWare RSA key (not sure if this could be done via the db mechanism):

Code: [Select]

rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub

Install VMWare tools on ESXi 5:

Code: [Select]

yum update
yum install vmware-tools-esx-kmods vmware-tools-esx-nox

Link the start script to run level 7:

Code: [Select]

ln -s /etc/init.d/vmware-tools-services /etc/rc7.d/S90vmware-tools-services

Start the service:

Code: [Select]

/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.

If useful, perhaps someone could add it to the FAQ at http://wiki.contribs.org/VMware_Tools

[ourmojo]

One should definitely share info, instead of only asking for it

One should also say Thank You when they have been helped.

Thank You! Worked perfectly.

[CharlieBrady]

One should definitely share info, instead of only asking for it

Yes, but please do so in the correct place. This forum's purpose is:

  Discussion of the use of *ONLY* the components and features included on the SME Server 8.x CD. Please help the developers by
  reporting any problems to the Bug Tracker first, not here.

The wiki is the correct place for you to post your information.

If useful, perhaps someone could add it to the FAQ at http://wiki.contribs.org/VMware_Tools

You can get access to do that.

http://wiki.contribs.org/SME_Server:Volunteering#Wiki_Team

[Stefano]

Install the relevant repository:

Code: [Select]

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 enabled


I would add to Charlie's post that (IMVHO) an external repository should not be enabled by default

[Michail Pappas]

Yes, but please do so in the correct place.

[...]

The wiki is the correct place for you to post your information.

You can get access to do that.

http://wiki.contribs.org/SME_Server:Volunteering#Wiki_Team

I understand that, but must respectfully add that my time is limited. Creating (yet another) account drains my limited time resource. So my reasoning is that I either (a) would post this in the forum, in the hope that google'ing for something like that would help someone or (b) not post it at all.

I understand this is a volunteer project, and I'm helping to the extent I can. And with that said, please do not take my explanation above as a sign of an apology on my part; rather an explanation.

@Stefano: thanks, did not know that, will fix it.

EDIT: Can't fix it Stefano, can't edit the initial post, perhaps a moderator?

[CharlieBrady]

I understand that, but must respectfully add that my time is limited.

Can you name one person's whose time is not limited?

[chris burnat]

I understand that, but must respectfully add that my time is limited. Creating (yet another) account drains my limited time resource. So my reasoning is that I either (a) would post this in the forum, in the hope that google'ing for something like that would help someone or (b) not post it at all.

I understand this is a volunteer project, and I'm helping to the extent I can. And with that said, please do not take my explanation above as a sign of an apology on my part; rather an explanation.

@Stefano: thanks, did not know that, will fix it.

EDIT: Can't fix it Stefano, can't edit the initial post, perhaps a moderator?

Hello Michael,
Fair enough.  I will go and fix, i.e. edit your original post and later on put your Howto in the Wikis and fix repos - need to check the lot to ensure that correct commands is given once we set the repo to "disabled".  This being said, you do not have to create another account for access to the Wikis, just open a bug in Bugzilla here:

Code: [Select]

http://bugs.contribs.org/enter_bug.cgi?product=SME%20Web%20site-select mediawikis for component
-provide your username for the Forums
Takes around 1 minute, someone will approve, you done, and can use Wikis next time.  I think you will find this a more efficient way of passing info than all of this coming and going in this thread.... (LOL)
Cheers.

Note: Moving to General Discussions.

[chris burnat]

Here is the edited version of the howto taking into accounts Stefano comments about external repos not being enabled.  I checked and it installs alright. However, vmtoolsd will not start....  Any clues?

Install the relevant repository:

Code: [Select]

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:

Code: [Select]

signal-event yum-modify

[Note: At this point I could not immediately call "yum install ..." for some reason. Just wait a bit if this happens.]

Import the VMWare RSA key (not sure if this could be done via the db mechanism):

Code: [Select]

rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub

Update server to latest packages:

Code: [Select]

yum update

Install VMWare tools on ESXi 5:

Code: [Select]

yum --enablerepo=vmware-tools install vmware-tools-esx-kmods vmware-tools-esx-nox

Link the start script to run level 7:

Code: [Select]

ln -s /etc/init.d/vmware-tools-services /etc/rc7.d/S90vmware-tools-services

Start the service:

Code: [Select]

/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.

###Note1 : not starting for me:

Code: [Select]

[root@sme80 /]# service vmware-tools-services start
[root@sme80 /]#
[root@sme80 ~]# pgrep -fl vmtoolsd
[root@sme80 ~]#
[root@sme80 ~]# service vmware-tools-services status
vmtoolsd is not runningvmmemctl kernel module not loaded.

###Note 2:

Code: [Select]

yum --enablerepo=vmware-tools install vmware-tools-esx-kmods vmware-tools-esx-nox
My understanding is that  this command assumes that we are dealing with a standard kernel, what about if kernel is PAE?

[Michail Pappas]

Hello Michael,
Fair enough.  I will go and fix, i.e. edit your original post and later on put your Howto in the Wikis and fix repos - need to check the lot to ensure that correct commands is given once we set the repo to "disabled".  This being said, you do not have to create another account for access to the Wikis, just open a bug in Bugzilla here:

Code: [Select]

http://bugs.contribs.org/enter_bug.cgi?product=SME%20Web%20site-select mediawikis for component
-provide your username for the Forums
Takes around 1 minute, someone will approve, you done, and can use Wikis next time.

Hahaha, ok I'll do that

I think you will find this a more efficient way of passing info than all of this coming and going in this thread.... (LOL)

Well, I must agree.

###Note 2:

Code: [Select]

yum --enablerepo=vmware-tools install vmware-tools-esx-kmods vmware-tools-esx-nox
My understanding is that  this command assumes that we are dealing with a standard kernel, what about if kernel is PAE?

... and there goes my first bug

In this case the line above should be (prolly) modified to:

Code: [Select]

yum --enablerepo=vmware-tools install vmware-tools-esx-kmods-PAE vmware-tools-esx-nox
Can you please provide me with the output of "uname -r" ? Perhaps I can do this with some scripting, in order to have a single yum install command for both PAE/non-PAE.

[chris burnat]

........[snip]
In this case the line above should be (prolly) modified to:

Code: [Select]

yum --enablerepo=vmware-tools install vmware-tools-esx-kmods-PAE vmware-tools-esx-nox
Can you please provide me with the output of "uname -r" ? Perhaps I can do this with some scripting, in order to have a single yum install command for both PAE/non-PAE.

1) On the server I tested your howto, it turns out it is a standard kernel, so command you had should work fine one would think, but it does not, or at least I cannot start  vmware-tools-services as shown in previous post:

Code: [Select]

[root@sme80 ~]# uname -r
2.6.18-308.8.2.el5
Life is full of mysteries...  I can test some more for you, server is still loaded.

2) My production server returns:

Code: [Select]

[root@gateway0 ~]# uname -r
2.6.18-308.11.1.el5PAEAnd whilst I did not tested your howto on this box, you may need to cater for this eventuality...

Cheers.

[chris burnat]

Oooops. I made an error, you need to follow the link given by Charlie to get access to the Wikis, or just paste this one:

http://forums.contribs.org/index.php?action=admin;area=regcenter;sa=register

and enter your  password.

[Michail Pappas]

1) On the server I tested your howto, it turns out it is a standard kernel, so command you had should work fine one would think, but it does not, or at least I cannot start  vmware-tools-services as shown in previous post:

Code: [Select]

[root@sme80 ~]# uname -r
2.6.18-308.8.2.el5
Life is full of mysteries...  I can test some more for you, server is still loaded.

Just to be on the safe side, you are running ESXi 5, correct? The guest is a 32-bit SME obviously? How did you configure your VM on ESXi, as Red Hat 5 32-bit, CentOS 4/5/6 32-bit, other?

I have tested this on the following systems:
* my production server (SME 8, under ESXi 5), server-only setup, with a 2.6.18-308.11.1.el5 kernel and
* a test server specifically made to test this issue (also SME 8, under ESXi 5), specs same as above

In the latter case I followed the instructions as edited by you and everything worked fine here.

EDIT: I'd try to run the contents of /etc/init.d/vmware-tools-services one line at a time and check what breaks where...

2) My production server returns:

Code: [Select]

[root@gateway0 ~]# uname -r
2.6.18-308.11.1.el5PAEAnd whilst I did not tested your howto on this box, you may need to cater for this eventuality...

This is a bit of a quick and dirty hax, but I've changed the install command to the following, which should work for both PAE/non-PAE kernels as well as the 64-bit ones (will need some feedback).

Code: [Select]

yum --enablerepo=vmware-tools install \
    vmware-tools-esx-kmods`uname -r | sed 's/2.*el5//g' | sed 's/PAE/-PAE/'` \
    vmware-tools-esx-nox


[Michail Pappas]

Being nub enough, please don't laugh with my suggestion. On the problematic machine:

Code: [Select]

cp /etc/init.d/vmware-tools-services ~
vi ~/vmware-tools-services
At line 11 which is initially empty, insert the following command:

Code: [Select]

set -x

Save the file and then from the shell, run the following (note the ambersand):

Code: [Select]

~/vmware-tools-services start

Paste the command output here.

[chris burnat]

OK, all is fine now.  I am a bit new to virtual environment (an understatement...) and I stuffed up.  Hope I did not waste too much of your time.  Where now? Are you happy with the hack you done for kernel (PAE)?  Problem is, there may be other kernels around, not sure...  It may perhaps be safer to have the user doing uname -r and then adding correct kernel type to the installation command, this way no possibility of mistakes..

[Michail Pappas]

OK, all is fine now.  I am a bit new to virtual environment (an understatement...) and I stuffed up.  Hope I did not waste too much of your time.

No worries there.

Where now? Are you happy with the hack you done for kernel (PAE)?  Problem is, there may be other kernels around, not sure...  It may perhaps be safer to have the user doing uname -r and then adding correct kernel type to the installation command, this way no possibility of mistakes..

I've already added a wiki for having 8.0 guests under either Esxi 5.0 or 5.0u1. If there are lots of kernels then I guess the proper thing to do is provide extra instructions for them. I have tested in a non-PAE kernel; it works fine. I've also made some tests so that the installation will go alright in a PAE-enabled kernel case. OTOH, perhaps play it safe and make the selection manually.

What do the other readers here think?