Greetings,
I'm using the VIX C bindings to call runScriptInGuest. When I make the call when connected to vCenter, I get a seg fault, but when I connect directly to the ESX system, it works fine. Is there something different that I should be aware of when calling through vCenter?
It may not be relevant, but I know the PowerShell wrapper for this function, Invoke-VMScript, seems to require the ESX system host/login info be passed in as parameters. This struck me as odd since the PowerShell session already had an authenticated vCenter connection, but now I'm wondering if certain VIX commands can't be run through vCenter and must be run directly against the ESX host.
Is there anything I should check on the vCenter system to troubleshoot its ability to proxy a VIX call?
Thanks,
- Chris