snowdog_2112
asked on
vmware esxi, vmrc character limit for target in shortcut?
Is there a 64 character limit in the -m parameter of the vmrc command line?
I have one guest with 65 characters in the -m "[datastore1] folder/vm_name.vmx" parameter, and I can't connect to it using vmrc. Other guests with less than 64 characters work fine.
(I don't know how to find the MOID to try the -M option and verify that I can connect that way).
I'm getting errors trying to connect to a guest using VMRC from 2 different machines. One a Win7 workstation, the error is:
Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe: The system cannot find the file specified.
From another workstation, I get an error about username/password.
I have one guest with 65 characters in the -m "[datastore1] folder/vm_name.vmx" parameter, and I can't connect to it using vmrc. Other guests with less than 64 characters work fine.
(I don't know how to find the MOID to try the -M option and verify that I can connect that way).
I'm getting errors trying to connect to a guest using VMRC from 2 different machines. One a Win7 workstation, the error is:
Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe:
From another workstation, I get an error about username/password.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think you can use -m (lowercase) for the path, and -M (uppercase)when specifying the MOID (i.e., case sensitive).
The same command works for the other Server 2003 guests on this esxi host, which leads me back to the character limit - the non-working guest is the only one near/past 64 characters.
I'll try the moid - if I can find that - and report back.
The same command works for the other Server 2003 guests on this esxi host, which leads me back to the character limit - the non-working guest is the only one near/past 64 characters.
I'll try the moid - if I can find that - and report back.
ASKER
AHA! That seems to be the case:
-m "[datastore1] path/filename.vmx" format must be less than 64 characters, and must have a space after the [datastore] name.
-M 64 where the "64" is the moid found in the /etc/vmware/hostd/vmInvent ory.xml file works.
Maybe this can be considered documentation to verify this for someone else!
-m "[datastore1] path/filename.vmx" format must be less than 64 characters, and must have a space after the [datastore] name.
-M 64 where the "64" is the moid found in the /etc/vmware/hostd/vmInvent
Maybe this can be considered documentation to verify this for someone else!
ASKER
-m "[datastore] path/filename.vmx
must be less than 64 characters including the "[ ]"'s and all spaces.
-M [n]
where [n] is the moid - do not include the "[" and "]" in the command line.
Thanks!
must be less than 64 characters including the "[ ]"'s and all spaces.
-M [n]
where [n] is the moid - do not include the "[" and "]" in the command line.
Thanks!
ASKER
bgoering -
You are correct about the -m (lowercase) when connecting to an ESX/ESXi host. The -m can be used when connecting to a VMware Server 2.x host.
In fact, if you include -m when connecting to an ESX host, the vmrc window does not even pop open. That was a head-scratcher for me for a while.
oh..and in my previous post, I see I forgot the closing " on the first line. It should be:
-m "[datastore] path/filename.vmx"
You are correct about the -m (lowercase) when connecting to an ESX/ESXi host. The -m can be used when connecting to a VMware Server 2.x host.
In fact, if you include -m when connecting to an ESX host, the vmrc window does not even pop open. That was a head-scratcher for me for a while.
oh..and in my previous post, I see I forgot the closing " on the first line. It should be:
-m "[datastore] path/filename.vmx"
vmware-vmrc -h hostname:port -u <username> -p <password> "[datastore1] folder/vm_name.vmx"
From what I have been able to determine including the -m can cause your login errors.