I have a virtual machine that suddenly won't boot up any more after a reboot and it's giving me the error "no host is compatible with the virtual machine". I tried removing it from the inventory and re-adding it, which fixed a similar issue i had a few months ago but it's not letting me re-add it to the inventory. Has anyone seen this issue or have any recommendations?
...but it's not letting me re-add it to the inventory
what does this mean? Are you getting an error?
See also, just in case
Troy Clavell wrote:
...but it's not letting me re-add it to the inventory
what does this mean? Are you getting an error?
See also, just in case
I'm not getting an error, the option is just grayed out.
you are right clicking on the vmx file to add to inventory? You have proper permissisons within vCenter perform these actions?
Also, my copy and paste didn't quite work, above so I fixed it with the correct link, which is also below
Troy Clavell wrote:
you are right clicking on the vmx file to add to inventory? You have proper permissisons within vCenter perform these actions?
Also, my copy and paste didn't quite work, above so I fixed it with the correct link, which is also below
Yes i am right clicking the vmx file and yes I have the proper permissions. I will check out the link provided, but it looks at first glance like it is unrelated to my issue. Thanks for the help thus far.
I would also look at restarting the management agents on the host in which the guest in question is registered, and maybe even your vCenter Server Service
Troy Clavell wrote:
I would also look at restarting the management agents on the host in which the guest in question is registered, and maybe even your vCenter Server Service
I did restart the management agents on the host it was residing on with no luck. I am hesitant to restart the vCenter Service itself because, while we are not using Lab Manager, this is a lab environment and is very active. Another note, it appears that the VM is locked, although it is not registered in vCenter. I am unable to download or move any of the files.
I was able to resolve my issue, thank you for your help.
How did you resolve the issue?
A reboot (for sure and a certainly a restart) of the vCenter Services resolve this issue
Eric