assafk Tracker

working with Guest User Mapping to run commands over guest OS

assafk — Tue, 19 Nov 2019 11:49:07 GMT

Hi All

i am trying to understand how can i run commands over a Guest Os using VMware SDK

here is the working code for running a command using VMware SDK ( in c#)

var processMgr = new ManagedObjectReference { type = "GuestProcessManager", Value = "guestOperationsProcessManager" };

var auth = new NamePasswordAuthentication { username = @"theGuestOsUser", password = "TheGuesOsPassword", interactiveSession = false };

var progSpec = new GuestProgramSpec { programPath = @"C:\Windows\System32\ipconfig.exe", arguments = "" };

var vmRef = new ManagedObjectReference { type = "VirtualMachine", Value = "vm-164" };

var pid = vimService.StartProgramInGuest(processMgr, vmRef, auth, progSpec);

as i could understand to be able to run commands on the VM with different SSO user

i need to go the Guest User Section and add the relevant SSO user

as you could see i've added: local user(root) / domain user (administrator)

as describe in the documentation

Configuring User Mappings on Guest Operating Systems

You must configure VMs to accept X.509 certificates. X.509 certificates allow the vSphere administrators in your data center to use SAML tokens issued by single sign-on service to access guest OSs.

the only related thread i could find is this one

https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.wssdk.dsg.doc_50%2Fsdk_sg_server_certificate_Appendix.6.4.html

can anyone explain what does it means to configure vm the accept x.509 certificates?

of at least point me to a thread the explain what needs to be done so this code will work

var processMgr = new ManagedObjectReference { type = "GuestProcessManager", Value = "guestOperationsProcessManager" };

var auth = new NamePasswordAuthentication { username = @"root@localos", password = "TheSSOPassword", interactiveSession = false };

var progSpec = new GuestProgramSpec { programPath = @"C:\Windows\System32\ipconfig.exe", arguments = "" };

var vmRef = new ManagedObjectReference { type = "VirtualMachine", Value = "vm-164" };

var pid = vimService.StartProgramInGuest(processMgr, vmRef, auth, progSpec);

thanks

Re: Invoke-VMScript "The guest operations agent could not be contacted."

assafk — Mon, 28 Oct 2019 14:02:07 GMT

the same issue happened to me.

i've logged into the VM and restarted the VMtools service

and the problem was resolved

Failed to connect to VC using VixHost_Connect getting 22003 error message

assafk — Thu, 10 Oct 2019 06:10:00 GMT

Hi All
i'm starting to use the VIX api, and i'm getting 22003 error message

this is the code

NOTE:

* i am running this code using VS 2017 , .net 4.72

the VC is 6.5

For vSphere, the VIX API was deprecated in 2012, as announced in the VIX 1.11 Release Notes. VIX 1.14 was the last supported release for vSphere. VIX is no longer supported with in 6.5 and VMware Tools 10.1.0 and later.

https://stackoverflow.com/questions/54868060/vmware-esxi-6-7-guest-os-password

VixError err;

char *vmxPath;

VixHandle hostHandle = VIX_INVALID_HANDLE;

VixHandle jobHandle = VIX_INVALID_HANDLE;

VixHandle vmHandle = VIX_INVALID_HANDLE;

jobHandle = VixHost_Connect(VIX_API_VERSION,

//VIX_SERVICEPROVIDER_DEFAULT,

VIX_SERVICEPROVIDER_VMWARE_VI_SERVER,

"THE_VC_IP_ADDRESS", // *hostName,

0, // hostPort,

"root", // *userName,

"THE_VC_PASSWORD", // *password,

0, // options,

VIX_INVALID_HANDLE, // propertyListHandle,

NULL, // *callbackProc,

NULL); // *clientData);

err = VixJob_Wait(jobHandle,

VIX_PROPERTY_JOB_RESULT_HANDLE,

&hostHandle,

VIX_PROPERTY_NONE);

am i missing something ?

Re: Errors 22002 and 22003 with VixHost_Connect()

assafk — Mon, 07 Oct 2019 14:05:17 GMT

i've experianced the same issue , but i think there is somthing that i am missing here

these are the steps that i've done :

1 . install the vmware vix API over my local machine (nothing special here) got only some asseblies and several code example

2. created a c++ project over VS2017 i've used the VixAllProductsDyn.dll

2.1 - project complies and runs without but VixHost_Connect failes to connect with error code 22003

this is the code sample

VixError err;

char *vmxPath;

VixHandle hostHandle = VIX_INVALID_HANDLE;

VixHandle jobHandle = VIX_INVALID_HANDLE;

VixHandle vmHandle = VIX_INVALID_HANDLE;

jobHandle = VixHost_Connect(VIX_API_VERSION,

//VIX_SERVICEPROVIDER_DEFAULT,

VIX_SERVICEPROVIDER_VMWARE_VI_SERVER,

"THE_VC_IP_ADDRESS", // *hostName,

0, // hostPort,

"THE_VC_USER_NAME", // *userName,

"THE_VC_PASSWORD", // *password,

0, // options,

VIX_INVALID_HANDLE, // propertyListHandle,

NULL, // *callbackProc,

NULL); // *clientData);

err = VixJob_Wait(jobHandle,

VIX_PROPERTY_JOB_RESULT_HANDLE,

&hostHandle,

VIX_PROPERTY_NONE);

if (VIX_FAILED(err)) {

std::cout << "connection failed " << err;

}

i dont believe i need to install the VIX over my VC

am i missing somthing ?

Re: vshpare 6.7 install plugin

assafk — Tue, 17 Apr 2018 07:12:35 GMT

i think my question wasn't clear enough.

our company has created a plugin that is currently works with other vSphare versions

the installation of the plugin is done via the vmware api.

when trying to install the plugin on 6.7 versoin , the installation is done without any exceptions

still although the vSphare logs shows that the plugin was successfully verified , plugin is not added

do you believe it is still related the BETA ?

thanks

vshpare 6.7 install plugin

assafk — Mon, 09 Apr 2018 16:07:25 GMT

Hi All

hope anyone could help on this one , we are trying to install a plugin on the vshpare 6.7 without any success

i could find this link which points that the flex and web client are going to be deprecated

Goodbye vSphere Client for Windows (C#) – Hello HTML5 - VMware vSphere Blog

but they are still available on the UI

when trying to install the plugin with the api calling the RegisterExtension function ( available on the VimService)

i could find some related logs on the VC

[2018-02-26T10:10:21.229+02:00] [WARN ] session-init-pool-8 70000091 100006 200004 com.vmware.vise.extensionfw.impl.PackageManifestParser Plugin version mismatch for com.MyPlugin.plugin between the plugin registration info (3.0)

and the version specified in plugin-package.xml (4.1). The registration version will be used but you should keep them in sync.

Line 114806: [2018-02-26T10:10:21.265+02:00] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Started validating com.MyPlugin.plugin:3.0

Line 114829: [2018-02-26T10:10:21.266+02:00] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Finished validating com.MyPlugin.plugin:3.0

[2018-02-26T11:00:03.427+02:00] [WARN ] data-service-pool-794 70000674 100003 200006 c.v.vsphere.client.vcextension.impl.ManagedByPropertyProvider ManagedObjectReference: type = VirtualMachine, value = vm-82, serverGuid = 4f57e45b-f53c-4c2b-8b6a-b64d72af7c15 specifies a managedBy relation to an extension with the key com.MyPlugin.plugin but no such extension is registered

does anyone has experienced the same issue when trying to install plugins on 6.7 ?

anyone knows it installing plugins on 6.7 is available ?

thanks

fail to install plugin with error "cannot open locale file for writing"

assafk — Mon, 25 Dec 2017 09:14:27 GMT

while trying to install plugin on VC environment

i'm getting this error

2017-11-01T12:17:34.309+01:00 [00872 error 'vpxdvpxdMoExtensionManager' opID=5c89a933] [ExtensionManagerMo] Failed: cannot open locale file for writing: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\MyPlugin\locale\en\extension.vmsg

2017-11-01T12:17:34.316+01:00 [00872 info 'commonvpxLro' opID=5c89a933] [VpxLRO] -- FINISH task-internal-4840 -- -- vim.ExtensionManager.registerExtension --

2017-11-01T12:17:34.316+01:00 [00872 info 'Default' opID=5c89a933] [VpxLRO] -- ERROR task-internal-4840 -- -- vim.ExtensionManager.registerExtension: vmodl.fault.SystemError:

--> Result:

--> (vmodl.fault.SystemError) {

--> dynamicType = <unset>,

--> faultCause = (vmodl.MethodFault) null,

--> reason = "Cannot open locale file for writing.",

--> msg = "",

--> }

--> Args:

i will try to give as much information as i can on the enviroment

1. the VC is installed on with Dutch settings ( i am not sure the english is available vc )

2. the user running the install is an admin on the VC .

3. user login the the VC machine is a domain admin

4. the vcenter server service is running under local system account - not sure this one is related since i've managed to install different plugin

Re: .sdd.sf folder after Storage vMotion

assafk — Sun, 26 Jul 2015 14:27:25 GMT

for every new top level directory i create on the vsan, the total of these files consume over 700MB, not so small.

Has anyone received any response from VMWare about this?