- Article History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
- Feature this Article
VMware Infrastructure
VMware Infrastructure
Does the connection to the VI SDK support IPv6?
VMware ESX 3.5 has full IPv6 guest support, but currently does not have IPv6 support in the vmkernel.
Does VMware ESX 3.5 support FC HBA virtualization and NPIV?
Yes.
What HTTP file access features are supported in VMware ESX 3.5 or VMware ESXi 3.5 or VirtualCenter 2.5?
VMware ESX 3.5, VMware ESXi 3.5 and VMware VirtualCenter 2.5 supports HTTP GET or PUT operations on the following files and directories:
/folder – Directory listing of known datacenters on this server.
/folder?dcPath=DCPATH – Directory listing of all datastores available at this datacenter.
/folder?dcPath=DCPATH&dsName=DSNAME – Top-level directory listing of the datastore. If the server is VMware ESX, dcPath=DCPATH& can be omitted and defaults to dcPath=ha-datacenter.
/folder/PATH...?dcPath=DCPATH&dsName=DSNAME – Directory listing of files in a datastore directory. No virtual disk interpretation (all files shown). If the server is VMware ESX, dcPath=DCPATH& can be omitted and defaults to dcPath=ha-datacenter.
/folder/PATH.../disk-flat.vmdk?dcPath=DCPATH&dsName=DSNAME – Access individual files. If the server is VMware ESX, dcPath=DCPATH& can be omitted and defaults to dcPath=ha-datacenter.
(optional feature) /folder?dsMoRef=MoRef&path=PATH.../disk-flat.vmdk – Access individual files.
/host – Flat directory listing of all configuration files that you can GET or PUT remotely. The set of files that are available is controlled by a configuration file. This URL format is only supported if the server is VMware ESX server.
/host/file – Access individual files with directory structure collapsed and names may be altered for uniquness and VMware ESX version stability - please refer to remote CLI spec for more details. This URL format is only supported if the server is VMWare ESX.
/tmp/file – (HTTP PUT only) Put a file to the /tmp directory on the host. Implicit creation of directories is supported. This URL format is only supported if the server is VMware ESX.
You can GET and PUT any file on a datastore, you can GET and PUT a selected set of configuration files, and you can PUT files into /tmp or a subdirectory of /tmp on VMware ESX.
The easiest way to determine what URLs you can use (except /tmp) is to open https://
/folder and https://
/host in your web browser and browse. Any file that you can GET in the browser you can also PUT.For more information about how to PUT or GET files using Java programming, see the samples under com.vmware.vimsample.httpfileaccess package in VI SDK package.
In this release, HTTP DELETE is not supported, but deleting datastore files is supported in the VIM API by the DeleteFile operation in HostDatastoreBrowser (deprecated) and the DeleteDatastoreFile operation in FileManager.
How can I get cpu wait on VMware VirtualCenter 2.0.2?
With VMware VirtualCenter 2.0.2, the cpu wait counter name changed to cpu idle . With VMware ESX 3.5, it reverted to cpu wait.
Why am I seeing a compilation error while building the SDK 2.0.1 code in a VirtualCenter 2.5RC1 environment?
Changes in constructors in Axis 1.4 cause this error.
PropertyFilterSpec, ObjectSpec, CustomizationFixedName, SharesInfo, TraversalSpec
Do I need Pegasus for CIM classes?
Pegaus contains the providers that implement some generic CIM classes as well as CIM classes specific to VMware. (One can get more info about these classes from the following guide as well as DMTF Web site.
Pegasus is on the server but you can run your choice of CIM library on the client.
Which versions of VMware ESX and VMware VirtualCenter are compatible with SDK 2.0?
With vim2, applications work on VMware ESX 3.0.x, VMware ESX 3.5.x, VMware ESXi 3.5, VMware VirtualCenter 2.0.x, and VMware VirtualCenter 2.5.x without change. The new functionality delivered by vim25 works only with 2.5, 3.5, and 3i.
