Virtualization Technology News and Information
VMware Releases VMware Studio 2.1

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.

The company has released a new version today, VMware Studio 2.1.  An with it, a number of new improvements, enhancements and security fixes:

VMware Studio improvements:

  • Additional Linux OS support is provided for SLES 11.2, 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 EULA into multiple languages, and vCenter Server will display it in the language of the prevailing locale.
  • 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.

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.

VMware Studio 2.1 fixes the following security issues:

  • VMware Studio 2.0 authenticated remote command execution. The Common Vulnerabilities and Exposures project ( 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 ( 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.

You can download VMware Studio 2.1 here.

Published Tuesday, July 13, 2010 5:28 AM by David Marshall
Filed under:
There are no comments for this post.
To post a comment, you must be a registered user. Registration is free and easy! Sign up now!
<July 2010>