VMware Studio 2.6 Release Notes

Release date: 8 March 2012 | Build 631426
Last document update: 28 Feb 2012
Check frequently for additions and updates to these release notes.


VMware Studio is an integrated development tool that packages existing software applications into virtual machines and vApps that are ready to run and optimized for VMware platform products. VMware Studio can build Linux-based virtual machines, Windows-based virtual machines, and vApps running single-tier or multitier applications.

For developer and user manuals, see the VMware Studio documentation landing page.

New in This Release

VMware Studio 2.6 offers new features including:
  • Support for builds on vCenter Server 5.0 and ESXi 5.0, with faster Windows builds.
  • Built-in profiles for vFabric Application Director, with a choice of RHEL, CentOS, SLES, and Ubuntu.
  • Thumbnail: when you build a virtual appliance on vSphere using the browser-based UI, a small image of the provisioning console appears in the dialog box. You can click on the thumbnail to enlarge it and watch the VM build.
  • A VM generated by VMware Studio 2.6 now installs the official release of VMware Tools presented by the virtualization platform at deployment time, so users can upgrade VMware Tools if they wish. The vSphere Client reports VMware Tools as “Running (Current)” rather than 3rd-party/independent.
  • If a Studio 2.6 generated VM powers on without networking, you can no longer set networking parameters without authentication from the blue-gray Console screen. Instead, you must log in and run the following command:
  • For improved security, updated versions of internal components sfcb, openssl, and lighttpd are included.
  • OVF support was improved, permitting specification of multiple deployment options, addition of the OVF password attribute, and creation of an OVF without networking properties.
  • The internal component ovftool was upgraded, and Studio 2.6 supports uploading OVFs to vCloud Director.
  • VAMI components such as the Web console UI now use message catalogs, so Studio-built virtual appliances can be localized, although VMware Studio itself is not localized.


For provisioning, VMware Studio 2.6 requires one of the following virtualization platform products:

  • VMware ESX/ESXi 5.0, 4.1, 4.0, or 3.5 through vCenter Server 5.0, 4.1, or 4.0
  • VMware ESX/ESXi 3.5 through VMware VirtualCenter 2.5
  • VMware ESX/ESXi 5.0, 4.1, 4.0, or 3.5
  • VMware Workstation 7.1, 7.0.1, or 6.5.2
  • VMware Cloud Director 1.0

Supported Platforms

Virtual appliances created by VMware Studio 2.6 can be deployed on the following supported platform products:

  • VMware vCenter Server 5.0, 4.1, and 4.0
  • VMware VirtualCenter 2.5
  • VMware ESXi 5.0
  • VMware ESX/ESXi 4.1, 4.0, and 3.5
  • VMware Workstation 8.0, 7.1, 7.0, and 6.5
  • VMware Player 4.0, 3.1, 3.0, and 2.5
  • VMware Cloud Director 1.0

The VMware Studio 2.6 Web console supports the following Web browsers:

  • Internet Explorer 8
  • Mozilla Firefox 10
  • Google Chrome 16 and 17

Known Issues

This release of VMware Studio has the following known issues:

  • If you want a vApp to deploy using vSphere IP Pools, you must check the option “Prompt for an IP address and retrieve additional parameters from an IP Pool” in both the vApp and all its constituent VMs. You can find this UI option on the Output tab under IP Address Deployment Choices.
  • When you provision a Windows VM on an ESX/ESXi 4.1 host using VMware Studio 2.6, you should first create the iso directory in the provisioning datastore, otherwise the host's mini Web server hangs and the build will fail. To create this directory, SSH to the host, cd to /vmfs/volumes/datastore-name and run the mkdir iso command. This is not necessary for provisioning a Linux VM because Linux ISO images are copied into the VM directory itself. The problem occurs only with ESX/ESXi 4.1 because it cannot copy a file if its pathname does not pre-exist. VMware Studio 2.6 copies ISO images to the provisioning host for faster builds.
  • Installation of VMware Tools during VM provisioning can cause the network to blank out for a noticeable time. This might be caused by time or timezone changes confusing the DHCP lease timeout. A good workaround is to set all ESX/ESXi hosts to the UTC timezone, preventing timezone changes.
  • There is an issue with RHEL 6.1 installer code where it cannot handle DHCP lease expiration during the OS installation process. The workaround is to open the console of the provisioning OS and select Retry (not Cancel) when you are offered the choice. After you request Retry, installation will continue. The thumbnail image of the provisioning console might give you an idea when a Retry is required.
  • In an Ubuntu VM built by Studio 2.6, and in the Studio appliance itself, the VMware Tools installer package is copied into /vmware-tools-distrib but not removed, wasting 320MB of disk space. To remove it manually, run the command below. If packaging an Ubuntu appliance, you can put this line in the post-install script:
    dpkg -r `dpkg -S /vmware-tools-distrib | sed s/://`

Resolved Issues

  • Unlike VMware Studio 2.5, Studio 2.6 can reliably provision using vCenter Server 5.0 and ESXi 5.0 hosts.
  • Using vCloud Director, VMware Studio 2.6 can now build a Windows VM, and build from an existing VM.
  • The Repository Staging Server is now optional. The Update service can be enabled without a pre-existing Web repository and will later accept updates from an update ISO.