check-circle-line exclamation-circle-line close-line

VMware vCenter Server 6.7.0b Release Notes

vCenter Server 6.7.0b | JUN 28 2018 | ISO Build 8832884

vCenter Server Appliance 6.7.0b | JUN 28 2018 | Build 8832884

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

vCenter Server 6.7.0b addresses issues that have been documented in the Resolved Issues and Known Issues sections, and the Photon OS security vulnerabilities. For more information, see VMware vCenter Server Appliance Photon OS Security Patches

Earlier Releases of vCenter Server 6.7

Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 6.7 are:

For internationalization, compatibility, installation and upgrades, open source components and product support notices see the VMware vSphere 6.7 Release Notes.

Patches Contained in This Release

vCenter Server 6.7.0b delivers the following patches. See the VMware Patch Download Center for more information on downloading patches.

Full Patch for VMware vCenter Server Appliance 6.7.0b

Product Patch for vCenter Server Appliance 6.7 containing VMware software fixes.

This patch is applicable to the vCenter Server Appliance and Platform Services Controller Appliance.

For vCenter Server and Platform Services Controller Appliances

Download Filename VMware-vCenter-Server-Appliance-6.7.0.12000-8832884-patch-FP.iso
Build 8832884
Download Size 2094.8 MB
md5sum 53f67000b6265e28cc39f686c223e7ca
sha1checksum 2483c2e638e55667a66dc268fbb41ab429c31463

Download and Installation

You can download this patch by going to the VMware Patch Download Center and choosing VC from the Search by Product drop-down menu.

  1. Attach the VMware-vCenter-Server-Appliance-6.7.0.12000-8832884-patch-FP.iso file to vCenter Server Appliance CD or DVD drive.
  2. Log in to the appliance shell as root and run the commands given below:
    1. To stage the ISO:
      software-packages stage --iso
    2. To see the staged content:
      software-packages list --staged
    3. To install the staged rpms:
      software-packages install --staged

For more information on patching the vCenter Server Appliance, see Patching the vCenter Server Appliance.

For more information on staging patches, see Stage Patches to vCenter Server Appliance.

For more information on installing patches, see Install vCenter Server Appliance Patches.

For issues resolved in this patch, see Resolved Issues.

For more information on patching using the Appliance Management Interface, see Patching the vCenter Server Appliance by Using the Appliance Management Interface.

Upgrade Notes for This Release

Important: Upgrade and migration paths from vCenter Server 6.5 Update 2 and above to vCenter Server 6.7 are not supported.

Resolved Issues

The resolved issues are grouped as follows.

Security Issues
  • This updated version of vCenter Server provides part of the hypervisor-assisted guest mitigation of CVE-2018-3639 for guest operating systems. For important details on this mitigation, see VMware Security Advisory VMSA-2018-0012.1.

Known Issues

The known issues are grouped as follows.

Miscellaneous Issues
  • If you enable per-VM Enhanced vMotion Compatibility (EVC), the virtual machine might fail to power on

    If you enable cluster-level EVC and even one of the hosts in the cluster is not patched with the hypervisor-assisted guest mitigation for guest operating systems, the new CPU IDs of that cluster might not be available on the cluster. In such a cluster, if you configure or reconfigure per-VM EVC, virtual machines might fail to power on.

    Workaround: Before you configure or reconfigure per-VM EVC, upgrade all the standalone ESXi hosts, as well as hosts inside a cluster, to the latest patches for hypervisor-assisted guest mitigation for guest operating systems.

  • If you disable per-VM EVC, migration of virtual machines by using VMware vSphere vMotion might fail

    If you enable cluster-level EVC and even one of the hosts in the cluster is not patched with the hypervisor-assisted guest mitigation for guest operating systems, the new CPU IDs of that cluster might not be available on the cluster. In such a cluster, if you disable per-VM EVC, migration by using vSphere vMotion might fail for virtual machines running on a non-patched host to a patched host.

    Workaround: Upgrade all hosts in the EVC cluster to the latest patch for hypervisor-assisted guest mitigation for guest operating systems. Disable per-VM EVC. 

  • Inconsistent patching of vCenter Server and ESXi might lead to issues with per-VM EVC

    If you patch a vCenter Server system with the hypervisor-assisted guest mitigation for guest operating systems and not all ESXi hosts have the upgrade too, a newly configured or reconfigured per-VM EVC might incorrectly power-on a virtual machine on an unpatched host. In such a case, the virtual machine might be missing some features added to a patched host. Due to compatibility checks, such virtual machines can not be migrated to patched hosts in the same EVC cluster by using vSphere vMotion. If the source and destination hosts are not in the same EVC cluster, they might have different feature sets and migration might be possible.

    Workaround: Before you configure or reconfigure per-VM EVC, upgrade all the standalone ESXi hosts, as well as hosts inside a cluster, to the latest patches for hypervisor-assisted guest mitigation for guest operating systems.

Known Issues from Earlier Releases

To view a list of previous known issues, click here.