I've just completed an upgrade from 3 x ESXi 5.0 hosts and a vCenter 5.1 appliance (Essentials Plus) to ESXi 6.0.5050593 and VCSA 6.5.5973321. This is a fully supported VMware setup. I upgraded the licenses and applied them to the new setup ok.
One very strange observation is that when I try and vmotion a VM to another host, if I select 'Change compute resource only', invariably the only destination host I'll see is the host the VM is currently running on - no other cluster hosts will show. If though, I select 'Change both compute resource and storage', I can expand the cluster and see all hosts. This method of migrating the VM will work, but I have to 'fake' a datastore change selection.
Things I've verified are;
It happens in both the Flash and HTML UI's.
Sometimes I will see all the migration hosts, but not all the time and very inconsistently
The message pre-migration will always show 'Compatability checks succeeded'.
I thought initially it was out of date VMware Tools, and it certainly looked more promising when tools was updated to 10.0.9 (build 10249), but then it all seemed to revert back and the same things happen. Is this a bug? I know I'm not running the latest ESXi version, or even the latest build of ESXi 6.0, but I'm not quite ready for that yet. It never happened in 5.x.
Thanks, but there isn't any error. Almost always, I just don't visibly see any other host to migrate to other than the host the VM is currently running on when stepping through the 'migrate' wizard. As I have the vMotion license, I should see all hosts in the cluster.
■ Verify that you have at least two ESXi hosts that are licensed for vMotion or are in evaluation mode.
■Verify that you have running instances of vCenter Server and the vSphere Web Client.
■Verify that hosts have access to shared storage of a supported type, such as Fibre Channel, iSCSI, or NAS.
■Verify that the source and destination hosts have compatible CPUs.
■Verify that hosts have access to the same physical networks.
■Verify that you have at least one active Gigabit Ethernet adapter on each host.
■Virtual machine files must be on shared storage visible by the hosts.
■Virtual machines must run a supported operating system.
■Virtual machines must not have a connection to a virtual media device with a mounted local image.
■Virtual machines must not have a connection to an internal vSwitch that is not connected to a physical network.
■Virtual machines must have access to the same subnets.
■Virtual machines must not have CPU affinity configured.
If you found my answers useful please consider marking them as Correct OR Helpful
First ensure that Vmotion is Enabled(@Vmkernel port ->properties) at both Hosts which you are trying to migrate th vm's.
Check there are resources available where you are trying to migrate.
This may help you out!!
Please reply if it is helpful for you so I can share my views in this blog!!
Having this same problem and hoping for a little help, please.
Company is rolling out vSphere 6.5 in January, and have built out a home lab. Successfully have VCSA, two Hosts in a cluster, and a VM running Ubuntu.
vMotion, HA, DRS are all enabled, have a shared iSCSI storage (OpenFiler) but when attempting to migrate the VM between Hosts the selection displays ONLY the Host being migrated from?
Being a relative Newb to networking--can someone please point me to what is missing?
It is 6.5 which is relatively new so it is POSSIBLE that there is a bug, I'm no vExpert or VCDX but I'll out that out there.
My actionable theory would be the vmotion network, as others have stated,
make sure that checkbox is checked at the portgroup level,
vlan id matches,
ips in the same subnet,
only one portgroup has vmotion enabled,
do some vmkpings through ssh if you can.
We have seen this problem with vCenter 6.5 and vSphere 6 hosts. Weirdly, if you open the console for the VM you are trying to migrate, then close it and try again all the hosts appear in the window. We have a call raised with VMware, but nothing they've attempted has resolved the issue so far. VMware say it's an issue with DRS, but we're on standard license, so not using it.
Same problem here with VCSA 6.5 lastest update.
It looks like a bug with the client interface because we can run vmotion with powercli without any problem.
But the web GUI, sometimes don't show us all the hosts available but only the host where the vm is running.
As proposed by admedsol,
Open the console and close it immediately after seems to unlock the list 😃
Do you have any official answer from VMware about your case/problem ? You can pressure them ... because you are NOT alone.
It 's definitely a bug.
I had the same problem, but it was due to local datastore I used to mount iso file when installing VM. I had CD/DVD not connected but even that local datastore was listed in "Related Objects" in VM's summary tab. I changed to iso on shared datastore (not connected) and all hosts are available to be destination compute resource in migrate wizard.
We just added a new 6.5 host and ran into this and I found this -> VMware Knowledge Base
EVC mode mismatch causes virtual machine migration issues (2014835)
The VM's can have a different EVC Mode than the host they are running on. Don't know how it would have happened but there is a solution in the KB article.
I had several vm's running on a EVC mode older then any of our current CPU's. Any of those VM's with the older EVC modes would not see the new host. The really weird thing is that the host we just add was the exact same cpu as 2 hosts we upgraded 6 months ago, and the VM's with the old EVC mode can see those just fine. Only difference is the new server was not upgraded from previous release but a fresh install of ESXi 6.5
Hope this helps.
we have seen this issue when we try to choose only compute it will not list all the esxi host and workaround would be using both both compute and storage option which would list all the esxi hosts it seems to be an issue with api used when we choose only compute during migration