Producent oprogramowania do wirtualizacji Vmware udostępnił najnowszą wersją dla rodziny 8.0 o numerze wersji 1a. Dzięki aktualizacji, zostały rozwiązane problem z utratę połączenia z siecią, gdy na hostach ESXi używano interfejsów sieciowych z obsługą protokołu LRO (Large Receive Offload). Ponadto, aktualizacja pozbyła się błędu związanego z konfiguracją i zarządzaniem portami vSphere Distributed Switch (VDS). Od nowszej wersji, poprawiono wydajność i stabilność migawek wirtualnych maszyn, co przyspiesza proces tworzenia, przywracania i migracji migawek. Po więcej informacji, zapraszam do dalszej części materiału.
Rozwiązane problemy:
ESXi_8.0.1-0.10.21813344
|
Patch Category |
Bugfix |
|
Patch Severity |
Critical |
|
Host Reboot Required |
Yes |
|
Virtual Machine Migration or Shutdown Required |
Yes |
|
Affected Hardware |
N/A |
|
Affected Software |
N/A |
|
Affected VIBs |
|
|
PRs Fixed |
3217456 |
|
CVE numbers |
N/A |
This patch updates the vsan VIB. Due to their dependency with the esx-base VIB, the following VIBs are updated with build number and patch version changes, but deliver no fixes: trx, bmcal-esxio, bmcal, vsanhealth, clusterstore, esx-dvfilter-generic-fastpath, native-misc-drivers, esxio-dvfilter-generic-fastpath, esxio-combiner, crx, gc, vdfs, gc-esxio, esx-base, esxio-combiner-esxio, native-misc-drivers-esxio, esxio-base, vds-vsip, esx-xserver, cpu-microcode, and esxio
-
vSAN hosts with deduplication and compression might fail after upgrade to ESXi 8.0 Update 1
This issue occurs only on vSAN all-flash hosts with deduplication and compression enabled and only when:
-
You have an existing disk group created on a vSAN version earlier than vSAN 7.0 Update 3.
-
You have added new capacity disks to such a disk group.
-
You upgrade the vSAN host to ESXi 8.0 Update 1.
The issue does not impact vSAN hosts with compression-only or checksum-only disk groups.
ESXi 8.0 Update 1 includes a background scanner to collect metadata. This background scanner might not recognize new disks added to an existing disk group. This issue can cause the ESXi host to fail with a purple diagnostic screen. Because the host fails and reboots before the background scan completes, repeated failures might occur.
The following details appear in the backtrace:
Panic Details: Crash at 2023-05-01T11:31:12.957Z on CPU 51 running world2019239 - VSAN_0x450080017780_PLOG. VMK Uptime:0:09:54:11.108Panic Message: @BlueScreen: Failed at bora/modules/vmkernel/plog/dedup/dedup_util.h:231 -- VMK_ASSERT(blkNum < DDPGetEndBlkNumber(&ddCtx->devices[devIndex].sb, blkType, blkNumCheck, 1))For more information, see VMware knowledge base article 92458.
This issue is resolved in this release.
-
esx-update_8.0.1-0.10.21813344
|
Patch Category |
Bugfix |
|
Patch Severity |
Critical |
|
Host Reboot Required |
Yes |
|
Virtual Machine Migration or Shutdown Required |
Yes |
|
Affected Hardware |
N/A |
|
Affected Software |
N/A |
|
Affected VIBs |
|
|
PRs Fixed |
N/A |
|
CVE numbers |
N/A |
Due to their dependency with the esx-base VIB, the following VIBs are updated with build number and patch version changes, but deliver no fixes: esx-update and loadesx.
esxio-update_8.0.1-0.10.21813344
|
Patch Category |
Bugfix |
|
Patch Severity |
Critical |
|
Host Reboot Required |
Yes |
|
Virtual Machine Migration or Shutdown Required |
Yes |
|
Affected Hardware |
N/A |
|
Affected Software |
N/A |
|
Affected VIBs |
|
|
PRs Fixed |
N/A |
|
CVE numbers |
N/A |
Due to their dependency with the esx-base VIB, the following VIBs are updated with build number and patch version changes, but deliver no fixes: esxio-update and loadesxio.
ESXi-8.0U1a-21813344-standard
|
Profile Name |
ESXi-8.0U1a-21813344-standard |
|
Build |
For build information, see Patches Contained in This Release. |
|
Vendor |
VMware, Inc. |
|
Release Date |
June 1, 2023 |
|
Acceptance Level |
Partner Supported |
|
Affected Hardware |
N/A |
|
Affected Software |
N/A |
|
Affected VIBs |
|
|
PRs Fixed |
3154255 |
|
Related CVE numbers |
N/A |
This patch updates the following issue:
This issue occurs only on vSAN all-flash hosts with deduplication and compression enabled and only when:
-
You have an existing disk group created on a vSAN version earlier than vSAN 7.0 Update 3.
-
You have added new capacity disks to such a disk group.
-
You upgrade the vSAN host to ESXi 8.0 Update 1.
The issue does not impact vSAN hosts with compression-only or checksum-only disk groups.
ESXi 8.0 Update 1 includes a background scanner to collect metadata. This background scanner might not recognize new disks added to an existing disk group. This issue can cause the ESXi host to fail with a purple diagnostic screen. Because the host fails and reboots before the background scan completes, repeated failures might occur.
The following details appear in the backtrace:
Panic Details: Crash at 2023-05-01T11:31:12.957Z on CPU 51 running world
2019239 - VSAN_0x450080017780_PLOG. VMK Uptime:0:09:54:11.108
Panic Message: @BlueScreen: Failed at bora/modules/vmkernel/plog/dedup/dedup_util.h:231 -- VMK_ASSERT(blkNum < DDPGetEndBlkNumber(&ddCtx->devices[devIndex].sb, blkType, blkNumCheck, 1))
For more information, see VMware knowledge base article 92458.
ESXi-8.0U1a-21813344-no-tools
|
Profile Name |
ESXi-8.0U1a-21813344-no-tools |
|
Build |
For build information, see Patches Contained in This Release. |
|
Vendor |
VMware, Inc. |
|
Release Date |
June 1, 2023 |
|
Acceptance Level |
Partner Supported |
|
Affected Hardware |
N/A |
|
Affected Software |
N/A |
|
Affected VIBs |
|
|
PRs Fixed |
3154255 |
|
Related CVE numbers |
N/A |
This patch updates the following issue:
This issue occurs only on vSAN all-flash hosts with deduplication and compression enabled and only when:
-
You have an existing disk group created on a vSAN version earlier than vSAN 7.0 Update 3.
-
You have added new capacity disks to such a disk group.
-
You upgrade the vSAN host to ESXi 8.0 Update 1.
The issue does not impact vSAN hosts with compression-only or checksum-only disk groups.
ESXi 8.0 Update 1 includes a background scanner to collect metadata. This background scanner might not recognize new disks added to an existing disk group. This issue can cause the ESXi host to fail with a purple diagnostic screen. Because the host fails and reboots before the background scan completes, repeated failures might occur.
The following details appear in the backtrace:
Panic Details: Crash at 2023-05-01T11:31:12.957Z on CPU 51 running world
2019239 - VSAN_0x450080017780_PLOG. VMK Uptime:0:09:54:11.108
Panic Message: @BlueScreen: Failed at bora/modules/vmkernel/plog/dedup/dedup_util.h:231 -- VMK_ASSERT(blkNum < DDPGetEndBlkNumber(&ddCtx->devices[devIndex].sb, blkType, blkNumCheck, 1))
For more information, see VMware knowledge base article 92458.
|
Name |
ESXi |
|
Version |
ESXi-8.0U1a-21813344 |
|
Release Date |
June 01, 2023 |
|
Category |
Bugfix |
|
Affected Components |
|
|
PRs Fixed |
3217456 |
|
Related CVE numbers |
N/A |
Notatki producenta: VMware ESXi 8.0 Update 1a
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie
