VMware Studio 2.0 Release Notes

General Availability Release | 31 August 2009 | Build 1017

Last document update: 16 September 2009

Check frequently for additions and updates to these release notes.



VMware Studio is an integrated development tool that takes existing software applications and packages them into virtual machines and vApps that are ready to run and optimized for VMware product platforms. VMware Studio can build Linux‐based VMs, Windows‐based VMs, and vApps, running single tier or multitier applications.

New Features in VMware Studio 2.0

The following features were added between VMware Studio 1.0 and 2.0:

  • Ability to create multiple-VM appliances, or vApps, to run on VMware vSphere.
  • More provisioning engines including ESX/ESXi 3.5 and 4, VMware Workstation 6.5.1, and VMware Server 2.0.
  • Build support for Windows Server 2003 and 2008 (32-bit and 64-bit) virtual appliances.
  • Build support for 64-bit Red Hat Enterprise Linux (RHEL) and SUSE Enterprise Linux Server (SLES).
  • Build support new Linux distributions RHEL 5.3, CentOS 5.3, and Ubuntu 8.04.1.
  • Extensible management services allow you to customize an interface into a new tab.
  • An Eclipse plug-in helps you package applications and create management services.
  • Automatic dependency resolution for application packages installed on Linux-based virtual appliances.
  • Existing VM build (input-as-VM) for Linux virtual appliances.
  • DMTF standard OVF 1.0 and open virtual appliance (OVA) packaging. VMware Studio 1.0 supported OVF 0.9.

You can read about release 1.0 in the VMware Studio 1.0 Release Notes and other VMware Studio documentation.

The following features were added since VMware Studio 2.0 Beta:

  • Eclipse usability improvements.
  • Update existing appliances from CDROM.
  • Web console footer customization in the appliance VM.
  • EULA first-boot display control in the appliance VM.
  • Host name editing in the Web console of the appliance VM.
  • Security fix for VMware Studio when uploading management services. See CVE-2009-2968.

VMware Studio 2.0 Beta build profiles are not fully compatible with the 2.0 GA software. VMware recommends that you use the Web console to re-create the beta build profiles from scratch based on the VMware Studio 2.0 GA template profiles.


For provisioning, VMware Studio 2.0 requires one of these virtualization product platforms:

  • VMware ESX/ESXi 4.0 and 3.5 U3 through VMware vCenter Server 4
  • VMware ESX/ESXi 3.5 U3 through VMware VirtualCenter 2.5 U3
  • VMware ESX/ESXi 4.0
  • VMware ESX/ESXi 3.5 U3
  • VMware Workstation 6.5.1
  • VMware Server 2.0
  • VMware Server 1.0.4, 1.0.5, and 1.0.6

Virtual appliances created by VMware Studio can run on these supported product platforms:

  • VMware vCenter Server 4
  • VMware VirtualCenter 2.5 U3
  • VMware ESX/ESXi 4.0
  • VMware ESX/ESXi 3.5 U3
  • VMware Workstation 6.5.1
  • VMware Server 2.0
  • VMware Server 1.04, 1.05, and 1.06
  • VMware Player 2.04 and 2.5

The VMware Studio 2.0 Web console supports these browsers:

  • Internet Explorer 6.0 or 7.0
  • Mozilla Firefox 2.0.14, 2.0.16, or 3.0.6

Known Issues

This release of VMware Studio has the following known issues:

  • Provisioning on an ESX/ESXi host managed by an active VirtualCenter or vCenter Server is not recommended. The VMware Studio build process could fail and ESX/ESXi Web services might also give errors because of concurrent reconfiguration from vCenter or VirtualCenter. When an ESX/ESXi host is managed, always select vCenter or VirtualCenter as the provisioning platform.
  • When you deploy an OVF 0.9 or 1.0 virtual machine onto an ESX/ESXi host or through VirtualCenter or vCenter Server, the VMware Tools time synchronization facility remains disabled after import. See Knowledge Base article 1014038 for solutions.
  • A Linux VM created by VMware Studio in OVF format, when imported into Workstation 6.5 with the Workstation Conversion Wizard, might fail to boot due to a kernel panic error. This is a known issue in the VMware Converter version that the Conversion Wizard runs. For a solution, see the VMware Studio Developer's Guide to Building vApps and Virtual Appliances, Troubleshooting appendix, problem with Buslogic SCSI adapter.
  • The SVGA and mouse drivers provided in the VMware-open-vm-tools package conflict with the versions provided by RedHat, CentOS, and SUSE. This is a known issue with VMware Tools, documented in the OSP manual, VMware Tools Installation Guide Operating System Specific Packages. The issue could affect VMware Studio's ability to build a VM with X server, or to manage updates when a conflict occurs.
  • Recent VMware product platforms warn about out-of-date VMware Tools in Studio-created Ubuntu 7.04 and 7.10 VMs, because OSP downloads are not available for those old Ubuntu releases. Although it is neither required nor recommended, users can manually uninstall the vmware-tools*.deb package using the dpkg command, and run Install VMware Tools on their virtualization platform to upgrade VMware Tools. However, note that manual changes to software packages in the VM will thwart the appliance update process by VMware Studio.
  • Firefox has memory leaks exacerbated by long-running VMware Studio sessions, especially when displaying the VM list. One workaround is upgrading to Firefox 3.