Vmware Virtual Machine
Keena Wiegert
Connect Fusion or Workstation to remote vSphere or ESXi servers to launch, control and manage VMs as well as physical hosts. Effortlessly migrate local VMs to your private cloud with the ease of drag-and-drop.
Desktop Hypervisor is a line of products consisting of VMware Workstation and VMware Fusion which let users run virtual machines, containers, and Kubernetes clusters on a Windows, Linux or Mac computer.
No, Workstation Pro and Fusion Pro do not provide a separate evaluation mode. Users wishing to evaluate before purchasing a commercial use license may do so with the built-in personal use license, provided the products are not used for commercial purposes without first purchasing a license. (i.e. users may personally evaluate the product to determine if they wish to use it in a commercial setting, whereby they would then require a commercial use license for that setting)
Workstation Pro and Fusion Pro commercial subscriptions include production support from the authorized Broadcom reseller who sold the licenses. Resellers follow the standard Broadcom support model and have an escalation path to VMware product engineering teams. Users with Personal Use licenses can obtain community support from our forums. Per-Incident support is no longer available.
No, Customers with active support contracts will be able to continue to use the Desktop Hypervisor products without any changes. When a customer's existing SnS expires, a new Subscription license is required to continue use.
Upon expiry of a subscription license, the product will default back to the Personal Use mode. While VMs will continue to boot, the product will be unauthorized for use in a commercial setting until the license key has been replaced with a new, valid subscription license key.
Workstation Pro and Fusion Pro were previously sold with perpetual licenses and an optional Support and Subscription add-on which provides access to major-version updates for the duration of the subscription term. These terms will continue to be honored, and the existing products will continue to be supported for the duration of their lifecycle, which can be found here. The perpetual licenses will not expire. When new Major versions of Fusion Pro and Workstation Pro are released, a new license key will be required, otherwise the products will operate in Personal Use mode.
As of April 30th, 2024 Workstation Player and Fusion Player are considered EOS (End of Sale) and are unavailable for purchase going forward. Customers with active contracts will continue to be supported for the duration of their contract. This means products will receive regular updates, and support tickets can be filed.
Users can now enjoy the full-featured versions of Workstation Pro and Fusion Pro without requiring a purchased license key. Workstation Pro and Fusion Pro installers, now by default, provide a free personal-use license built-in. While Workstation Player and Fusion Player are no longer being sold, they will continue to function and receive product updates until the next major versions are released.
VMware Workstation Player is an ideal utility for running a single virtual machine on a Windows or Linux PC. Organizations use Workstation Player to deliver managed corporate desktops, while students and educators use it for learning and training.
VirtualMachine extends the ManagedEntity type because virtual machines are part of a virtual infrastructure inventory. The parent of a virtual machine must be a folder, and a virtual machine has no children. Destroying a virtual machine disposes of all associated storage, including the virtual disks. To remove a virtual machine while retaining its virtual disk storage, a client must remove the virtual disks from the virtual machine before destroying it. Properties
This property is set when a virtual machine is created or when the ReconfigVM_Task method is called. The virtual machine configuration is not guaranteed to be available. For example, the configuration information would be unavailable if the server is unable to access the virtual machine files on disk, and is often also unavailable during the initial phases of virtual machine creation.
datastore* PManagedObjectReference[]
to a Datastore[]
Can be explicitly refreshed by the RefreshStorageInfo operation. In releases after vSphere API 5.0, vSphere Servers might not generate property collector update notifications for this property. To obtain the latest value of the property, you can use PropertyCollector methods RetrievePropertiesEx or WaitForUpdatesEx. If you use the PropertyCollector.WaitForUpdatesEx method, specify an empty string for the version parameter. Any other version value will not produce any property values as no updates are generated.
To retrieve the configuration, you typically use ChildConfiguration. To change the configuration, use UpdateChildResourceConfiguration.
resourcePool*ManagedObjectReference
to a ResourcePool
This property is set when a virtual machine is created or associated with a different resource pool. Returns null if the virtual machine is a template or the session has no access to the resource pool.
rootSnapshot*ManagedObjectReference[]
to a VirtualMachineSnapshot[]
A client using this ticketing mechanism must have network connectivity to the ESX server where the virtual machine is running, and the ESX server must be reachable to the management client from the address made available to the client via the ticket. Acquiring a virtual machine ticket requires different privileges depending on the types of ticket:
- VirtualMachine.Interact.DeviceConnection if requesting a device ticket.
- VirtualMachine.Interact.GuestControl if requesting a guestControl or guestIntegrity ticket.
- VirtualMachine.Interact.ConsoleInteract if requesting an mks or webmks ticket.
- VirtualMachine.Interact.DnD if requesting a drag and drop ticket.
Any % (percent) character used in this name parameter must be escaped, unless it is used to start an escape sequence. Clients may also escape any other characters in this name parameter. The privilege required on the source virtual machine depends on the source and destination types:
- source is virtual machine, destination is virtual machine - VirtualMachine.Provisioning.Clone
- source is virtual machine, destination is template - VirtualMachine.Provisioning.CreateTemplateFromVM
- source is template, destination is virtual machine - VirtualMachine.Provisioning.DeployTemplate
- source is template, destination is template - VirtualMachine.Provisioning.CloneTemplate
- source is encrypted virtual machine - Cryptographer.Clone
If a host is specified, the secondary virtual machine will be created on it. Otherwise, a host will be selected by the system. If the primary virtual machine (i.e., this virtual machine) is powered on when the secondary is created, an attempt will be made to power on the secondary on a system selected host. If the cluster is a DRS cluster, DRS will be invoked to obtain a placement for the new secondary virtual machine. If the DRS recommendation (see ClusterRecommendation) is automatic, it will be automatically executed. Otherwise, the recommendation will be returned to the caller of this method and the secondary will remain powered off until the recommendation is approved using ApplyRecommendation. Failure to power on the secondary virtual machine will not fail the creation of the secondary. Required PrivilegesVirtualMachine.Interact.CreateSecondarySince vSphere API 4.0Parameters
If a host is specified, the secondary virtual machine will be created on it. Otherwise, a host will be selected by the system. If a FaultToleranceConfigSpec is specified, the virtual machine's configuration files and disks will be created in the specified datastores. If the primary virtual machine (i.e., this virtual machine) is powered on when the secondary is created, an attempt will be made to power on the secondary on a system selected host. If the cluster is a DRS cluster, DRS will be invoked to obtain a placement for the new secondary virtual machine. If the DRS recommendation (see ClusterRecommendation) is automatic, it will be automatically executed. Otherwise, the recommendation will be returned to the caller of this method and the secondary will remain powered off until the recommendation is approved using ApplyRecommendation. Failure to power on the secondary virtual machine will not fail the creation of the secondary. Required PrivilegesVirtualMachine.Interact.CreateSecondarySince vSphere API 6.0Parameters
If the virtual machine is on a vSAN datastore, then the Fault Tolerance secondary virtual machine and the tie-breaker file also have to be placed on that same vSAN datastore. Conversely, if a primary VM is not using vSAN datastore, then its Fault Tolerance secondary virtual machine can not be placed on a vSAN datastore. Fault Tolerance is not supported for VMs that are using both vSAN and non-vSAN datastores for its configuration and disks. If the virtual machine is using persistent memory for any of its disks, then its corresponding secondary disk placement entry should not be specified in the FaultToleranceVMConfigSpec. The system will automatically place the corresponding secondary disk on persistent memory.
Snapshots are not supported for Fault Tolerance primary and secondary virtual machines. Any % (percent) character used in this name parameter must be escaped, unless it is used to start an escape sequence. Clients may also escape any other characters in this name parameter. Required PrivilegesVirtualMachine.State.CreateSnapshotParameters
d3342ee215