Invalid VMs in the inventory

[vmhyperv]

Hi VMware team,

        We have VMs in the inventory that showing invalid but we can do RDP and its pingable.Any help on this will be much appreaciated.Please find the screenshot.

thanks

vmguy

[UmeshAhuja]

Hi,

Try to restart the management agent on the host, will solve the problem

[UmeshAhuja]

Hi,

If restarting the management agent doesnt work then go for the step mention in the below link

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

[vmhyperv]

Hi,

  I tried all the steps as per kb but after removing the vms from inventory i am not able to add it back.Once i browse data store,Right click vm then add to inventory option is greyedout. :smileysad:

vmguy

[a_p_]

Has the datastore been presented to e.g. a Windows host at any time? I'd recommend you run fdisk -lu on the host to verify thet all VMFS datastore partitions still show up with the correct partition type "FB" (opposed to "07" for NTFS)

André

[vmhyperv]

hi,

I executed the command fdisk -lu  which shows FB vmfs partition table.Please  FA

vmguy

[UmeshAhuja]

Hi,

From the host console  add the VM again in vCenter with the vmware-cmd option:

vmware-cmd –s register servername.vmx

Will show you the register vm list

vmware-cmd -l

http://blog.vmpros.nl/wp-content/uploads/2010/06/image19.png

[vmhyperv]

Hi,

  I added the vm from console since its esxi4.1

vim-cmd solo/registervm /vmfs/volumes/datastore_name/VM_directory/VM_name.vmx

but output is 1056  :smileysad:

regards

vmguy

[vmhyperv]

Hi,

finally opened SR with VMware and they suggested that re-booting ESXi will fix the issue.So waiting for outage approval.

Thanks

vmguy

[john23]

can you check vmware.log for invalid vm as well hostd.log...any observation

[a_p_]

Do the VM's have something in common, e.g. the same datastore? This could be the result of an issue with the datastore.

André

[vmhyperv]

Yes all the invalid VMs  were using same data store

thanks
vmguy