vprobe test.vp vmware-vprobe: Failed to load script in vmkernel: cannot enable probe "VMM1Hz" Not found Looks like vp scripts are no longer preferred and Emmet (.emt) is the way to do things....
See more...
vprobe test.vp vmware-vprobe: Failed to load script in vmkernel: cannot enable probe "VMM1Hz" Not found Looks like vp scripts are no longer preferred and Emmet (.emt) is the way to do things. At least, my super quick experiment here has been much more productive with emmett than with vp. Try creating test.emt with the following contents: VMM:VMM1Hz printf("testing\n"); then run: vprobe -m /vmfs/volumes/<volume>/linux/linux.vmx test.emt and it should be up and running. The -m option accepts either a full path to the .vmx file or the VMID of the vm, as shown by the vim-cmd vmsvc/getallvms command at the ESXi shell. and this error vprobe -c test.vp -m /vmfs/volumes/<volume number>/linux/linux.vmx vmware-vprobe: Compile error: Syntax error: <cmdline>: line 1, token '.' You don't want the -c option here... that tells the vprobe utility to use the next argument as the literal text of an Emmett script to run. In your case, you end up trying to run a script consisting of the literal text test.vp (not the contents of the file with that name), hence the error reported at the '.' token (which doesn't even exist within the file test.vp... but does exist in the text "test.vp"). For instance, you can run a "hello world" Emmett script against VMID 1 like this: vprobe -m 1 -c 'VMM:VMM1Hz printf("Hi there\n");' Cheers, -- Darius
