A. Mikkelsen VMware ESX scripts, commands, tools and other nice to know things that will make your virtualization days easier!!!!

Sunday, July 18, 2010

19 Comments »

  1. Thank you SO MUCH. This has made my upgrade from 4.0 to 4.1 so PAINLESS!!

    Great guide.

    Comment by Cameron — Wednesday, July 21, 2010 @ 5:20 am

  2. Thanks.

    Comment by A. Mikkelsen — Wednesday, July 21, 2010 @ 12:56 pm

  3. Hello Anders,
    Tripped over this little gem of an article. Now, being a nearly newbie in the upgrading-esxi business, I like to ask you to erase a few doubts;
    My scenario is to upgrade a esxi 3.5 box to 4.1. I have dl an upgrade package: upgrade-from-ESXi3.5-to-4.1.0-0.0.260247-release.zip. Extracted to a folder, it has the same name(!). In it, I have a “metadata.xml”. I do not see a “metadata.zip” anywhere. Please help connect the dots 🙂

    Thanks,
    – Christian

    Comment by Christian — Tuesday, September 21, 2010 @ 9:34 am

  4. Hi Christian,
    Have you tried the Host Update utility?
    Have you tried with the “metadata.xml”?

    A. Mikkelsen

    Comment by A. Mikkelsen — Tuesday, September 21, 2010 @ 12:14 pm

  5. Christian,
    I don’t think this solution will work on 3.5.
    You have to use the Host Update Utility.

    A. MIkkelsen

    Comment by A. Mikkelsen — Tuesday, September 21, 2010 @ 12:20 pm

  6. If you get the error:

    /vmfs/volumes/4a97b524-063cb5d9-ff13-0030489c63a8/upgrade # esxupdate update -m metadata.zip
    metadata.zip ######################################################################## [100%]

    vmware-esx-tools-light-4.1.0-0.0.260247.i386.vib ###### ( 9%)
    Encountered error FileIOError:
    The error data is:
    Filename – None
    Message – I/O Error (28) on file : [Errno 28] No space left on device
    Errno – 10
    Description – Unable to create, write or read a file as expected.

    then go to the Config-GUI and relacte /tmp/scratch to your local datastore, reboot and it should work …

    Comment by Thomas von Siebenthal — Tuesday, September 21, 2010 @ 12:30 pm

  7. “Hi Christian,
    Have you tried the Host Update utility?
    Have you tried with the “metadata.xml”?”

    No. I must admit I didn’t have the courage to experiment with metadata.xml
    The Host Update utility seems difficult to find on VMWares site. What package could it be in?

    Thanks,
    – Christian

    Comment by Christian — Tuesday, September 21, 2010 @ 18:32 pm

  8. Hi Christian,
    If you install the vSphere Client you are asked if you want to install the HostUpdate Utility
    I not sure if the HostUpdate Utillity is avaiable in the vSphere Client in the free version of ESXi.
    But it is in the vSphere Client version from vCenter.

    A. Mikkelsen

    Comment by A. Mikkelsen — Wednesday, September 22, 2010 @ 9:02 am

  9. Hello Anders,

    thank you very much for this great guide!

    One question to the configuration of the ESXi host. Will this be kept after the upgrade? Can I restart the updated host with the “old” configuration or is there a way to save the configuration and then to restore after the upgrade?

    Thanks, Tom

    Comment by Tom — Wednesday, November 10, 2010 @ 11:02 am

  10. Hi Tom,
    The configuration is kept after upgrade.
    To backup the configuration, please read one of the following guides.
    http://professionalvmware.com/2010/05/how-to-backup-esxi-configuration-the-missing-piece/comment-page-1/
    http://communities.vmware.com/thread/231705
    The guides also explain how to restore 🙂

    A. Mikkelsen

    Comment by A. Mikkelsen — Wednesday, November 10, 2010 @ 14:27 pm

  11. Thank you for this information. Great!

    Comment by Tom — Tuesday, November 23, 2010 @ 10:39 am

  12. Glad to be able to help ..

    A. Mikkelsen

    Comment by A. Mikkelsen — Tuesday, November 23, 2010 @ 12:06 pm

  13. Brill… thanks….

    Comment by R de Vos — Wednesday, December 15, 2010 @ 12:48 pm

  14. Glad to be able to help

    Comment by A. Mikkelsen — Wednesday, December 15, 2010 @ 22:04 pm

  15. tx. worked.

    Comment by alex — Friday, February 25, 2011 @ 21:08 pm

  16. Hello!

    This description is work!!! Excelent!!! 🙂
    Thank You this!
    I can upgrade my system 4.0 to 4.1 ESXi !!!!

    Comment by Tibor Kiss — Thursday, May 5, 2011 @ 13:07 pm

  17. Hi Tibor,
    Glad to be able to help.
    A. Mikkelsen

    Comment by A. Mikkelsen — Friday, May 6, 2011 @ 12:28 pm

  18. Thank you. This worked for me to upgrade from v4.0 to v4.1-Update1. I had physical access to the host, so I used the console there. Alt-F1, then type “unsupported”, then you’ll be prompted for a password.

    Comment by Andre Lombard — Thursday, May 19, 2011 @ 22:54 pm

  19. Thanks for your feedback.
    A. Mikkelsen

    Comment by A. Mikkelsen — Saturday, May 21, 2011 @ 16:45 pm

RSS feed for comments on this post. TrackBack URL

Leave a comment

Powered by WordPress