4.3 The Hyper-V Provisioning Adapter

This section includes the following information:

For known Hyper-V provisioning adapter issues, see Troubleshooting Hyper-V VM Provisioning Operations in the NetIQ Cloud Manager 2.1.5 Troubleshooting Reference.

4.3.1 Provisioning Actions Supported by the Hyper-V Provisioning Adapter

The following table lists the VM provisioning actions supported by the Orchestration Console for the hyperv provisioning adapter job.

Table 4-3 Provisioning Actions Supported by the Hyper-V Provisioning Adapter

Orchestration Server Managed VM Action

SLES 10

Windows 2000

Windows Server 2003

Windows Server 2008

Provision

X

X

X

X

Pause

X

X

X

X

Resume

X

X

X

X

Suspend

X

X

X

X

Shutdown

(X)1

X

X

X

Shutdown Agent

X

X

X

X

Restart

X

X

X

X

Hot Migrate2

X

X

X

X

Warm Migrate3

Move Disk Images4

X

X

X

X

Resync State5

X

X

X

X

Save Config

X

X

X

X

Apply Config

X

X

X

Create Template

X

X

X

Delete / Destroy Resource6

X

X

X

X

Checkpoint

X

X

X

X

Restore

X

X

X

X

Remove Template Dependency

X

X

X

Install Agent

X

X

X

Personalize

X

X

X

Cancel Action

X

X

X

X

Check Host Assignment

X

X

X

X

Launch Remote Desktop

X

X

X

Create Virtual Disk

X

X

X

X

Create Virtual NIC

X

X

X

X

Delete Virtual Disk

X

X

X

X

Delete Virtual NIC

X

X

X

X

1 Shutting down the Orchestration Agent on a SLES 10 VM (guest OS) is possible if the agent is installed manually in the VM.

2 A “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 action 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 action requires shared storage.

4 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 action does not require shared storage; the move is between separate repositories.

5 In addition to updating the VM’s status, Resync State collects information about the present VM host, even if the VM is migrated to some other host by an external action executed in a Hyper-V clustered environment. It also discovers the osfamily and ostype fact values.

6 The Delete/Destroy Resource action deletes all VM files (including snapshot files) except ISOs that are attached to the image. The action might not destroy the VM file folders if the VM was created in a non-default location.