ESX Virtualization

VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....

VMware vSphere 8.0 U2b Released

By | Last Updated:

Shares

There is a new patch you'll have to apply to your virtual infrastructure. The patch is quite important as it fixes A LOT, especially the CBT fix that occurred after the U2a.

Don't forget to backup your vCenter server appliance BEFORE jumping the gun for applying the patch.

What's New (ESXi)

  • 100 GiB of trial storage capacity per vSAN core: With vSphere 8.0 Update 2b, as part of the VMware vSphere Foundation offering, you can use up to 100 gibibytes (GiB) of vSAN storage per vSAN host licensed core without applying a vSAN licensing key. For capacity larger than 100 GiB per vSAN core, you can purchase vSAN capacity per tebibyte (TiB) and apply a vSAN key that reflects the total raw storage capacity of the vSAN cluster. For more information on capacity reporting in and licensing vSAN, see Demystifying Capacity Reporting in vSAN and Counting Cores for VMware Cloud Foundation and vSphere Foundation and TiBs for vSAN.

Table of contents

From the Release Notes below:

Resolved Issues

Installation, Upgrade, and Migration Issues

  • Migration of virtual machines with Virtual Trusted Platform Module (vTPM) across vSphere DRS-enabled clusters failsIn the vSphere Client, when you try to migrate VMs with vTPM across DRS-enabled clusters without selecting any hosts, the final step of the wizard fails with an error such as A DRS fault has occurred while retrieving VM placement recommendations: xvmotionPlacement. If you use the PlaceVM API to live relocate a VM with a vTPM from one DRS cluster to another DRS cluster, the operation also fails.This issue is resolved in this release. With the fix, you can safely migrate VMs with vTPM across DRS-enabled clusters.
  • You see significant delay in downloading ESXi patches from the vSphere Update Manager Download Service when using a proxy serverDue to URL accessibility checks, you might see a delay of up to 24 hours in downloading ESXi patches from the Update Manager Download Service when using a proxy server.This issue is partially resolved in this release. The time for downloading ESXi patches from the Update Manager Download Service when using a proxy server is reduced to few hours.
  • The vSphere DRS migration threshold slider does not display correctly in the vSphere ClientOn vCenter Server 8.0 Update 2, when you navigate to vSphere DRS > Edit > Automation > Migration Threshold, the slider appears much shorter than in previous releases. This is a cosmetic issue that does not affect the functionality of the slider.This issue is resolved in this release.

Virtual Machine Management Issues

  • The VPXD service might fail during a consolidation task due to file locked exceptionDuring a consolidation task in a vCenter environment, such as Consolidate virtual machine disk files, multiple processes lock more than one file and in some environments it is possible to see multiple File Locked exceptions. As a result, the VPXD service might fail while fetching the lock details for the affected files.This issue is resolved in this release.
  • You cannot manually set a static MAC address on a virtual machine by using the vSphere ClientIn the vSphere Client, when you right-click on a virtual machine, select Edit Settings > Virtual Hardware > Network adapter > MAC Address and select Manual from the drop-down menu, then enter a MAC Address and click OK, the Reconfigure virtual machine task appears to complete successfully. But when you check the configured MAC address, it is still set to Automatic and the previous MAC Address is unchanged.This issue is resolved in this release.
  • Encrypted virtual machines in a vSphere DRS cluster might power on slowlyPower-on of encrypted VMs in a DRS-enabled cluster might take more than 90 seconds because of the time it takes to synchronize the VM encryption keys to each ESXi host within the cluster.This issue is resolved in this release. The fix removes redundant encryption key synchronizations.
  • You cannot edit the settings of powered on VMs of hardware version 9 or earlierIn the vSphere Client, when you open Edit Settings on a powered on VM of hardware version 9 or earlier, you see a red exclamation mark beside the Virtual Hardware and VM Options tabs and no content in the dialog box. The Edit Settings dialog works for powered off VMs.This issue is resolved in this release. The fix makes sure that the edit settings of VMs of hardware version 9 or earlier display properly in the vSphere Client.
  • In the vSphere Client, you see only 15 objects per page when migrating a VM to a new compute resourceIn the vSphere Client, when you migrate a virtual machine and opt to change only the compute resource, on the Select compute resource page you see up to 15 objects as compared to the default of 35 for inventory lists.This issue is resolved in this release. The fix makes sure you see a list of up to 35 objects on the Select compute resource page.

Storage Issues

  • You see unusually high CPU usage when you open the Storage DRS recommendations page under the vSphere Client datastore viewIn the Monitor tab in the vSphere Client datastore view, when you look at the Storage DRS recommendations, you might see unusually high CPU usage, up to 100%. The issue occurs due to a fault search algorithm in the DRS recommendation service.This issue is resolved in this release.

Server Configuration Issues

  • You see an error for invalid certificate bytes when configuring new identity source for Active Directory over LDAPIf a certificate .pem file contains the Windows-specific line endings \r\n, or CRLF, you might not be able to configure a new identity source for Active Directory over LDAP. The configuration workflow fails with an error Cannot configure identity source due to Invalid certificate bytes.This issue is resolved in this release.

Miscellaneous Issues

  • Virtual machine tasks such as power off and clone take unusually longIn rare cases, when a service account password for the vService Manager expires, running operations on virtual machines such as power on, clone, and delete might take unusually long to complete. You can see the operations in the task list, but you see no progress for more than 10 minutes.This issue is resolved in this release. If you are already facing the issue, log into the vCenter VM and run the command service-control --restart vsm.
  • You see many errors for HTTP failure due to the waitForUpdates method in the vpx service logsCanceling the waitForUpdates() method is part of the normal workflow when the vpx service waits for a task running on the vpxa or hostd service to complete. However, the canceled call results in a failed HTTP request and subsequently in a log message at the info level. In some environments, such messages, which are not requesting any specific action, might significantly load the vpx service logs.This issue is resolved in this release. The fix lowers the log level to verbose in case the fault for the waitForUpdates() method is RequestCanceled to avoid logging of unnecessary messages in the vpx service logs.
  • You cannot edit the vCenter alarm Datastore usage on disk based on available capacityWhen you select the Datastore usage on disk based on available capacity option in the alarm definition wizard from the Configure tab in the vSphere Client, the Edit task displays indefinitely in progress and you cannot make any changes.This issue is resolved in this release.

Networking Issues

  • You see a black screen after activating the VMware Remote Console (VMRC) proxy serviceAfter you activate the VMware Remote Console, you see a black screen with an error such as The webmks ticket has expired. instead of configuration parameters.This issue is resolved in this release.
  • Port ID selections in the Add Port Mirroring Session wizard might not workWhen you create a port mirroring session by using the vSphere Client to mirror vSphere Distributed Switch traffic to ports, uplinks, and remote IP addresses, Port ID selections in the Select sources and Select destinations steps might not work. For example, in the Select sources page, when you select a Port ID check box and filter to select a host, after selecting a host, the selection on the Port ID disappears. As a result, you cannot filter an ESXi host.This issue is resolved in this release.
  • In the vSphere Client, you do not see all ESXi hosts available to add to a vSphere Distributed SwitchIn the vSphere Client, when you associate ESXi hosts in a cluster with a vSphere Distributed Switch, not all hosts in the cluster are visible and available for selection under the Select hosts page of the Add and Manage Hosts wizard. For example, you might see 8 hosts when the total number of available hosts in the cluster is 20 and you cannot scroll down to see the full list. When you click Select All, you see 20 selected hosts but they remain not visible.This issue is resolved in this release.

vCenter Server and vSphere Client Issues

  • Login and vSphere Client sessions might be affected from connectivity issues between VMware Cloud Gateway and VMware CloudWith vSphere 8.0 Update 2b, if you use vSphere 8.0 Update 2 or later, you no longer need to honor the 45-minute window of vSphere Client sessions to maintain connectivity between VMware Cloud Gateway and VMware Cloud. If your vSphere system is of version earlier than vSphere 8.0 Update 2, after upgrading to 8.0 Update 2b, you can log in to the vSphere Client at any time and see no error for loss of connectivity between VMware Cloud Gateway and VMware Cloud.This issue is resolved in this release.
  • In air-gapped environments, you see untranslated or partial messages in Japanese locale in the vSphere Client for vSAN troubleshooting optionsOnly in air-gapped environments, when you navigate in the vSphere Client to vSAN > Skyline Health > Overview > vSAN optimal datastore default policy configuration > Troubleshoot, you might see untranslated or partial messages in the Japanese locale.This issue is resolved in this release.
  • Log in to the vSphere Client intermittently failsIn large environments where the vsphere-ui service handles multiple concurrent tasks and a single task request might exceed 20 MB, the service might run out of memory and fail. As a result, log in to the vSphere Client intermittently fails.This issue is resolved in this release.
  • After upgrading to vCenter 8.0 Update 2, you see many warnings in the vSphere Client that a privilege check failsIn some environments, during the prestart stage of the VMware Service Manager (VSM), a missing privilege for the VsmSvcRole might cause vCenter to issue multiple warnings after an upgrade to version 8.0 Update 2. In the vSphere Client, under Monitor > Events, you might see hundreds of warnings per day.This issue is resolved in this release. The fix makes sure the VsmSvcRole gets all required privileges.
  • You cannot open the vSphere Client Summary tab from a VMware Aria Operations objectWhen you navigate to a VMware Aria Operations object, for example a VM under Environments > vSphere > vSphere Host and Cluster > vSphere World > vCenter Server > Datacenter, and select Open Virtual Machine in vSphere Client from the Actions drop down menu, you see an error. The issue occurs due to accidental encoding of some characters in the navigation segment. As a result, the vSphere Client cannot open the Summary tab of the virtual machine as the current object and you see the error Missing Route This route is not supported:<link to object>.This issue is resolved in this release.

vSAN Issues

  • You cannot remove IP settings in the vSAN File Service Domain wizardIn the vSphere Client, when you open the File Service Domain wizard, the affinity site selection area overlaps the button to remove IP settings and you cannot click the button. The issue affects only vSAN Stretched Cluster environments.This issue is resolved in this release.

Security Issues

  • vCenter Server 8.0 Update 2b provides the following security updates:
    • The Guava suite is updated to version 32.1.0-jre.
    • Apache Tomcat is updated to versions 8.5.95/9.0.82.
    • Eclipse Jetty is updated to version 9.4.53.v20231009.
    • Apache Log4j is updated to version 2.21.1.

More posts from ESX Virtualization:

Stay tuned through RSS, and social media channels (Twitter, FB, YouTube)

Shares
5/5 - (1 vote)

About Vladan SEGET

This website is maintained by Vladan SEGET. Vladan is as an Independent consultant, professional blogger, vExpert x16, Veeam Vanguard x9, VCAP-DCA/DCD, ESX Virtualization site has started as a simple bookmarking site, but quickly found a large following of readers and subscribers.

Connect on: Facebook. Feel free to network via Twitter @vladan.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

x