vmtoolsd not running on nested ESXi

[admin]

Hi Jim,

I have 2 nested ESXi running with esx-tools-for-esxi-9.7.0-0.0.00000.i386.vib installed but both of them the daemon is not starting (I assume vmtoolsd is the right service to check)

From nested ESXi

/var/log # /etc/init.d/vmtoolsd start

vmtoolsd started

/var/log # /etc/init.d/vmtoolsd status

vmtoolsd is not running

This is what I can see from /var/log/vmkernel.log

2014-01-27T08:07:43.817Z cpu1:46568)User: 2742: wantCoreDump : vmtoolsd -enabled : 0

2014-01-27T08:07:43.841Z cpu0:46570)User: 2742: wantCoreDump : vmtoolsd -enabled : 0

Attached vmware.log

[admin]

I wouldn't recommend running this guest with shadow paging, but that shouldn't affect VMware Tools.

For the best performance and usabiliity, remove these lines from your .vmx file:

monitor.virtual_mmu = software

monitor.virtual_exec = hardware

and add the following line:

vhv.enable = TRUE

Please create /etc/vmware-tools/toolsd.conf inside the ESXi VM with the following contents:

[logging]
log = true

vmtoolsd.level = debug
vmtoolsd.handler = file
vmtoolsd.data = /tmp/vmtoolsd.log

Then, try to start /usr/sbin/vmtoolsd manually.

Upload your vmkernel.log file and /tmp/vmtoolsd.log.

[admin]

Hi Jim

Following your step I get to Running (Not Installed) same as the guys heer Re: Nested ESX tools show up as Running (Not Installed)

Attached vmkernel.log, weirdly it doesn't generate /tmp/vmtoolsd.log

My physical ESXi i 5.5

Thanks.

[admin]

My bad.  That should have been vmtoolsd.conf.

Anyway, it sounds like things are working for you now (aside from needing to restart hostd), so you shouldn't need that logging.