VMware Cloud Community
drheim
Enthusiast
Enthusiast
Jump to solution

newly created VMs cannot vMotion

I have a new 6.5 cluster and all my VMs can vMotion fine across all 7 new hosts fine.  I created a new VM from a new template that will not vMotion. I have powered it off and disconnected CD-Rom, and network(it was on a portgroup on distributed switch),, but it still will not let me vmotion it to any of the other hosts that all the other VMs can vMotion to.  It is not pegged to a host in a DRS rule, etc. Let me know if anyone has any ideas.

Reply
0 Kudos
1 Solution

Accepted Solutions
drheim
Enthusiast
Enthusiast
Jump to solution

I figured out what it was.  The VM was created by someone else and assigned to a local disk. on the host

View solution in original post

Reply
0 Kudos
5 Replies
a_p_
Leadership
Leadership
Jump to solution

Please check whether the VM is stuck in installing VMware Tools.

André

Reply
0 Kudos
drheim
Enthusiast
Enthusiast
Jump to solution

No - It is on Tools v.13.  My permissions are admin at the vCenter level, but double-checking everything permissions wise as it is weird that I cannot vmotion this new VM anywhere, and I also cannot tell the guest OS to poweroff gracefully.  All other VM functions seems fine.

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

No - It is on Tools v.13.

That's most likely the Hardware Version, not the Tools version.

Anyway, please don't mind me asking you to look for this again. Check whether you see the "Install VMware Tools" option for the VM, or whether it shows s.th. like "Abort/Cancel/end VMware Tools installation".

André

Reply
0 Kudos
drheim
Enthusiast
Enthusiast
Jump to solution

Sorry - Thanks for asking again.  It is not showing Install VMWare Tools as an option..  Guest OS has almost all options greyed out.  It is VM version 13. 

Reply
0 Kudos
drheim
Enthusiast
Enthusiast
Jump to solution

I figured out what it was.  The VM was created by someone else and assigned to a local disk. on the host

Reply
0 Kudos