Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a deployment with what I would call an Enterprise Cloud Provider. It's VMWare Infrastructure 3.5.x and includes VMotion / VMWare HA instances, etc.

At Provider 1 VMWare Tools was installed:

  • vmware-guestd is running and;
  • at least two kernel modules are loaded, vmmemctl & vmhgfs

Provider 1 does nightly VM Snapshots.

We are beginning a new deployment at Provider 2 (also an Enterprise Cloud Provider). They did not install VMWare Tools. Provider 2 does not do nightly VM Snapshots but rather file-system backups (using an agent).

From my reading it seems like at the very least VMWare Tools should be installed for the Memory Balloon Driver (vmmemctl) and from reading sources like this one it suggests that certain VirtualCenter management operations also depend upon VMWare Tools being installed in the Linux guest.

Note that all of our instances are headless (default runlevel is 3) and RHEL.

It is hard to find authoritative information on this question and the aforementioned source is somewhat dated.

Can someone shed some light on this? What are the factors/criteria that would lead to an answer in the affirmative or negative?

TIA

Cheers

share|improve this question

4 Answers 4

up vote 7 down vote accepted

You should also have the tools loaded for ease of guest shutdown and power management. Being able to shut the guest operating system down from the Vcenter server or infrastructure client is handy.

share|improve this answer
    
Heard back from Provider 2. They have essentially admitted an oversight (FML). In a VirtualCenter deploy VMWare Tools should definitely be installed, even in headless Linux guests. (Selecting as best answer since it was the closest.) –  HTTP500 Jan 21 '11 at 17:27

I'd be tempted to load all of the vmtools, not only will the guest be less of a load on the host but it's a great way of getting your time right.

share|improve this answer
2  
Thanks for your reply. With regard to timekeeping though VMWare best practices are to use NTP not VMWare Tools. kb.vmware.com/selfservice/microsites/… "In all cases use NTP instead of VMware Tools periodic time synchronization." –  HTTP500 Jan 18 '11 at 21:11
    
@Jason -- Do you know if that's a recent new recommendation? I could swear that an earlier version of that document said the opposite, but it's possible I'm mis-remembering. –  larsks Jan 18 '11 at 21:41
3  
@larsks, using NTP it is a somewhat new recontamination. I noticed the change a few months ago. –  Zoredache Jan 18 '11 at 21:47
    
Hadn't seen that document. –  Chopper3 Jan 18 '11 at 22:23
    
@Zoredache -- interesting. Thanks! –  larsks Jan 19 '11 at 1:24

In addition to the better power/cpu/memory management that other answers have mentioned, the tools also give you the vmxnet* and pvscsi/something else/ device drivers that, ostensibly, provide better performance for networking and IO compared to emulating a "real" device.

share|improve this answer

Installing the tools will allow for better cpu and memory management. For example, Transparent Page Sharing & Memory Ballooning.

Understanding Memory Resource Management in VMware (pdf)

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.