To find out about these dependencies you can use the esxcli software vib get command in an ESXi shell. They can require another VIB package (or even a specific version of another VIB package) to be installed, or they might rely on features (certain libraries, function sets or interfaces) that are provided by other VIB packages.
VIB packages can have dependencies on each other which are defined in their metadata.
HP ESXI 6.0 DOWNLOAD UPDATE
But this does not cause the same update issue. (which adds support for Intel Jacksonville NICs) whereas ESXi 6.0 still includes an older version 2.5.4-6. This is an unusual exception, but not the only one of its kind: Since Update 3 ESXi 5.5 also includes a net-e1000e driver package of version 3.2.2.1-2. ( tl dr? If you just want to know the resolution of the issue then skip to the next paragraph So what are the workarounds?) Version strings are interpreted from left to right, so the package included in the ESXi 5.5 Update 3b ImageProfile (version 1.0-3.) is considered newer than the ones included in any of the ESXi 6.0 ImageProfiles (version 1.0-2.). With ESXi 5.5 Update 3b the xhci-xhci VIB that is mentioned in the error message was updated to version 1.0-3vmw.550.547 ( extending USB 3.0 support), but in ESXi 6.0 the version number of this package currently is 1.0-2vmw.600.758. Sure there are workarounds, and once you understand the root cause of the issue they are easy to find. What are our options in this situation, are there really no workarounds?
0 kommentar(er)
