A notice about a potential interaction between ESX Server 3.0.1 and VirtualCenter 2.5 just shot through my e-mail, and I thought it important enough to post here.
According to this VMware KB document, any ESX Server running version 3.0.1 should have patch ESX-7557441 installed before VirtualCenter is upgraded to version 2.5. If this patch is not installed, it’s possible that virtual machines which are configured to automatically start or stop will unexpectedly reboot when VirtualCenter is upgraded to version 2.5. Since VirtualCenter has to be upgraded before you can start upgrading your ESX Servers, then this could definitely be an issue.
More information on why this may occur is provided in this related VMware KB article.
This may be a fairly rare situation, since (tongue in cheek) organizations always make sure that their ESX Servers are kept patched. (OK, you can stop laughing now.) Seriously, though, if you do still have servers running ESX 3.0.1 be sure to apply this patch before starting along your upgrade path.
Tags: ESX, Virtualization, VMware
3 comments
Comments feed for this article
Trackback link
http://blog.scottlowe.org/2008/01/10/esx-server-301-patch-needed-for-vc-25/trackback/
Friday, January 18, 2008 at 10:22 pm
Rich
I think your post (and this problem) explains what happened to me at a client that I was helping upgrade to VI3.5 this week. We upgraded VC. Then we connected several ESX 3.0.2 hosts without any issues. We started connecting ESX 3.0.1 hosts and all of a sudden my client’s phone start ringing because a file server VM is no longer available. Sure enough it had rebooted, but not only did it reboot the properties of the virtual nic no longer had the “connected box” checked. I wish I would have read this post on Monday ….
Tuesday, January 22, 2008 at 6:52 am
slowe
Rich,
I wish I had posted this sooner! I could have saved you some trouble.
Sunday, February 3, 2008 at 10:14 am
vijaysys
Hi Scott
some inputs need for the following scenario: I have added additional 20 GB of disk space to one of my virtual machine(which has linux os). Do i need to reboot the Virtual machine, to configure new file system for the extra space added….
Thanks
regards
vijay