I am pretty interested in testing the new functionality of vMotion as it has been announced at VMworld a few days ago in San Francisco. This is how it is described on VMWare website:
"vSphere vMotion – Leverage the advantages of vMotion (zero-downtime migration) without the need for shared storage configurations. This new vMotion capability applies to the entire network."
Looks wonderful, isn't it? So i decided to upgrade some of my ESXi running on ProLiant BL460c G7 servers from vSphere 5.0.0-768111 to vSphere 5.1.0-799733 using the file 'VMware-ESXi-5.1.0-799733-HP-5.30.28.iso' which has just been released from VMWare for HP servers.
These are my screenshot of the upgrade:
|Current version is ESXi 5.0.0-768111|
|Selecting the ISO for ESXi5.1|
|VMFS selection for upgrade|
|Here you can choose between a fresh install or an upgrade|
|ESXi succesfully upgraded to 5.1|
Apparently everything went well, but it has not. My ESXi has been upgraded but it is no more recognised by my VirtualCenter instance, which is still sitting at 5.0. The error I get says: "A general system error occurred. Timed waiting for vpxa to start"...
It definitively looks like I cannot manage ESXi 5.1 hosts from VirtualCenter 5.0. What a pity. I have to downgrade because I don't feel like passing to VirtualCenter 5.1 right now as we don't have any information about stability on this version. Has anyone of you already upgraded VirtualCenter to version 5.1? Please let me know how your upgrade went and if it is as stable as it should.
For completeness, here's a few useful links to 5.1 products:
- vSphere 5.1 release notes
- VirtualCenter 5.1 and modules
- vSphere PowerCLI 5.1
- vSphere vCloud Director 5.1
- vSphere 5.1 configuration maximums
- vSphere 5.1 what's new
- vCenter 5.1 what's new