VMware Cloud Community
nava_thulasi39

Unable to add the virtual machine to the inventory

Hi,

Recently I come across issue while restarting the virtual machine. So I have unregistered the virtual machine and when I try to add it to inventory the option was grayed out.

So I tried to add through ESXi command, after adding it, it didn't show the VM in Vcenter inventory.

Hence I created 1 more vmx file, now I have the option to add it to the Inventory - But the error is "A virtual machine or template having the same  name is already registered."

In the Inventory, I couldn't find the name.. Even in esxi servers too.

Experts, Could you please help me to resolve this issue now? Thanks in advance.

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
8 Replies
farkasharry
Hot Shot
Hot Shot

Can you find it in the inventory by browsing it? I mean not over serach but browsing to it?
I had a similar issue: I could not find the VM with the search option but could find it by browsing the inventory. It turned out to be a missing folder path entry. I moved the VM to the root folder, then back to the correct one. The path was added and the VM was findable over search.

*** If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful! *** vExpert 2019, VCAP-DCA,VCP,MCSE,MCITS and some more...
Reply
0 Kudos
vmhyperv
Contributor
Contributor

Hi,

Please logout from the VI client and try to login again.As its says the "A virtual machine or template having the same  name is already registered." One more thing did you remove the vm from inventory properly.

Thanks

vmguy

Reply
0 Kudos
nava_thulasi39

Hi,

Thanks for the reply.

I am afraid, I didn't get what you mean?

You mean, Datastore Inventory Browse?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
nava_thulasi39

Thanks for the reply. Smiley Happy

1. Please logout from the VI client and try to login again.As its says the "A virtual machine or template having the same  name is already registered."

- I have done many times.

2. One more thing did you remove the vm from inventory properly.

- I am afraid, I have unregistered using Vsphere client as well as ESXi console. Now the problem is, I don't fine the VM anywhere.

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
farkasharry
Hot Shot
Hot Shot

I mean when you are clicking through your ESX hosts and the virtual machines, not using the search window in the upper-right corner of the vSphere client.

*** If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful! *** vExpert 2019, VCAP-DCA,VCP,MCSE,MCITS and some more...
Reply
0 Kudos
farkasharry
Hot Shot
Hot Shot

there is a way to find out where the VM is. Logon to the host over ssh (or dcgui) and run esxtop to see if the VM is running on it. Then shut it down and unregister it again over the command line.

*** If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful! *** vExpert 2019, VCAP-DCA,VCP,MCSE,MCITS and some more...
Reply
0 Kudos
nava_thulasi39

Hi,

You put some lights on my issue.

Through esxtop, I could see the VM (worldid) is running.

But when I see the list of the VM by pressing V, it's not available in the list. And using the world id i couldn't kill that process (kill worldid)

Any further tips to resolve the issue?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
FSvcoe
Enthusiast
Enthusiast

I'm sure you've gotten this resolved by now...but :smileylaugh:...

We had this happen recently with an 8 node ESXi 4.1 cluster. One of the fibre switches went south, causing a hiccup with the paths back to the SAN ( We have Powerpath installed-but that's another story). Two of the hosts we just couldn't get reconnected to VC, depsite multiple efforts and restarting the mgmt agent via the services.sh script. After rebooting, a number of the VM's were grayed out while attempting to right click and choose Power..Power on, or trying to edit settings. We could remove from VC inventory, but were unable to add back in.

Turns out, our issue was a lock that got obtained from one of the other hosts in the cluster. When we rebooted the first, some of the VM's restarted on other hosts, but some tried to start (and failed) from the second host that was also having the mgmt agent issue. Running 'VMKFSTOOLS -D <vmname>.vmx displayed the info that we traced back to the MAC of the host that had the lock. Once we knew where it was running, we could resolve on the appropriate host.

untitled.JPG

Hoefully this will help someone, really kind of a headscratcher with the second host involved. The KB below is also helpful in troubleshooting this.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051

Reply
0 Kudos