A.5 VMware ESX VM Hypervisor (Experimental)

The following table represents the PlateSpin Orchestrate VM actions and whether or not PlateSpin Orchestrate can perform that action on the guest operating system.

NOTE:Novell considers the PlateSpin Orchestrate provisioning technology used in conjunction with VMware ESX as “experimental” because it has not yet been fully tested.

Table A-5 PlateSpin Orchestrate VM Actions Supported Operating Systems Using ESX

PlateSpin Orchestrate Managed VM Action

SLES 9

SLES 10

RHEL 4

RHEL 5

Windows 2003

Provision

X

X

X

X

X

Pause

 

 

 

 

 

Resume

 

 

 

 

 

Suspend

X

X

X

X

X

Shutdown

X

X

X

X

X

Shutdown Agent

X

X

X

X

X

Restart

X

X

X

X

X

Move Disk Image 1

X

X

X

X

X

Hot Migrate 2

X

X

X

X

X

Warm Migrate 3

X

X

X

X

X

Resync State

X

X

X

X

X

Save Config

X

X

X

X

 

Apply Config

 

 

 

 

 

Create Template

 

 

 

 

 

Delete / Destroy Resource

X

X

X

X

X

Checkpoint

X

X

X

X

X

Restore

X

X

X

X

X

Remove Template Dependency

 

 

 

 

 

Install Agent

X

X

X

X

X

Personalize

X

X

X

X

X

Cancel Action

X

X

X

X

X

Check Host Assignment

X

X

X

X

X

Launch Remote Desktop

X

X

X

X

X

1 A “move” is the relocation of VM disk images between two storage devices when the VM is in a not running state (including VMs that are suspended with a checkpoint file). This function does not require shared storage; the move is between separate repositories.

2A “hot migrate” (also called a “live migrate”) is the migration of a running VM to another host and starting it there with minimal resulting downtime (measured in milliseconds). This function requires shared storage.

3 A “warm migrate” is the migration of a suspended VM to another host and starting it there with brief resulting downtime (measured in seconds). This function requires shared storage.