Solved

vmware esxi, vmrc character limit for target in shortcut?

Posted on 2010-08-19
6
2,959 Views
Last Modified: 2012-05-10
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.
0
Comment
Question by:snowdog_2112
  • 4
  • 2
6 Comments
 
LVL 28

Accepted Solution

by:
bgoering earned 500 total points
ID: 33495316
Looking at your test case it would appear that you are hitting a character limit, but have not been able to find any documentation to support that.

From this post on VMware server 2 (http://communities.vmware.com/message/999988) to find the MOID

" you can specify the VM by either datastore path, or managed object ID (a.k.a. "Moe ID"). You can determine the moid for a VM by looking at vmInventory.xml in /etc/vmware/hostd/ or %ALLUSERSPROFILE%\Application Data\VMware\VMware Server\hostd as appropriate."

The vmInventory.xml file also works for ESX/ESXi to find the MOID.

If you are on the VMware Server 2.x platform you could also obtain an newer version of vmware-vmrc by installing either (1) the vSphere 4.1 client, or (2) the VMware Guest Console (VGC) Fling from http://labs.vmware.com/flings/vgc. I don't know if that alleviates the 64 character limit but it might be worth a try.

Good Luck
0
 
LVL 28

Expert Comment

by:bgoering
ID: 33495348
Also note that if using the path (rather than the MOID) don't actually include the -m parameter. It should be:

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.
0
 

Author Comment

by:snowdog_2112
ID: 33503179
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.
0
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 

Author Comment

by:snowdog_2112
ID: 33503224
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/vmInventory.xml file works.

Maybe this can be considered documentation to verify this for someone else!
0
 

Author Closing Comment

by:snowdog_2112
ID: 33503242
-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!
0
 

Author Comment

by:snowdog_2112
ID: 34034850
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"
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now