Re: vmtoolsd and 'No value found'

Hi all,

The whole thing with "guestinfo"  worked for me after a little fix. The following example illustrates he case:

$ vmware-cmd --config esxi-24 "[DS_104.24_150] LTSP2/LTSP2.vmx" setguestinfo myTest "hello world"
setguestinfo(myTest hello world) = 1
$ vmware-cmd --config esxi-24 "[DS_104.24_150] LTSP2/LTSP2.vmx" getguestinfo myTest
getguestinfo(myTest) = hello world
$ vmtoolsd --cmd "info-get guestinfo.myTest"
No value found
$ vmtoolsd --cmd "info-get myTest"
Invalid key name supplied
$ vmware-cmd --config esxi-24 "[DS_104.24_150] LTSP2/LTSP2.vmx" setguestinfo guestinfo.myTest "bla-bla-bla"
setguestinfo(guestinfo.myTest bla-bla-bla) = 1
$ vmware-cmd --config esxi-24 "[DS_104.24_150] LTSP2/LTSP2.vmx" getguestinfo guestinfo.myTest
getguestinfo(guestinfo.myTest) = bla-bla-bla
$ vmtoolsd --cmd "info-get guestinfo.myTest"
bla-bla-bla

Some details:

1. All commands were issued from a virtualized linux box (LTSP2) which has vCLI installed on
2. File "esxi-24" contains login credentials to access corresponding hypervisor (host for LTSP2)
3. DS_104.24_150 is the datastore on "esxi-24" hypervisor

Conclusions:

1. You can use vmware-cmd (remotely via vCLI) to set and get guestinfo parameters
2. Only those params which have "guestinfo." prefix are available to be accessed from "vmtoolsd" daemon.