VMware Studio 2.1 Release Notes

Release date: 13 July 2010 | Build 1318-268792
Last document update: 9 July 2010
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 platform products. VMware Studio can build Linux-based VMs, Windows-based VMs, and vApps running single tier or multitier applications.

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

New Features in VMware Studio 2.1

VMware Studio improvements:

  • Additional Linux OS support is provided for SLES 11, CentOS 5.4, RHEL 5.4, and Ubuntu 8.04.3 and 8.04.4.
  • Unlike previous versions, VMware Studio 2.1 can create virtual appliances from virtual machines that were not originally created with VMware Studio, based on a discovery phase.
  • The CLI offers the --newos option so you generate a build profile for any RPM-based or DEB-based Linux OS.
  • You can run concurrent builds with Studio 2.1. After a configurable limit is reached, builds wait in a queue.
  • The generated virtual machine always reboots before your application installs. Some applications expect a full installed working system before they themselves will install. Rebooting after OS installation provides the real environment in which to install, instead of an artificial post-installation environment.
  • You can now specify the order of application package repository installation.
  • VMware Studio 2.1 optionally analyzes the list of RPM and DEB packages to locate unused items and generate a small-footprint virtual machine. It can also reduce the footprint post-installation with a file removal list.
  • VMware Studio 2.1 can generate a discovery report showing contents of a virtual appliance.
  • You can now import vApp profiles.
  • You can translate your EULAs into multiple languages, so the vSphere Client and the VM first-boot script will display it in the language of the prevailing locale.
  • Your EULAs can be placed into files, rather than embedded into the build profiles.
  • You can digitally sign an OVF file, so VMware vSphere 4.1 can verify the signed certificate during OVF import.
  • VMware vSphere 4.1 also supports OVF with thin provisioned disk, and the vmw:Config option.
  • You can associate network labels with specific NIC cards by modifying the XML profile.
  • The vamisupport utility is placed into output appliances to retrieve useful data for troubleshooting VAMI related issues.

Updates to virtual appliances have been enhanced:

  • You can generate signed manifests so customers can ensure that patches are coming from a trusted source.
  • Polling for available updates was optimized.
  • The appliance manifest now carries change log information, which can contain information on whether an update is critical or required. You can force reboot of the appliance after an update.
  • You can add your EULA, in any one language, to an update.
  • Extended configuration parameters can be passed through to the manifest.
  • The virtual appliance administrator can create a tarball of log files to help support personnel diagnose failed updates and other problems.

Requirements and Support

For provisioning, VMware Studio 2.1 requires one of these virtualization platform products:

  • VMware ESX/ESXi 4.1 or 4.0 through VMware vCenter Server 4.1 or 4
  • VMware ESX/ESXi 3.5 through VMware VirtualCenter 2.5
  • VMware ESX/ESXi 4.1 or 4.0
  • VMware ESX/ESXi 3.5
  • VMware Workstation 6.5.2, 7.0.1, and 7.1
  • VMware Server 2.0 (deprecated)
  • VMware Server 1.0.4, 1.0.5, and 1.0.6 (deprecated)

The VMware Studio 2.1 Web console supports these browsers:

  • Internet Explorer 7 or 8
  • Mozilla Firefox 3.0, 3.5, or 3.6

Virtual appliances created by VMware Studio can run on these supported platform products:

  • VMware vCenter Server 4.0 and 4.1
  • VMware VirtualCenter 2.5
  • VMware ESX/ESXi 4.0 and 4.1
  • VMware ESX/ESXi 3.5
  • VMware Workstation 6.5, 7.0, and 7.1
  • VMware Player 2.5, 3.0, and 3.1
  • VMware Server 2.0 (deprecated)
  • VMware Server 1.04, 1.05, and 1.06 (deprecated)

Security Issues

VMware Studio 2.1 fixes the following security issues:

  • VMware Studio 2.0 authenticated remote command execution. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2667 to this issue. This issue can affect virtual appliances that were generated by VMware Studio 2.0.
  • VMware Studio 2.0 local privilege escalation. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2427 to this issue.

To remediate CVE-2010-2667, VMware recommends that developers use Studio 2.1 to rebuild any virtual appliances that contain VAMI services. For more details on these vulnerabilities, see the corresponding VMware security advisory, VMSA-2010-0011.

Known Issues

This release of VMware Studio has the following known issues:

  • Builds could hang or fail after unsetting proxy in Web console. If you set the HTTP proxy and later unset it by unchecking Use a Proxy Server in the Studio Web console, subsequent builds could hang or error-out. The workaround is to remove the http_proxy key from the Studio appliance's /etc/environment file.
  • When importing a VM with the CLI, the engine name is case sensitive. With the studiocli command's -I option, after choosing "vi" for remote import, you must specify the engine name in lower case, for example "esx" instead of "ESX" for provisioning.
  • After VM import the status file contains a buildable local path, but clicking it yields a 404 error. After importing, the status file in the constructed instance directory contains the path to the downloaded VM. However, the path should be a URL, and the UI does not interpret it correctly.
    No workaround is necessary. The builds work properly, only the UI has difficulty.
  • A password is required for ESXi provisioning, but it should not be required. ESXi ships without a password by default. Studio 2.0 allowed you to provision with a password-less ESXi; Studio 2.1 does not.
    Workaround: Set a password for ESXi.
  • Giving incorrect arguments to studiocli might show queued jobs in the UI. If studiocli is given incorrect arguments or options, the UI may show that a build is queued forever.
    Workaround: You can cancel the build using the UI or with the studiocli command.
  • Builds might time out using Workstation 7.1. If Workstation 7.1 is not started, the vmrun command that Studio uses will still bring up the UI, but invoked with ssh, the vmrun command does not return right away (as it does normally), so the Studio build times out.
    Workaround: Start Workstation first, before using it to provision.
  • The updatecli.log contains preload messages during SLES upgrade. During a SLES upgrade, updatecli.log shows many ignored ld.so errors, although the upgrade succeeds and the packages seem to have been correctly installed. Here is a sample of the error:
    ERROR: ld.so: object '/lib/libpam_misc.so.0' from LD_PRELOAD cannot be preloaded: ignored.
    These messages are benign, you can safely ignore them.
  • The VMware Studio IP address appears in appliance's boot config file. A SLES 11 appliance created by Studio contains a reference to the Studio VM's IP address in its boot menu.
    Workaround: The IP address can be removed from the /boot/grub/menu.lst file.
  • Misleading debug message "Creating update ISO/ZIP" that doesn't happen. The following messages may appear in the debug.log for a build without an update service.
    30/04/2010 10:20:14 [dbug] Creating update ISO/ZIP using signing script:
    30/04/2010 10:20:14 [dbug] Merging update repository using signing script:

    These messages are benign, you can safely ignore them.
  • VMware Studio 2.1 does not configure network cards other than eth0. The in-guest scripts that ship with Studio do not support the configuration of multiple Network Interface Cards (NICs).
    Workaround: To allow other or multiple network cards, you can configure cards other than the one associated with eth0 yourself.
  • Existing VM import does not preserve an existing appliance's configuration. When the Existing VM feature is used with an existing, configured virtual appliance as its base, existing scripts and services from the base appliance may be overwritten with data from the new appliance.
    Workaround: This might be what you want, because the new VM overrides the base VM's configuration. If this is not what you want, ensure that the base VM does not contain data that must be preserved. The configurations that can be overwritten include the base VM's existing first boot script, subsequent boot script, EULAs, management services, and so on.
  • Existing VM build does not prevent concurrent sourcing of same deployed VM. Two concurrent Existing VM builds must not point to the same deployed VM that is already present on a virtualization engine such as ESX or vCenter Server. This could cause the first build to fail after the second build powers off the transient VM.
    Workaround: Do not point two concurrent Existing VM builds at the same deployed VM.
  • If a build profile contains certain hand-created disk and partition sizes, the UI might fail to validate the partition size. A possible cause is the loss of precision in translating megabytes and gigabytes into cylinder sizes.
    Workaround: Use the UI to create the disk and partition sizes.
  • The postinstall.log contains messages warning about authentication.
    WARNING: The following packages cannot be authenticated!
    These messages are benign, you can safely ignore them.
  • The postinstall.log contains messages warning of conflicting distributions.
    W: Conflicting distribution: http://a.b.c.d stable Release (expected stable but got hardy).
    These messages are benign, you can safely ignore them.