Maintenance mode can get stuck at 2% progress when there are still active VMs running on that ESX host. An ESX or ESXi Server will not complete going into maintenance mode until there are no running VMs running on it.
If you have HA configured it should automatically vmotion off the VMs to another ESX host with enough resources. If your also using DRS it will do some load balancing and also work out any affinity rules.
What can stop VMs from vmotioning automatically to another host is:
- CD/Floppy still attached to VM - If so remove it
- The virtual machine vNIC is attached to an internal only network or a vSwitch not available on another ESX server - Check spellings of vSwitches and which network type the VM isconnected to.
- VMtools currently installing in the Virtual Machine - Wait for install to complete or cancel the installation.
- The virtual machine is stored on a datastore local to that ESX host - The VM needs to be on a centralized datastore (SAN etc) that is availble to another ESX host.
Share this blog post on social media:
Tweet
Latest Blog Posts
- vSphere 7 U1 - Part 3 - Creating a Datacenter, HA/DRS Cluster and Adding a Host
- vSphere 7 U1 - Part 2 - Deploying vCenter 7.0 U1 VCSA
- vSphere 7 U1 - Part 1 - Installing ESXi 7.0 U1
- Veeam CBT Data is Invalid - Reset CBT Without Powering Off VM
- View Administrator Blank Error Dialog/Window After Upgrade