Build number is the same after applying ESX400-200912001

[clopmz]

Hi all,

I have a strange problem. I have applied ESX400-200912001bundle to my ESX4 host and build conintues at "VMware ESX 4.0.0 build-208167". If this correct?? On another ESXi server build has changed to 219382 ....

Thanks.

[vmroyale]

Hello.

I have a strange problem. I have applied ESX400-200912001bundle to my ESX4 host and build conintues at "VMware ESX 4.0.0 build-208167". If this correct?? On another ESXi server build has changed to 219382 ....

It is probably correct. Check out kb 1012514 for detailed information on how build numbers work.

Good Luck!

[AndreTheGiant]

See also:

Andre

[bio]

Still confusing.. According to those vmware KB articles the command vmware -v will show the build number of the vmware kernel.

Also ESX400-200912401-BG states that the vmkernel will be updated

Also running command rpm -qa | grep -i vmware shows : vmware-esx-vmkernel64-4.0.0-1.10.219382

Then why it shows the wrong build number ?

bio...

[RonTom42]

I don't think it is correct. VMware forgets to update their build number record (stored somewhere on the ESX) from time to time wen releasing patches. It's very annoying for those of us that are trying to help VMware's customers to stay up to date. So VMware, please add another point to the QA checklist for patch releases.

[g_5]

Hi everybody,

We've got exactly the same issue on a four nodes "ESX 4 Update 1 Build 208167" Cluster which has been patched with the ESX400-200912001 bundle (normaly change build number to 219382).

Someone found a workaround (if it is the appropriate term) ?

Regards