Vprobes is not yet supported on ESX. Please let VMware know if you'd like to see the support for ESX. I certainly would but they need to hear request for official support from more customers. ...
See more...
Vprobes is not yet supported on ESX. Please let VMware know if you'd like to see the support for ESX. I certainly would but they need to hear request for official support from more customers. Hacking around, I couldn't find a good way to use vProbes for the use case you described. You could use HV-Exit to look for in/outs to the SCSI controller in the VMM (see https://github.com/vmware/vprobe-toolkit/blob/master/cookbook/vt-exit.emt) Otherwise, if you know the vmkernel function or system call for opening a new virtual disk, you could just do: $ vprobe -t FUNCTION_NAME and you'll get a trace of all entries and exits to that function. Not sure if this helps. Can you share more about the use case?
This sounds like a question for a different forum. fwiw: I don't know of a way to use vprobes to provide this access. Vprobes is a facility for binary instrumentation of guest, vmm, vmx and vm...
See more...
This sounds like a question for a different forum. fwiw: I don't know of a way to use vprobes to provide this access. Vprobes is a facility for binary instrumentation of guest, vmm, vmx and vmkernel functions.
You have to know the entry function name if it's a standard vmkernel function. Might also work for a VMware driver. Are you the driver author? If so, look at the VMware driver guide on how to inj...
See more...
You have to know the entry function name if it's a standard vmkernel function. Might also work for a VMware driver. Are you the driver author? If so, look at the VMware driver guide on how to inject your driver symbols in. To trace a function, do this: $ vprobe -t World_Switch Enter: World_Switch Enter: World_Switch Enter: World_Switch Exit: World_Switch retval = 0x41221d265000 Exit: World_Switch retval = 0x412241ce5000 Exit: World_Switch retval = 0x412214925000 Let me know if you need more.
