running ESXi update seems to have no effect

[adamwms]

Hello,

Initial state:

vim-cmd vimsvc/license --show

(...)

Properties:

     [ProductName] = VMware ESX Server

     [ProductVersion] = 6.0

     [count_disabled] = This license is unlimited

     [feature] = vsmp:8 ("Up to 8-way virtual SMP")

     [FileVersion] = 6.0.2.0

(...)

vmware -vl

VMware ESXi 6.0.0 build-3620759

VMware ESXi 6.0.0 Update 2

Running an update:

esxcli software profile update -p ESXi-6.0.0-20181104001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

Update Result

   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

   Reboot Required: true

   VIBs Installed: VMware_bootbank_cpu-microcode_6.0.0-3.100.9313334, VMware_bootbank_ehci-ehci-hcd_1.0-4vmw.600.3.69.5572656, (...)

   VIBs Removed: VMware_bootbank_cpu-microcode_6.0.0-0.0.2494585, VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.600.2.34.3620759, (...)

reboot (twice as after the first one the server struggled with obtaining IP from DHCP)

Version check again:

vmware -vl

VMware ESXi 6.0.0 build-3620759

VMware ESXi 6.0.0 Update 2

Why is it still reporting 6.0.0-2.34.3620759 from 2016-03-02 rather than 6.0.0-3.110.10719132 from 2018-11-04?

Thanks,
Adam

[dbalcaraz]

Hi,

Well it seems that the update didn't apply correctly.

DId you check the esxupdate.log in order to see what the host really did?

Let us know.

[adamwms]

I've just retried it with the same effect - update tool reports success but the version doesn't change.
Update log attached (no warnings or errors).

[dbalcaraz]

I can't see any attachment here.

Weird that you get a success report but well, something is wrong obviously.

Did you try to download the update and apply it locally?

[adamwms]

Hmm, the attachment looks accessible: https://communities.vmware.com/servlet/JiveServlet/download/2823481-213218/esxi.test-2018-12-13-esx...

What are the steps for

download the update and apply it locally

?

[dbalcaraz]

Well, you should just change the depot:

esxcli --server=server_name software profile update --depot=file:///<path_to_profile_ZIP_file>/<profile_ZIP_file> --profile=profile_name

More info: Upgrade or Update a Host with Image Profiles

[adamwms]

The problem is not availability of update images.

I have downloaded ESXi600-201811001.zip and ran:

esxcli software profile update -d /vmfs/volumes/datastore1/ESXi600-201811001.zip -p ESXi-6.0.0-20181104001-standard

(...)

Message: The update completed successfully

After first reboot ESXi reports build 10719132 (2018-11) on the console but at the same time the following message is displayed:

No compatible network adapter found. Please consult the product's Hardware Compatibility Guide (HCG) for a list of supported adapters.

Switching to a static IP doesn't help and the only recovery option is a reboot.

After reboot ESXi decides to roll everything back to the previous build 3620759 (2016-03) which is generally a good safe choice.

So my issue has something to do with running ESXi in a VirtualBox VM in Ubuntu 16 Linux and NIC settings / drivers.

[adamwms]

More info: Upgrade or Update a Host with Image Profiles

The esxcli software profile update command brings the entire content of the ESXi host image to the same level as the corresponding upgrade method using an ISO installer. However, the ISO installer performs a pre-upgrade check for potential problems, such as insufficient memory or unsupported devices.

This would probably highlight my NIC problem before proceeding with the update and I would like to give it a try.

Question: where do I get ESXi 6.0.0 (2018-11) ISO from?

The latest one listed here: VMware vSphere with Operations Management is 6.0 U1b (2016-01-07) which is even older to what I currently have installed.

[dbalcaraz]

I see, it's not problem of the image nor the location.

If it rollbacks automatically, then the install was wrong obviously.

[dbalcaraz]

Search for the VMware vSphere product without "Operations Management".

I found this (you must logon in your account): https://my.vmware.com/group/vmware/info?slug=datacenter_cloud_infrastructure/vmware_vsphere/6_0

[cheese2]

So you're running ESXi inside a VirtualBox VM?  AFAIK nesting ESX inside any non-VMware virtualization product is not supported, in which case I'm not surprised the installer is having difficulty identifying the vnic created by VirtualBox.  Have you tried running ESX inside VMware player instead?  I've had success with it in the past.

[adamwms]

I can't really find what you've suggested.
Most downloads are unavailable saying:

You either are not entitled or do not have permissions to download this product.

Check with your My VMware Super User, Procurement Contact or Administrator.

If you recently purchased this product through VMware Store or through a third-party, try downloading later.

Any point asking VMware support without a support contract?

[adamwms]

I can confirm that update of a VMware Player VM running ESXi went ok.
The only minor problem I had was getting bridged networking working.
Ended up using NAT.