ESXi/vSphere 5.5 U2: old NFS/vMotion issue reincarnated “remote host IP_Address failed with status Busy”

Uh oh, an old issue seems to have been reincarnated in vSphere 5.5 U2 which may cause vMotions of guests on NFS storage to fail with the error: remote host IP_Address failed with status Busy

This issue was first evident some time ago where it affected V4.1 and was subsequently fixed (albeit temporarily) with ESXi 4.1 u2 +.

See the original KB here  with the workaround for those who can’t/couldn’t upgrade; These things happen, we just have to deal with them.

To workaround this issue when you do not want to upgrade, you must modify the swap type setting on both the source and target host.
To modify the setting:
  1. Launch the vSphere Client and log in to your vCenter Server.
  2. Select the source ESX host and then click the Configuration tab.
  3. Click Software > Advanced Settings > Migrate.
  4. Under the Migrate options, locate the line containing Migrate.VMotionResolveSwapType. By default, it is set to 1.
  5. Change the value to 0.
  6. Click OK.
  7. Repeat Steps 2 to 6 for the destination host.

….but when you have a cluster of many hosts, that’s going to take waaaaaay tooooo long. So, of course, we’re going to speed that up with PowerCLI !

Check your hosts (filter the host list via cluster/datacenter; (I’m filtering to a DEV cluster with 4 hosts)

25-02-2015 7-03-19 PM

Change them;

25-02-2015 7-03-35 PM

Verify change

25-02-2015 7-03-55 PM

Keep an eye on the KB, no doubt a patch will be forthcoming.

Job Done. Don’t be CLI shy.



Related Post

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: