VMware Studio 2.5 Release Notes

Release date: 14 April 2011 | Build 387333
Last document update: 07 April 2011
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.

The release notes cover the following topics:

What's New in This Release

VMware Studio includes the following enhancements:

  • Support for vCloud Director 1.0
    • Studio now supports vCloud Director 1.0 to build your virtual machines and vApps.
    • An OVF built with Studio can be deployed both on vSphere and vCloud Director 1.0.
  • Studio Interchange Format Package (SIF)
    The new SIF package in Studio allows you to share your build appliance artifacts with another user. You can export and import SIF files using the studiocli for building appliances. When creating a SIF package, you can choose to include or exclude specific item types, for example, OS ISO. This is useful for distributing appliance artifacts for Windows appliances without having to include a Windows ISO.
  • OVF Properties
    • You can now transport the OVF properties to the guest using a CD-ROM. This is particularly useful if you do not want to install VMware Tools in the appliance.
    • A new ovfenv tool is available for Linux built appliances to read the OVF properties from the guestInfo (added by VMware Tools) or the CD-ROM. This ovfenv tool can also be used to remove any sensitive data in the application like passwords, after the data is consumed.
  • Utilities to Reduce the Size of an Appliance
    VMware Studio includes two new command-line utilities to reduce the size of an appliance:
    • jeoser processes an operating system ISO and application packages and outputs the required subset of files from the operating system ISO to run the application.
    • makejeosvm creates a virtual machine using these files and application packages. This process reduces the size of an appliance by an order of magnitude. For instance, using these two new command-line utilities, you can reduce the size of an appliance from 600Mb to approximately 50Mb.

    • Note: This feature is currently included as an experimental feature to receive feedback from the Studio community. All conditions are listed in the EULA and http://www.vmware.com/support/policies/experimental.html
  • Ability to Extend Appliances Disk Size
    Studio now allows you to define a disk that can be grown. You can configure a non-system disk so that it is LVM-enabled. You can then add more disks to the logical volume group to increase the disk size.
  • Studio Updates
    You can now retrieve updates from a Studio update repository available on VMware Website or distributed through a downloadable ISO.
  • On-demand Application Repositories
    You can now select packages from application repositories. If a package from any repository depends on a package present in the on-demand repository, then Studio installs those dependent packages into the appliance. Note that these packages are installed only if the application packages need them.
  • PVSCSI Support
    PVSCSI adapters are high-performance storage adapters that results in greater throughput and lower CPU utilization. Studio now allows you to create disks using PVSCSI controller.
  • VMXNET and VMXNET3 Support
    You can now include virtual network adapters such as VMXNET and VMXNET3 in the build profile for building appliances with optimal network performance.
  • 64-bit VAMI Packages
    Studio now supports 64-bit VAMI packages to run on 64-bit operating systems.
  • Longer Build Instance Name
    The build instance name was earlier restricted to 11 characters. That restriction is now removed.
  • Automatic ISO Files for Appliances
    You can now attach ISO images to CD-ROM drives when the drives are selected in the user interface. These ISOs are not related to the operating system ISO images that you use to install the operating system.
  • Scalability
    You can build 10 appliances concurrently from the user interface and command line interface.
  • Troubleshooting
    Studio now supports an additional flag --keeponerror to retain virtual machines of the failed builds on the provisioning engine. This helps you to debug any problems with the build.

Networking Enhancements

  • Support for IPv6 Protocol
    You can configure IPv6 addresses (DHCP, Static, or Automatic) for the appliances created using Studio 2.5.
  • Choice of IPv6/IPv4
    A choice to configure appliances with IPv4 only or IPv6 and IPv4 address format.
  • Multiple Network Interface Cards
    Ability to manage multiple network interface cards in the appliance using the appliance Web Console or appliance command line interface.
  • Choice of IP Pools
    You can now choose to deploy virtual appliances on vCenter Server without IP pools. If IP pools are disabled, the OVF deployment wizard prompts you to specify the necessary networking properties (IP addresses, DNS, and Gateway) during deployment.

Security Enhancement

  • Only users who are members of VAMI group can access the generated appliance. By default, only root users are added to the VAMI group.

Support for Additional Guest Operating Systems

VMware Studio can now build virtual appliances using the following additional guest operating systems:

  • CentOS 5.5 (32-bit and 64-bit)
  • RHEL 5.5 (32-bit and 64-bit)
  • RHEL 6 (32-bit and 64-bit)
  • SLES 10.2 (32-bit and 64-bit)
  • SLES 11 SP1 (32-bit and 64-bit)
  • Ubuntu 10.04 (32-bit and 64-bit)
  • Windows Server 2003 R2 (32-bit and 64-bit)
  • Windows Server 2008 R2 (64-bit)


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

  • VMware ESX/ESXi 4.1, 4.0, or 3.5 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 Cloud Director 1.0
  • VMware Server 2.0 (deprecated)

Supported Platforms

Virtual appliances created by VMware Studio can be deployed on the following 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 Cloud Director 1.0
  • VMware Server 2.0 (deprecated)

Supported Web Browsers

The VMware Studio Web console supports the following Web browsers:

  • Internet Explorer 7 or 8
  • Mozilla Firefox 3.0, 3.5, or 3.6
  • Google Chrome 8.0 or 9.0

Known Issues

This release of VMware Studio has the following known issues:

  • Existing virtual machine import fails if the required user-configurable property exists
    If a virtual machine containing an integer OVF property is imported and a transient virtual machine name is specified during the import process, Studio fails to import the virtual machine and displays the following error message:
    FaultString: Property {propertyname} is not configured.
    Workaround: Do not specify the transient virtual machine name.
  • vCloud Director retains vApp templates of a cancelled build
    While building an appliance using the vCloud Director if you cancel the build during the process, sometimes the vApp instance of the cancelled build is retained in the vCloud Director.
    Workaround: Studio recommends you to view the status of the vApp and manually delete the vApp template from the vCloud Director.
  • An error message is displayed during network configuration
    While configuring a network interface by using the command-line interface, sometimes the following error message is displayed:
    [ERROR] Attempted translation of an Invalid IPv6 address
    You can ignore these messages.
  • RHEL 6.0 operating system installation becomes unresponsive due to the DHCP timeout bug
    RHEL 6.0 operating system installation freezes while waiting for retry confirmation. This is due to an expired DHCP address.
    Workaround: In the pop-up dialog box select Retry or alternatively, provide a static IP address for provisioning the virtual machine to bypass the DHCP dependency.
  • Studio user interface intermittently displays the list of virtual machines in a small scrolling frame
    Studio user interface intermittently displays the list of virtual machines in a small frame instead of a normal display size.
    Workaround: Click the VMs tab after clicking any other tab in the user interface. Studio will display the frame in a normal view.
  • The file system size specified for LVM does not match with the file system size provided in the build profile
    This occurs because the disk size is typically rounded to the full physical extent by the operating system. Therefore, the size of the file system specified in the build profile for LVM does not precisely match with what is produced.
  • Temporary files are retained in the appliance in the /tmp folder
    A few temporary files are retained in the appliance under the /tmp folder. These files are harmless. If required, you can delete these files as part of a post-install script.
  • Ensure that you provide the engine name in lower case when importing a virtual machine with the CLI
    With the studiocli command's -I option, after selecting vi for remote import, you must specify the engine name in lower case, for example "esx" instead of "ESX" for provisioning.

Resolved Issues

The following is a list of issues resolved in VMware Studio

  • Unable to download latest updates, security fixes, and patches if update repository URL redirects to another URL
    The earlier version of Studio could not download the latest updates, security fixes and patches when a URL given for the update repository redirects to another URL. This issue is resolved.
  • Studio configures incorrect network addresses for SLES builds
    When you import an SLES virtual machine and create a new build using the resulting build profile, Studio configures incorrect networking properties in the generated appliance. To prevent Studio from configuring incorrect networking properties, you can remove the /etc/udev/rules.d/70-persistent-net.rules file at the end of the SLES builds.
  • When you build a profile in the Studio, vadk: provisioning timeout parameters are ignored
    The vadk: provisioning time out section in the build profile allows you to set various timeout values that the build uses, such as the time Studio waits before giving up to determine the network address from the virtual machine, the time before giving up the wait for an operating system to install, and so on. These values were ignored and only the defaults were included in the build scripts. This issue is resolved in this release.
  • Networking parameters revert to their deploy-time settings after a reboot
    When you deploy a virtual machine under vCenter Server, you are given a choice for network configuration (DHCP, Fixed, or Transient) and may also assign an IP address to the virtual machine. After the virtual machine is running, VAMI allows for network reconfiguration of the virtual machine. However, vCenter Server does not know if the network was reconfigured. So, there is a flag in the virtual machine that tells the VAMI code run at boot time that the network has been reconfigured in the virtual machine and to ignore the network parameters from vCenter Server.
    This works fine if you use user interface to reconfigure the network. However, the blue screen network configuration does not set this flag, so the next time the virtual machine is booted, the network parameters are reset to the state when the virtual machine was first deployed. This issue is resolved in this release.
  • Builds could fail if proxy in the Web console is not set
    When you set the HTTP proxy and later reset it by deselecting Use a Proxy Server in the Studio Web console, subsequent builds either fail or become unresponsive. This issue is resolved in this release. You can now remove the http_proxy key from the Studio appliance's /etc/environment file.
  • Build profile displays incorrect disk size after importing a virtual machine
    After a virtual machine import, the build profile displays an incorrect disk size, and as a result, the virtual machine built from the build profile is deployed incorrectly. This occurs because the vCenter and ESX indicates that the disk size is too small. This issue is resolved in this release.
  • Studio Web console displays incorrect OVF URL
    When a virtual machine is imported, sometimes the OVF URL is displayed incorrectly in the Web console. This issue is resolved in this release. The URL is now set to correct path in the status file.
  • A misleading debug message, Creating update ISO/ZIP, appears in the build profile log
    When you create a virtual machine without an update service, the following debug messages are added to the log.
    [info] Build Export: /opt/vmware/www/build/c53.3/exports
    [dbug] VA Packaging Duration: 00:00:57
    [dbug] Creating update ISO/ZIP using signing script:
    These debug messages are now removed from the log.