plz paste error screen shot
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.
What browser are you using? Have you tried a different one?
Same here. Using ESXI 6.5 and almost always a missing host under available VMotion resource. Tried Firefox, Chrome, IE, Safari and they are all the same.
■ 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?
Cluster Setup.jpg 112.7 K
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.
1 person found this helpful
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.
I ran into this problem too .
I've upgraded from VCSA 6.0 to VCSA 6.5 .
Any update or fix on this , apart from opening the VM console as suggested on this thread ?
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.
1 person found this helpful
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.
Thanks for advice. Pointing CD to vmtools iso or any other iso on shared storage worked it out. I see now other hosts accessible for vMotion.
Same here! I just migrated from v5.5 to v6.5 and it only happened to one of my Windows 7 vm box. I tried other Windows and it worked fine.