HI there,
Just have a silly question.
I got 2 ESX server enabled with HA and DRS.
The 1st ESX with 2 running VM, is it possible to start the "Maintanence Mode" at that moment.
will it migrate all live VM to the other host? or i need to manually stop that 2 VM?
Thanks
Normally it will just VMotion the VM's across to the other Host unless either of the 2 VM's have any dependencies or affinities on that Host or they have CD-ROM/Floppy images inserted.
If it cannot VMotion the VM's off it will not enter maintainence mode.
Simon
However, The Enter maintanence mode task just stuck at 2%.
When i tried to shut down all live VMs, then the task continue to flow and complete.
What is happening?
thanks
This normally means that there is a dependancy to the Host. To help find out what is going on follow these steps;
1. Turn the VM's on
2. Try to Migrate each VM across to the other Host
If there is a dependancy on one of the VM's it will not allow you to Migrate it and it should give you a Error sign with a little discription of why the operation cannot be complete. You will see this information in the Migration Wizard when you select the other Host as the Host that you want to Migrate to.
Simon
yup, i did the manual migration and it works fine.
But it just doesn't work by executing the "Enter maintanence mode".
For the events, it states "Unable to automatically migrate VMXXXX"
so werid.
thanks
I take it you can enter Maintanence Mode when either there are no VM's on the Host or all VM's are Shut Down?
Simon
DRS need to be configured as "fully automated" for this to work, as well.
i did it. but still in vain.
thanks
I got the same issue with ESX 3.5 update 3, which i am testing in the lab.
The maintenance mode stays at 2%, and i get unable to automatically migrate "vm" from "esxhost1"
The HA option are set allow availabilty contraints etc. When i turn off HA, i can set a host into maintenance mode, without problems.
I had a closer look at the release notes, and it looks like a know issue. It looks like they re-added an old bug back again.
For me a good reason to wait a couple of months, this bug should be fixed first.
It's a known issue indeed. Rob is absolutely correct.
Duncan
Blogging: http://www.yellow-bricks.com
If you find this information useful, please award points for "correct" or "helpful".
Duncan,
Do you have any insight info when this bug will be fixed?
We are retesting ESX 3.5 Update 3, with the latest patches buildnumber 143128. And now maintenance mode works again, also with 2 hosts.
I did an upgrade with VUM, and also tested it with fresh new installations.
The patches from last januari fixed a lot of problems.