in my case, the same problem occurred when changing the vMotion user interface for the migration of the vm
comparing with an updated host that just before restarting it changed the vMotion interface to vmk1, review the advanced options and this had a change that in other hosts was not updated:
"Migrate.Vmknic"
by default, the option has the value "vmk0", and in others it was empty, so I was changing in each host by the interface "vmk1" or "vmk2" according to each case
It would be interesting if someone else happens to the problem can try using the advanced options and indicate if this solves the problem
↧
Re: vMotion Gets Auto Enabled at Random on Management Port Group - Is there a reason?
↧