ChocolateRain
asked on
Can't vMotion or Storage vMotion anything since upgrading vCenter to 5.0
Moved my vCenter server to a VM. This moved me from 4.1 to 5.0.
Have 2 ESXi 4.x servers and 1 ESXi 5.0 server under the vCenter datacenter.
I can't move any VMs even when they are powered off (vMotion or Storage vMotion).
This is between the 4.x servers themselves or between the 4.x servers and the 5.x servers.
When I try and do a Storage vMotion on a powered-off computer: Call "EnvironmentBrowser.QueryC
Have 2 ESXi 4.x servers and 1 ESXi 5.0 server under the vCenter datacenter.
I can't move any VMs even when they are powered off (vMotion or Storage vMotion).
This is between the 4.x servers themselves or between the 4.x servers and the 5.x servers.
When I try and do a Storage vMotion on a powered-off computer: Call "EnvironmentBrowser.QueryC
ASKER
vMotion is enabled on 2 of the 3 servers. The ESXi 5.0 server presently only has 2 NICs (LAN and SAN) and therefore should still be able to at least do Storage vMotion. But it doesn't even make it that far; when I try and do anything vMotion related it fails with this message.
All servers are licensed.
Shared Storage is consistent, all are connected to the SAN, the SAN management console shows them all as connected and they are all running VMs on the same SAN LUN.
All servers are licensed.
Shared Storage is consistent, all are connected to the SAN, the SAN management console shows them all as connected and they are all running VMs on the same SAN LUN.
So if you hightlight a VM, which is powered on and select Migrate....
what happens, when does the error occur?
what happens, when does the error occur?
Does validation complete OKAY?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you checked all licenses are present on all hosts?
Shared Storage is consistent across hosts?