WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / ESXi / w00t! VMware Tools for Nested ESXi!

w00t! VMware Tools for Nested ESXi!

11.11.2013 by William Lam // 42 Comments

I have been working with Nested ESXi since it original inception and this technology has greatly benefited me and the entire VMware community, especially when it comes to learning about VMware software and being able to easily prototype something before installing it on actual hardware. However, one thing that I felt that has been missing for awhile now is the ability to run an instance of VMware Tools within a Nested ESXi VM. I have personally been asking for this feature for a couple of years and I know many in the VMware community have expressed interests as well.

I am super excited to announce that VMware has just released a new Fling that provides you with a VIB that you can install VMware Tools inside a Nested ESXi host. I originally showed a demo of this at VMworld Barcelona in my vBrownBag Tech Talk and as I mentioned we would be releasing this as a VMware Fling very soon. So here it is!

UPDATE (08/20/15) - An updated version of VMware Tools for Nested ESXi was just published, make sure to download latest version and you can find more details here.

Requirements:

  • Nested ESXi running 5.0, 5.1 or 5.5 

Installation:

To install the VIB, you simply just need to download it and upload the VIB it to your Nested ESXi datastore and then run the following commands:

esxcli system maintenanceMode set -e true
esxcli software vib install -v /vmfs/volumes/[VMFS-VOLUME-NAME]/esx-tools-for-esxi-9.7.0-0.0.00000.i386.vib -f
esxcli system shutdown reboot -r "Installed VMware Tools"

You can also install the VIB directly from VMware.com if you have direct or proxy internet connectivity from your ESXi host by running the following commands:

esxcli network firewall ruleset set -e true -r httpClient
esxcli software vib install -v http://download3.vmware.com/software/vmw-tools/esxi_tools_for_guests/esx-tools-for-esxi-9.7.0-0.0.00000.i386.vib -f

Once the VIB has been successfully installed, you will need to reboot the host for the changes to take effect. To verify, you can now login to either your vSphere Web/C# Client and you should now see the status for VMware Tools for your Nested ESXi host showing green and the IP Address of the Nested ESXi host should be displayed.

So why would you want to do this? Well, there’s a couple of reasons actually. The first one is pretty basic, which is when I need to reboot or shutdown a Nested ESXi VM, instead of having to jump into the VM console or SSH into ESXi host, I could just right click in the vSphere Web/C# Client and just say shutdown or reboot. I also tend to do all sorts of craziness in my lab (I’m sure this is an understatement for folks that know me) and may often break networking connectivity to my Nested ESXi VM. In vSphere 5.0, we introduced the Guest Operations API (formally known as VIX API) which is now part of the vSphere API. This API is actually quite handy as it allows you to perform guest operations within the VM without needing network connectivity as it relies on the fact that VMware Tools is running (pretty cool stuff!).

Here is a screenshot demonstrating the executing of vmkfstools through the Guest Operations API to one of my Nested ESXi VM:

A couple of things to note:

  • If you install VMware Tools on Nested ESXi VM, you will NOT be able to just right click in the UI and say install/upgrade
  • If you wish to integrate this into you ESXi image, you can take a look at a community tool  called ESXi-Customizer created by Andreas Peetz which I have used in the past and works great. Image Builder does not support raw VIBs, only zip files which may need to contain additional metadata information. If you want to create an offline bundle instead to then use Image Builder to create your custom ISO, Andreas has a new tool you can take a look at here.

Finally, if you have any feedback (likes/dis-likes), thanks, comments please head over to the VMware's Fling page for VMware Tools for Nested ESXi and leave a comment. I am sure the Jim Mattson the engineer who built this Fling would greatly appreciate any feedback you may have.

More from my site

  • How to run Nested ESXi on top of a VSAN datastore?
  • Quick Tip: New Hyper-V guestOS identifier in vSphere 5.5
  • Nested Virtualization Resources
  • Disabling IPv6 via Command-Line For ESXi 5.1 (Without Automatic Host Reboot)
  • Using PowerCLI to invoke Guest Operations API to a Nested ESXi VM

Categories // ESXi, Nested Virtualization Tags // ESXi 5.0, ESXi 5.1, ESXi 5.5, nested, nested virtualization, vmware tools, vSphere 5.0, vSphere 5.1, vSphere 5.5

Comments

  1. *protectedRemsadQC says

    11/11/2013 at 8:48 pm

    Hi,
    the link http://download3.vmware.com/software/vmw-tools/esxi_tools_for_guests/esx-tools-for-esxi-9.7.0-0.0.00000.i386.zip doesn't work

    File not found 🙁

    Reply
    • *protectedRemsadQC says

      11/11/2013 at 8:57 pm

      The link shoul be http://download3.vmware.com/software/vmw-tools/esxi_tools_for_guests/esx-tools-for-esxi-9.7.0-0.0.00000.i386.vib

      Reply
    • *protectedWilliam Lam says

      11/11/2013 at 10:29 pm

      Thanks. I've fixed the link

      Reply
  2. *protectedRemsadQC says

    11/11/2013 at 8:59 pm

    After esxi reboot, the vmware tools status is "Running, version:9440 (Not installed).

    I can see the IP addresses into the summary tab.

    I have the same status for all nested esxi.

    Reply
    • *protectedWilliam Lam says

      11/11/2013 at 10:29 pm

      What version of Nested ESXi VMs are you running and also what version is the underlying physical host?

      Reply
    • *protectedMasim Vavai Sugianto says

      11/12/2013 at 8:21 pm

      Hi,

      I have similar result, VMware Tools is not installed but vSphere nested host IP displayed correctly. vSphere nested version 5.5 on top of vSphere 5.5

      Reply
    • *protectedWilliam Lam says

      11/13/2013 at 3:04 am

      Looks like this might be some type of odd "caching", we already have a report of it on the communities https://communities.vmware.com/message/2311487#2311487 Engineering will take a look and hopefully have an update soon, however it is installed and running but just not displaying it in the UI/API

      Reply
    • *protectedMasim Vavai Sugianto says

      11/13/2013 at 9:06 am

      Hi,

      Yes, VMware Tools works as expected (I can reboot and shutdown nested vSphere), the only problem so far is VMware Tools installation status (on C# client said : Running, not installed, on Web Client said Running, version:9440 (Not installed)"

      Thank you

      Reply
    • *protectedAndreas Peetz says

      11/13/2013 at 8:17 pm

      For me the issue of the tools being displayed as "Not installed" is resolved after another reboot of the nested host.
      - Andreas

      Reply
  3. *protectedAmmesiah says

    11/12/2013 at 9:33 am

    Amazing work William, thanks from all VM geeks for that !

    Reply
  4. *protectedneocontrast says

    11/15/2013 at 5:34 pm

    Hello,

    Thanks for posting the VMware Tool on ESXI fling, very cool stuff!!!

    I am experiencing a similar problem to what some are seeing. The difference that I have noticed is that failure only happens to some of my nested ESXi hosts. An observation (could be a coiencidence), that tools start on my i7-3840QM and E3-1245 processors (Workstation 10 and ESXi 5.1.0 (799733)) just fine and failed to start on E5-2630 (ESXi 5.1.0 (799733)). I also observed that I needed to use the --no-sig-check switch when installing the vib on the nested hosts on the E5-2630 machine.

    Below is a snippet from the /var/log/syslog.log file of vmtoolsd failing to start. Thoughts?

    2013-11-15T16:19:58Z watchdog-vmtoolsd: [35709] Begin '/usr/sbin/vmtoolsd ++group=host/vim/vimuser/vmtoolsd', min-uptime = 60, max-quick-failures = 1, max-total-failures = 5, bg_pid_file = ''
    2013-11-15T16:19:58Z watchdog-vmtoolsd: Executing '/usr/sbin/vmtoolsd ++group=host/vim/vimuser/vmtoolsd'
    2013-11-15T16:19:58Z vmsvc[35732]: [ warning] [GLib-GObject] invalid (NULL) pointer instance
    2013-11-15T16:19:58Z vmsvc[35732]: [critical] [GLib-GObject] g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    2013-11-15T16:19:58Z vmsvc[35732]: [ message] [vmtoolsd] Tools Version: 9.7.0.00000 (build-00000)
    2013-11-15T16:19:58Z vmsvc[35732]: [ message] [vmsvc] Cannot load message catalog for domain 'hgfsServer', language 'C', catalog dir '/etc/vmware-tools'.
    2013-11-15T16:19:58Z vmsvc[35732]: [ message] [vmsvc] Cannot load message catalog for domain 'vix', language 'C', catalog dir '/etc/vmware-tools'.
    2013-11-15T16:19:58Z vmsvc[35732]: [ message] [vmsvc] Cannot load message catalog for domain 'powerops', language 'C', catalog dir '/etc/vmware-tools'.
    2013-11-15T16:19:58Z vmsvc[35732]: [ message] [vmtoolsd] Shutting down 'vmsvc' service ...
    2013-11-15T16:19:58Z vmsvc[35732]: [ error] [vmsvc] ASSERT bora-vmsoft/lib/rpcChannel/rpcChannel.c:802
    2013-11-15T16:19:58Z watchdog-vmtoolsd: '/usr/sbin/vmtoolsd ++group=host/vim/vimuser/vmtoolsd' exited after 0 seconds (quick failure 1) 134
    2013-11-15T16:19:58Z watchdog-vmtoolsd: Executing '/usr/sbin/vmtoolsd ++group=host/vim/vimuser/vmtoolsd'
    2013-11-15T16:19:58Z vmsvc[35758]: [ warning] [GLib-GObject] invalid (NULL) pointer instance
    2013-11-15T16:19:58Z vmsvc[35758]: [critical] [GLib-GObject] g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    2013-11-15T16:19:58Z vmsvc[35758]: [ message] [vmtoolsd] Tools Version: 9.7.0.00000 (build-00000)
    2013-11-15T16:19:58Z vmsvc[35758]: [ message] [vmsvc] Cannot load message catalog for domain 'hgfsServer', language 'C', catalog dir '/etc/vmware-tools'.
    2013-11-15T16:19:58Z vmsvc[35758]: [ message] [vmsvc] Cannot load message catalog for domain 'vix', language 'C', catalog dir '/etc/vmware-tools'.
    2013-11-15T16:19:58Z vmsvc[35758]: [ message] [vmsvc] Cannot load message catalog for domain 'powerops', language 'C', catalog dir '/etc/vmware-tools'.
    2013-11-15T16:19:58Z vmsvc[35758]: [ message] [vmtoolsd] Shutting down 'vmsvc' service ...
    2013-11-15T16:19:58Z vmsvc[35758]: [ error] [vmsvc] ASSERT bora-vmsoft/lib/rpcChannel/rpcChannel.c:802
    2013-11-15T16:19:58Z watchdog-vmtoolsd: '/usr/sbin/vmtoolsd ++group=host/vim/vimuser/vmtoolsd' exited after 0 seconds (quick failure 2) 134
    2013-11-15T16:19:58Z watchdog-vmtoolsd: End '/usr/sbin/vmtoolsd ++group=host/vim/vimuser/vmtoolsd', failure limit reached

    Reply
  5. *protectedJim says

    11/18/2013 at 8:24 pm

    It sounds like your non-working instance(s) may be picking up the following option:

    monitor_control.restrict_backdoor = TRUE

    This option defeats VMware Tools (for any guest type).

    Reply
  6. *protectedLikeAHoss says

    11/29/2013 at 4:10 am

    This comment has been removed by the author.

    Reply
  7. *protectedJay says

    08/07/2014 at 8:00 pm

    Do you know if vmmemctl is implemented?

    Reply
    • William Lam says

      08/07/2014 at 11:10 pm

      No, it is not.

      Reply
      • *protectedJay says

        08/08/2014 at 1:17 pm

        Drat! Do you know if it will be?

        Reply
        • William Lam says

          08/08/2014 at 3:23 pm

          It's feedback I've already provided to Engineering, so we'll just have to wait and see

          Reply
          • *protectedJay says

            08/08/2014 at 4:00 pm

            Thanks. As much as everyone ends up using nested ESXi, it would be nice to have.

  8. *protectedsoulassassin0220 says

    10/23/2014 at 7:45 pm

    Thanks for this mate, although I needed to add the word "software" in my switch aswell. so it read "esxcli software vib install......"

    Reply
  9. *protectedpeter says

    11/08/2014 at 8:54 pm

    neat they work in fusion as well

    Reply
  10. *protectedRuss says

    04/30/2015 at 12:59 am

    I'm doing something a bit different - running ESXi 5.5U2 and vCenter 5.5U2e (Version 5.5.0 Build 2414847) both as guests under Fusion 7.1.1 Pro. The ESXi guest is unable to sync it's clock to the Fusion clock. It appears the the vmtoolsd is running:

    ~ # ps | grep tool
    35167 35167 vmtoolsd /usr/sbin/vmtoolsd

    But Fusion is not syncing the clock, so perhaps they are incompatible versions. I have the vCenter and ESXi hosts on a private VLAN under Fusion, so internet services like ntpd are unavailable.

    Reply
    • William Lam says

      04/30/2015 at 3:30 am

      I don't think its the incompatible version but potentially that VMware Tools for Nested ESXi may not contain the necessary code for for time sync as it is not the full blown VMware Tools, so it only exposes very basic functionality such as viewing IP Information and being able to run Guest Operations. You will probably have to point your ESXi VM to valid NTP source such as 0.pool.ntp.org unless you have a local NTP instance running

      Reply
      • *protectedRuss says

        06/17/2015 at 8:59 pm

        Hi Walter - I have ntpd configured now, but it when I suspend/resume the esxi host under fusion, it restarts with the date the machine was suspended. Eventually, ntpd corrects it, but it can take a long time.

        However, if you shut it down and reboot it later, then ntpd will correct the time when it starts up. So the trick is to always shut it down (at least until we have vmware tools that can do the time sync correctly).

        BTW, here is a gist that provides an alias to generate the correct esxcli command to set time and date from a mac or linux machine: https://gist.github.com/russt/da5000c909c1e42117ed

        I use it like this: ssh myesxi `esxidate`

        Reply
        • *protectedRuss says

          06/17/2015 at 11:56 pm

          Sorry William for calling you Walter - been watching too much Scorpion I guess.
          Also the command is

          ssh myesxi `esxidate`
          Reply
  11. *protectedJack says

    08/20/2015 at 6:51 pm

    FYI, I just installed a nested ESXi 6 VM and it already came with a vmware-tool:
    Running, version:9536 (Unsupported older version)

    Unfortunately it's already a unsupported older version, but newer than the vib from https://labs.vmware.com/flings/vmware-tools-for-nested-esxi ( I tried it, it shows as version 9441 , not sure why, the screenshot in that url shows 9504 ).

    Any idea where we can get the latest vmware-tool for nested ESXi ?

    Thanks

    -Jack

    Reply
  12. *protectedJason Boche (@jasonboche) says

    08/21/2015 at 1:09 pm

    New version released today!
    esxcli software vib install -v http://download3.vmware.com/software/vmw-tools/esxi_tools_for_guests/esx-tools-for-esxi-9.7.2-0.0.5911061.i386.vib

    Reply
    • William Lam says

      08/21/2015 at 2:27 pm

      Thanks Jason. I actually blogged about it yesterday here http://www.virtuallyghetto.com/2015/08/vmware-tools-for-nested-esxi-updated-to-v1-2.html but I should probably also update this article to mention the update!

      Reply
  13. *protectedBrian says

    02/12/2016 at 12:50 pm

    Looks like these are no longer available, now that 6.x has them built-in?

    Reply
  14. *protectedDmytro says

    06/28/2016 at 12:19 am

    Thanks for the post!

    Reply
  15. *protectedGraham Smith says

    08/08/2023 at 9:58 am

    I don't think this works any more... certainly not with ESXi 7.0.3. nested inside 7.0.3. I have downloaded esx-tools vib but it simply will not install locally. I even tried using a webserver on the same box to install over http but regardless of what I tried it cites a certificate error:

    " ('VMware_bootbank_esx-tools-for-esxi_9.7.0-0.0.00000', 'Could not find a trusted signer: self signed certificate')"

    Reply
    • William Lam says

      08/08/2023 at 3:36 pm

      You don’t need this as VMware Tools has been OOTB for Nested for awhile now 🙂

      Reply

Trackbacks

  1. VMware Lab Part 1, the preparation of a nested ESXi 5.5 | Piszki Lab | EN says:
    03/21/2014 at 11:34 pm

    […] program . This program is used to add to the initial installation image of all we need additional drivers (VIB). According to the instructions on the site, prepare the appropriate installation […]

    Reply
  2. A nugget – VMware tools for Nested ESXi – ESX Virtualization | says:
    05/16/2014 at 4:07 am

    […] William has also published a good post about how the VIX component, now called Guest operations API, which can leverage the use of VMware tools only to execute actions inside the VM (so no network connectivity is necessary), and allows more than just shutdown or reboots… Read William’s article here. […]

    Reply
  3. HowTo: Install Nested ESXi 5.5 | Cloud Solutions Architect says:
    07/26/2014 at 9:56 am

    […] http://www.virtuallyghetto.com/2013/11/w00t-vmware-tools-for-nested-esxi.html […]

    Reply
  4. VMWare Tools for Nested ESXi | Caroline Wood : NET701 Modules says:
    10/16/2014 at 10:13 am

    […] woot! VMware Tools for Nested ESXi! […]

    Reply
  5. Preparing to Learn VMware version 6 | allsidesvirtual says:
    02/09/2015 at 5:04 pm

    […] http://www.virtuallyghetto.com/2013/11/w00t-vmware-tools-for-nested-esxi.html […]

    Reply
  6. Nested Virtualization Resources | virtuallyGhetto says:
    12/15/2015 at 9:06 am

    […] VMware Tools for Nested ESXi  […]

    Reply
  7. VMware Tools is now pre-installed with Nested ESXi 6.0 | virtuallyGhetto says:
    07/06/2016 at 10:41 am

    […] with VMware Tools when running Nested ESXi. This means you no longer have to manually install the VMware Tools for Nested ESXi but ESXi will be able to automatically detect that it is running inside of a VM and automatically […]

    Reply
  8. Using PowerCLI to invoke Guest Operations API to a Nested ESXi VM | virtuallyGhetto says:
    10/25/2016 at 8:10 am

    […] did I find out that there was a known issue with the VMware Tools for Nested ESXi, both the installable VIB and the pre-installed version in ESXi 6.0 on how the guest operations are executed. The good news […]

    Reply
  9. How to properly clone a Nested ESXi VM? | virtuallyGhetto says:
    11/02/2016 at 11:42 am

    […] the IP Address and hostname which you of course can leverage the Guest Operations API if you have VMware Tools for Nested ESXi […]

    Reply
  10. Nested virtualization. Виртуальный ЦОД VMWare или ESXi 5.5 на ESXi 5.5. Часть 1. | Sergey Seregin's Blog says:
    01/16/2017 at 9:16 pm

    […] UPD. VMware tools for NestedESXi […]

    Reply
  11. VMware Tools for ESXi-九州で仮想化するなら株式会社イーアイティ says:
    06/29/2018 at 2:20 am

    […] というわけで、私が以前、以下のブログやコミュニティを元に Nested ESXi に VMware Tools をインストールした手順をご紹介していきたいと思います。 VMware Community – ネステッド ESXi 用の VMware Tools 使ってみました。 virtuallyGhetto – w00t! VMware Tools for Nested ESXi! […]

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • VMware Flings is now available in Free Downloads of Broadcom Support Portal (BSP) 05/19/2025
  • VMUG Connect 2025 - Minimal VMware Cloud Foundation (VCF) 5.x in a Box  05/15/2025
  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025