VMware

 

VMware Virtual Infrastructure SDK 1.4 Release Notes


This page contains the Virtual Infrastructure SDK release notes for VMware VirtualCenter 1.4. This release features VMware Server compatibility, enhanced hardware support, and corrections to the SDK reference manual. For SDK 1.3 release notes, click here.



New Features Since the Previous Virtual Infrastructure SDK (VirtualCenter 1.3.1) Release

  1. SDK Support for 64-bit Hosts

    The SDK has now added support for 64-bit hosts. A host with 64-bit support appends new status information to the SystemInfo.name property passed to the client.

  2. SDK Support for Client CD-ROM

    The SDK has added support for remote CD-ROM devices. VMware Server and GSX Server allow a Console client to attach a physical CD-ROM device on the client's machine as a virtual device to a virtual machine running on a remote host. The SDK now allows you to detect when a client CD-ROM is in use, using VirtualDiskInfo.hostDev. The SDK also allows you to use VirtualDiskInfo.hostDev to disconnect the client CD-ROM by switching to a physical device on the remote host (where the virtual machine runs). This feature is only available with VMware Server and GSX Server hosts.

  3. SDK support for auto detect

    SDK clients can now get or set "auto detect" as the VirtualDiskInfo.hostdev property for CD-ROM and floppy devices.

  4. SDK E1000 Support

    The SDK has added support for E1000 virtual network adapters. Virtual Network adapters using the E1000 driver can be created for virtual machines on VMware Server hosts, allowing clients to take advantage of features such as VLAN support in the guest operating system. E1000 support is determined by the value of VirtualNetworkAdapter.features. The E1000 feature is only available with VMware Server hosts.

  5. The SDK Java samples directory has been updated:
    • GetHostVmInfoSample.java has been added to the directory.
    • PutUpdatesSample.java has been revised to demonstrate SDK 1.4 features.

Fixes Since the Previous Virtual Infrastructure SDK (VirtualCenter 1.3.1) Release

  1. Web Service Crashes If Passed a Bad vmHandle parameter

    An SDK client could crash the Web Service if it invoked an operation with a bad vmHandle. Typically, this happens when the client passes a bad path to the ResolvePath operation and ignores a fault resulting from the invalid input.
    To correct this, upgrade to VirtualCenter 1.4 or later. The Web Service now throws a fault when it receives a bad vmHandle.

  2. This version of the VMware SDK reference guide corrects information about the BadParameter fault. It is possible for the Create operation to throw this fault in rare circumstances. This information was inadvertently omitted from the documentation. It has now been corrected.
  3. This version of the VMware SDK reference guide supplies information about the format of the VirtualMachineInfo.suspendDirectory property that was missing from previous versions.
  4. This version of the VMware SDK reference guide corrects information about the ViewInfo datatype. Note that permissions are not populated for this datatype.
  5. This version of the VMware SDK reference guide corrects information about the PutUpdates operation. In some cases, properties can't be modified by invoking the PutUpdates operation, but were incorrectly documented as if they were modifiable. In other cases, properties can be modified with PutUpdates. The specific changes are:

    • All properties of the DiskFileInfo datatype can not be modified with PutUpdates.
    • The value of DiskKind can be modified if the device is a CD-ROM or floppy disk.
    • The diskDeviceInfo and diskFileInfo properties of the DiskType datatype can not be modified with PutUpdates.
    • The "name" and controllerType properties of VirtualDiskInfo can not be modified with PutUpdates.
    • The guestOS property of VirtualMachineInfo can not be modified with PutUpdates.
    • The "name" property of VirtualNetworkAdapter can not be modified with PutUpdates.

Known Issues in This Release

  1. Host Names in the Inventory Are Case Sensitive to the SDK.

    When the SDK is used to add a host to the VirtualCenter inventory, the host name is stored exactly as the SDK client passes it to the VirtualCenter server. Uppercase letters and lowercase letters in the name remain unchanged. Users should be aware of this case sensitivity when they use ResolvePath to locate a host in the inventory. If a host name is capitalized a certain way when added (for example, MYhost), it must be capitalized the same way in the path parameter passed to the ResolvePath operation. If you try to find myhost but the host name was stored as MYhost, ResolvePath will fail to match the host name.

  2. The SDK Stores UTF-8 in the Sysprep Customization File.

    When creating a Sysprep file to customize a virtual machine, the SDK writes the value of Autoprep.Sysprep.UserData.FullName directly to the Sysprep file. The SDK expects to work with UTF-8 encoding, but Sysprep expects the native encoding of the host operating system.

    To work around this problem, use the native encoding expected by Sysprep. Store a correctly encoded value -- not a UTF-8 value -- in Autoprep.Sysprep.UserData.FullName, and this value will be correctly stored in the Sysprep file.

  3. The Perl samples are incompatible with some SOAP::Lite versions.

    The Perl samples in the SDK toolkit are incompatible with some recent versions of SOAP::Lite, including versions 0.67 and 0.63. SOAP::Lite version 0.55 continues to work with the Perl samples.

  4. The README file contains incorrect versions for the manuals.

    The README file contains incorrect versions for the reference guide and the programming guide. The versions shown in the README are 1.2 and 1.1. The correct version of each guide is 1.4.

  5. The README file does not describe the PutUpdatesSample.

    A new sample, PutUpdatesSample, has been added to the sample directory. The README file should be amended to describe PutUpdatesSample as follows:

    This command demonstrates how to enable the autodetect feature for CD-ROM or floppy devices and how to reset a virtual CD-ROM device to the default host location.

    Run as: java com.vmware.sample.PutUpdates.PutUpdatesSample <URL> <username> <password> <vmpath> edit dev

  6. The README file incorrectly describes the syntax of the AnswerVMSample.

    The correct description for AnswerVMSample is the following.

    Run as: java com.vmware.sample.AnswerVM.AnswerVMSample <URL> <username> <password> <vmpath>

  7. The README file incorrectly describes the syntax of the QueryPerf2.pl Perl sample.

    The README file incorrectly describes the syntax of the QueryPerf2.pl Perl sample. The <vmpath> element should not be in the command. The correct syntax description follows.

    The command to run QueryPerf2.pl is:
    perl QueryPerf2.pl <URL> <username> <password> <host>


Using Perl Sample Code with VirtualCenter 2.0

The 1.4 SDK can be used to communicate with VirtualCenter 2.0. Certain differences apply when using Perl sample clients:

  • The Perl samples do not support SSL. VirtualCenter 2.0 uses SSL by default. To use Perl samples with a VirtualCenter 2.0 server, the VirtualCenter reverse proxy must be altered from its default settings to allow SDK requests over the non-SSL port. The default URL is:
    http://<hostname>/sdk. In this URL, <hostname> represents the name of the VirtualCenter 2.0 server machine.
  • Perl samples now take an optional <wsdl> argument that allows users to specify the location of the vma1 WSDL. The location is http://<hostname>/sdk/vma?wsdl. The optional argument need only be specified for use with VirtualCenter 2.0; the samples will work by default with VirtualCenter 1.x.