Hi,
Please have a look at the explanation >http://blogs.vmware.com/vsphere/2012/02/understanding-esxi-patches-finding-patches.html
Kyle Gleed said:
↧
Channel:
VMware Communities: Message List
X
Are you the publisher?
Claim or
contact us
about this channel.
X
0
Channel Details:
- Title: VMware Communities: Message List
- Channel Number: 7575849
- Language: English
- Registered On: January 5, 2013, 3:31 am
- Number of Articles: 232869
- Latest Snapshot: November 6, 2020, 7:21 pm
- RSS URL: http://communities.vmware.com/community/feeds/messages?rssusername=jorad
- Publisher: https://communities.vmware.com/?view=discussions
- Description: Most recent forum messages
- Catalog: //communities994.rssing.com/catalog.php?indx=7575849
© 2024 //www.rssing.com
Say Patch01 includes updates for the following VIBs: “esxi-base”, “driver10″ and “driver 44″. And then later Patch02 comes out with updates to “esxi-base”, “driver20″ and “driver 44″.
P2 is cumulative in that the “esxi-base” and “driver44″ VIBs will include the updates in Patch01. However, it’s important to note that Patch02 not include the “driver 10″ VIB as that module was not updated.
So yes patches are cumulative, but you need to pay attention to the VIBs included in each patch as we may not include all VIBs with the patch.
Note, if we update VIB the patch will include any dependent VIBs even if they weren’t updated.
So the chances are that you're likely missing some updates....