The following sections provide solution to the problems you might encounter while performing provisioning operations on VMs managed by the Hyper-V hypervisor:
The VM is Suspended When you Try to Revert the Snapshot of a Powered-on VM Running on a Hyper-V host
Source:
Hyper-V provisioning adapter job
Explanation:
If you try to revert the snapshot of a powered-on VM running on a Hyper-V host, the VM is suspended. This is a known behavior of VMs running on a Hyper-V host.
Action:
Provision the suspended VM:
-
In the Orchestration Console, right-click the suspended VM, then click .
The Provision VM dialog box is displayed.
-
In the drop-down list, select the appropriate Hyper-V host.
-
Click .
Hyper-V Provisioning Jobs Fail When Several Jobs Are Started Simultaneously
Source:
Hyper-V provisioning adapter job
Explanation:
If you start more than the default number of Hyper-V provisioning jobs at the same time (for example, creating a template on each of three Hyper-V VMs simultaneously), the jobs fail because of an insufficient number of joblet slots set aside for multiple jobs.
Action:
If you need to run more than the default number of joblets (one is the default for Hyper-V) at one time, change the value on the VM host configuration page, or change the value of the joblet.maxwaittime fact in the hyperv policy so that the Orchestration Server waits longer to schedule a joblet before failing it on the VM host because of no free slots.
For more information, see “Joblet Slots” in the The Resource Object
section of the NetIQ Cloud Manager 2.1.5 Orchestration Console Reference.
OS info for Hyper-V VMs is Not Always Auto-Discovered by the Orchestration Agent.
Source:
The Orchestration Agent
Explanation:
As with other VMs managed by Xen and VMware, the OS info for Hyper-V VMs is not always auto-discovered by the Orchestration Agent.
The OS info for Hyper-V VMs is discovered only in the following circumstances:
-
The Discover VM Images event triggers a Resync event for offline VMs to get OS info. However, OS info is not retrieved for the discovered templates.
-
The Resync event on the VM retrieves the OS family and type if it is offline.
-
The Resync event on the template sets the OS family to “Windows” because only Windows templates are supported in the hyperv provisioning adapter.
-
The Create Template event tries to retrieve OS info before creating the template. Create Template succeeds only if the VM’s OS family is Windows.
Action:
To work around this issue, you can either enter this information manually, install the Orchestration Agent on the VM to enable discovery, or use the Key/Value Pair Exchange mechanism to support integration services installation.
Limitations of Linux VMs as Guests on Hyper-V
Source:
Hyper-V provisioning adapter job
Explanation:
The Orchestration Server does not support the or actions for Linux-based Hyper-V VMs.
Action:
None.