If you are using HotAdd to backup VMDK disks which are larger then 2TB while running vSphere 5.5 be warned that this will fail silently as described in KB2068424.

  • When using the HotAdd transport mode, you are unable to back up disks that are 2 TB or larger in size.
  • Backing up disks larger than 2TB in HotAdd transport mode fail silently, but report a successful back up on Windows virtual machines.

VMware currently has no workaround for this! If you are using Veeam make sure you check out the solution provided by Luca.

VMware announced some updates for several products:

VMware ESXi 5.0 Update 2

What’s New

Not much new here. Mostly support for additional guest operating systems and some resolved issues.

For more information read the release notes.

VMware vCenter Server 5.0 Update 2

What’s New

This release offers the following improvements besides the resolved issues:

  • vCenter Server is now supported on Windows Server 2012
  • Additional Guest Operating System Customization Support
  • vCenter Essentials no longer enforces vRAM usage limit of 192 GB

For more information read the release notes.

VMware vCenter Server 5.1.0b

What’s New:

This release offers the following improvements besides the resolved issues:

  • Timeout errors occurring when logging in to the vSphere Client have been addressed.
  • You can log in to a vSphere Web Client as a user of an Active Directory domain that has a non-standard UPN.

For more information read the release notes.

VMware vCenter Site Recovery Manager 5.0.2

What’s New

This release offers the following improvements besides the resolved issues:

  • Added support for protection and IP customization for some new guest operating systems.
  • The vSphere Replication management server accepts MD5 certificates. See Caveats and Limitations.
  • Upgraded OpenSSL 0.9.8m to 0.9.8t for improved security. This addresses the security advisory that was issued for OpenSSL in January 2012.
  • Auto-generated certificates use RSA keys of 2048 bits.

For more information read the release notes.

VMware vCenter Site Recovery Manager 5.1

What’s New

This release offers the following improvements besides the resolved issues:

  • SRM 5.1 supports reprotect and failback with vSphere Replication. Previously, you could only perform reprotect and failback on array-based protection groups. In SRM 5.1 you can perform reprotect and failback on vSphere Replication protection groups.
  • The SRM Server in SRM 5.1 is now a fully 64-bit application.
  • Improved handling of datastores in the all paths down (APD) state. If SRM detects that a datastore on the protected site is in the all paths down (APD) state and is preventing a virtual machine from shutting down, SRM waits for a period before attempting to shut down the virtual machine again. The APD state is usually transient, so by waiting for a datastore in the APD state to come back online, SRM can gracefully shut down the protected virtual machines on that datastore.
  • Improved disk resignaturing for VFMS disks.

For more information read the release notes.

VMware vCloud Connector 2.0

New Features:

  • Datacenter Extension
  • Content Sync
  • Cross-cloud Search
  • Multi-tenant Node
  • Copy and deploy in one operation
  • New User Interface

For more information read the release notes.

Have fun upgrading!

When VMware release ESXi 5.0 Update 1 the auto start manager broke which was first discovered and discussed on the communities and later on in an official blog post. VMware now released a new patch which resolves this issue. The new patch also fixes some other bugs and security issues.

Installing the patch does require a reboot of the host before it works again. If you have ESXi 5.0 Update 1 installed I suggest you update as soon as possible and benefit from autostart.

Today VMware released minor updates for VMware Workstation (bringing the version to 8.0.4) and VMware Fusion (bringing the version to 4.1.3). These contains a few bug and security fixes. They are available now and are free as usual.

VMware Workstation

General Issues

  • Linux guests running the Linux kernel version 2.6.34 or later could not be pinged from the host via an IPv6 address.
  • On rare occasions, Linux guests would suddenly fail to Autofit or enter Unity.
  • Unity mode would exit if the title bar of an application contained certain non UTF-8 encoded extended ASCII characters.
  • On Windows hosts, the VMware Workstation user interface sometimes became unresponsive when minimized from full-screen mode if the suggestion balloon was being displayed.
  • On Windows hosts, the user interface sometimes became unresponsive if the application was rendered on an extended display that was abruptly disconnected.

Security Issues

  • VMware host Checkpoint file memory corruption
    Input data was not properly validated when loading Checkpoint files. This issue could have allowed an attacker with the ability to load a specially crafted Checkpoint file to execute arbitrary code on the host.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3288 to this issue.
  • VMware virtual machine remote device denial of service
    A device (such as CD-ROM or keyboard) that is available to a virtual machine while physically connected to a system that does not run the virtual machine is referred to as a remote device. Traffic coming from remote virtual devices was incorrectly handled. This issue could have allowed an attacker who was capable of manipulating the traffic from a remote virtual device to crash the virtual machine.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3289 to this issue.

More information can be found in the release notes.

VMware Fusion

General Issues

  • Resolved an intermittent issue with an unreleased version of Mac OS X.
  • Fixed a race-condition when starting VMware Tools in some OpenSUSE virtual machines.

Security Issues

  • VMware host Checkpoint file memory corruption
    Input data was not properly validated when loading Checkpoint files. This issue could have allowed an attacker with the ability to load a specially crafted Checkpoint file to execute arbitrary code on the host.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3288 to this issue.
  • VMware floppy device out-of-bounds memory write.
    Due to a flaw in the virtual floppy configuration, it was possible to perform an out-of-bounds memory write. This vulnerability could have allowed a guest user to crash the VMX process or to potentially execute code on the host.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-2449 to this issue.

More information can be found in the release notes.

VMware released the final version on their “vSphere 5.0 Hardening Guide”.

This latest version represents a significant step in the evolution of the guide. Based on feedback from customers and partners, the guide was re-structured from the ground up with the following key aspects:

  • The guide is being released exclusively in spreadsheet format. Many of you have indicated that, although the accompanying text found in previous versions of the guide is interesting, the specific steps for assessment and remediation of the recommendations are really what matters. Since people often end up putting the guide into spreadsheet format anyway, we figure we’d save you the trouble!
  • All guidelines have the same set of metadata, and a new standardized and extensible identification scheme. This will enable customers to more readily adapt the guide to suit their particular environment by selecting the specific guidelines and fields that are of interest to them, and also help them in the generation of standard checklists and similar documents.
  • A primary goal for this guide was to enable greater automatability. To this end, the guide includes both assessment and remediation commands for the three main vSphere CLIs: vSphere CLI (vCLI), ESXi Shell, and PowerCLI. References have also been added to sections of the vSphere API documentation that relate to each specific guideline.
  • The previous recommendation levels have been replaced by a system using Profiles. This is part of the move towards putting the guide into industry-standard format, a potential benefit that will be fully realized in the future.

The document is available on the VMware Communities.