VMware Cloud Community
MotokiN
Contributor
Contributor

The differences between ESXi5.0 update1 and update3, original image and HP custom image

Hi, I found very strange situatuion, as writing in subject.

When I updated the ESXi Server (installed with ESXi5.0 update1 HP custom image) with ESXi5.0 update3 HP custom image.

and I found specified driver version is different, in comparison with installed directry with ESXi5.0 update3 HP custom image.

belowi will write some some of the crues.

according to the image configuration data,

1: ESXi5.0 update1 HP custom image

      <vib>

        <vibVersion>1.4.5</vibVersion>

        <vibID>VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.1.11.623860</vibID>

        <name>ata-pata-amd</name>

        <version>0.3.10-3vmw.500.1.11.623860</version>

        <vendor>VMware</vendor>

        <vibType>bootbank</vibType>

        <summary>pata_amd: ata driver for VMware ESX</summary>

        <systemReqs>

          <maintenanceMode>true</maintenanceMode>

          <swPlatform locale="" version="5.*" productLineID="embeddedEsx"/>

        </systemReqs>

        <relationships>

          <depends>

            <constraint name="vmkapi_2_0_0_0"/>

            <constraint name="com.vmware.driverAPI-9.2.0.0"/>

            <constraint name="com.vmware.libata-9.2.0.0"/>

          </depends>

          <conflicts/>

          <replaces/>

          <provides/>

          <compatibleWith/>

        </relationships>

        <postInstall>

          <rebootRequired>true</rebootRequired>

          <hostdRestart>false</hostdRestart>

        </postInstall>

        <softwareTags>

          <tag>driver</tag>

          <tag>module</tag>

        </softwareTags>

        <vibFile>

          <sourceUrl>zip:C:\MXDK\buildagent\work\MTX_SOURCE_PATH\hp-esxi50-iso\vmware-bundles\VMware-ESXi-5.0.0-623860-depot.zip?vib20/ata-pata-amd/VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.1.11.623860.vib</sourceUrl>

          <relativePath>vib20/ata-pata-amd/VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.1.11.623860.vib</relativePath>

          <packedSize>14324</packedSize>

          <checksum>

            <checksumType>sha-256</checksumType>

            <checksum>25df7dd0ed62a301b0f2e591a2b6e1b18c9624076af44704f5a1cd829ed8032c</checksum>

          </checksum>

        </vibFile>

      </vib>

2: ESXi5.0 update3 HP custom image

      <vib>

        <vibVersion>1.4.5</vibVersion>

        <vibID>VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512</vibID>

        <name>ata-pata-amd</name>

        <version>0.3.10-3vmw.500.0.0.469512</version>

        <vendor>VMware</vendor>

        <vibType>bootbank</vibType>

        <summary>pata_amd: ata driver for VMware ESX</summary>

        <systemReqs>

          <maintenanceMode>true</maintenanceMode>

          <swPlatform locale="" version="5.*" productLineID="embeddedEsx"/>

        </systemReqs>

        <relationships>

          <depends>

            <constraint name="vmkapi_2_0_0_0"/>

            <constraint name="com.vmware.driverAPI-9.2.0.0"/>

            <constraint name="com.vmware.libata-9.2.0.0"/>

          </depends>

          <conflicts/>

          <replaces/>

          <provides/>

          <compatibleWith/>

        </relationships>

        <postInstall>

          <rebootRequired>true</rebootRequired>

          <hostdRestart>false</hostdRestart>

        </postInstall>

        <softwareTags>

          <tag>driver</tag>

          <tag>module</tag>

        </softwareTags>

        <vibFile>

          <sourceUrl>zip:C:\MXDK\buildagent\work\MTX_SOURCE_PATH\hp-esxi50-iso\vmware-bundles\update-from-esxi5.0-5.0_update03.zip?vib20/ata-pata-amd/VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512.vib</sourceUrl>

          <relativePath>vib20/ata-pata-amd/VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512.vib</relativePath>

          <packedSize>14314</packedSize>

          <checksum>

            <checksumType>sha-256</checksumType>

            <checksum>e5a3c6409200f4ff708a08d838cd1fd057b8feb63d62841e57442b12cb657687</checksum>

          </checksum>

        </vibFile>

      </vib>

I think if I update ESXi5.0 update1 to update3 ,VMware_bootbank_ata-pata-amd  version could be 500.1.11.623860. but if I install directry with ESXi5.0 update3 HP custom image,

the VMware_bootbank_ata-pata-amd  version could be 0.3.10-3vmw.500.0.0.469512.

I suspect the composer in VMware made a mistake to select the baseline image for update3.

May I have some idea for that. I am now very  embarrassed about this.

0 Kudos
0 Replies