ESX Virtualization

VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....

Nakivo Backup and Replication - #1 Backup solution for Virtual, physical, cloud, NAS and SaaS

Updating ESXi 4.1 to Update 1 brings an error vim.fault.noHost

By | Last Updated:

Shares

When I was trying to update the latest Update 1 I got an error on one host.

The error message says Install error on host: error details: vim.fault.noHost. It was quite strange since both other hosts I was updating went smooth without any errors. I was trying to apply those patches via CLI without success either. Then I did a quick research on Google and I found a reply on a VMware communities here.

Then I took a quick look at my host, and there were 2 orphaned VMs which were pointing to disconnected datastore, which wasn't used anymore. I did unregister those 2 VMs and try to patch the host again. The problem was solved and the host patched successfully.

A quote from the solution:

If you have any invalid, inaccessible or orphaned VMs (like me) in the inventory, you should unregister those virtual machines and try again with update in Update Manager.

Works for me.

vim.Fault.NoHost error when patching VMware ESXi4.1 to Update 1

To unregister an orpaned VM from the host just do like this:

How to remove orphaned VM from inventory

01. Rightclick the orphaned VM

02. Remove from Inventory.

You should normally be able to apply the latest patches for your ESX(i) host. It seems that the VI client is a bit faster, more responsive.

Does anyone has the same feeling?

Shares
Vote !

About Vladan SEGET

This website is maintained by Vladan SEGET. Vladan is as an Independent consultant, professional blogger, vExpert x16, Veeam Vanguard x9, VCAP-DCA/DCD, ESX Virtualization site has started as a simple bookmarking site, but quickly found a large following of readers and subscribers.

Connect on: Facebook. Feel free to network via Twitter @vladan.

Comments

  3. Vladan says

    It was a community effort, the credit goes there… -:)

    btw, why don’t you guys use Gravatar to get a picture/logo with your name…?

  4. Silvio says

    Hi,

    thx. This was a nice hint. I had the same problems with error “vim.fault.noHost” at one of five hosts. Your post helped alot. Thx!!!

  5. Richard says

    Sweet post m8!

    Got this error on one of my hosts after upgrading 12 other. This made my day!

  7. Jean-Francois Leroux says

    I had the same error in ESXi 4.1.
    No VMs were orphaned, but I had a Virtual Lab created in this particular host.
    Had to unregister the Lab and then the update went through without a problem. Your tip proved very useful. Kudos!