When placing a host in Maintenance Mode, VC no longer VMotions VMs automatically. It has to be done manually. The workaround is to disable HA in the cluster or manually VMotion the VMs to another host myself.
Note that DRS will still VMotion VMs around in a cluster. It's just the Maintenance Mode function where VMotion isn't working automatically.
This is a valuable time saving feature that got broke and an integral component of VMware Update Manager. Please fix ASAP.
Thank you,
Jas
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Minneapolis Area VMware User Group Leader
My case # through HP is 3603346583 opened 9/23/08.
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Minneapolis Area VMware User Group Leader
My case has been escalated to VMware.
The VMware SR # is 1137883191
HP has told me that VMware plans to address this issue and release the fix in u3.
VMware has also issued internal KB 1002412 which I don't think I have access to but trust it addresses my issue.
I gather this is the last significant communication I will hear about this until VMware releases the fix in u3 (or sooner through a patch hopefully).
Jas
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Minneapolis Area VMware User Group Leader
Here is what i found regarding
Although I have not yet seen this happen, I have definatly heard of this. Seems there are quite a few "issues" that U2 has caused. Maybe U3 will fix them all
Yep - saw that, unfortunately doesn't the issue I'm having. It was an easy one to try though.
Waiting for u3 could be a long wait. I believe this issue should be fixed sooner through a patch. Update Manager is now a much more manual process again.
There is another related discussion that may soon emerge which carries MUCH more signifcance but more on that later. I need to do a little testing to see if I'm impacted by that as well.
Thank you Troy.
Jas
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Minneapolis Area VMware User Group Leader
There is another related discussion that may soon emerge which carries MUCH more signifcance but more on that later. I need to do a little testing to see if I'm impacted by that as well.
it doesn't have anything to do with hostd spawns does it?
There is another related discussion that may soon emerge which carries MUCH more signifcance but more on that later. I need to do a little testing to see if I'm impacted by that as well.
it doesn't have anything to do with hostd spawns does it?
No.
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Minneapolis Area VMware User Group Leader
I spent some time on the phone today with a VMware employee regarding the SR that was opened with VMware on this issue.
VMware confirms two things:
1. The root cause of the issue is VirtualCenter 2.5u2
2. The fix will be coming in u3. The only time frame they would guarantee delivery of u3 is by the end of this year
Until then, the offered workarounds are:
1. Manually VMotion VMs
2. Disable HA
Jas
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Minneapolis Area VMware User Group Leader
Hi
This is relevant to this issue I believe http://www.vmwarewolf.com/host-wont-go-into-maintenance-mode/
Interesting response to the issue you logged Jason
Cheers
David
Hi
This is relevant to this issue I believe http://www.vmwarewolf.com/host-wont-go-into-maintenance-mode/
Interesting response to the issue you logged Jason
Cheers
David
It is the exact issue. Well, half of it anyway. I tried contacting vmwarewolf to give him the other half of the pertinant information to post but I couldn't find any way to contact him on his site, his "add comments" on his article doesn't work, and my guessed email attempts to administrator and webmaster at vmwarewolf dot com both bounced.
The other symptom that hasn't really been talked about yet is that when this issue is present, VMs cannot be powered on (for the same reason - VI thinks they would violate resource constraints).
Jas
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Minneapolis Area VMware User Group Leader
I just blogged about it, this issue has been addressed with Update 3 for VirtualCenter.
Duncan
Blogging: http://www.yellow-bricks.com
If you find this information useful, please award points for "correct" or "helpful".
Hi,
I'm with the same problem with a 2 hosts cluster, i'm using VC 2.5 U3, if i disable HA i'm able to put the host in Maintenance Mode.
After all this VC release did not correct the problem.
Regards,
Goodspeed