Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Skip to end of metadata
Go to start of metadata

Admin Guide 2. Cloud Node. Hyper-V


Introduction to Hyper-V 2012 R2 plugin

The Hyper-V 2012 R2 plugin is not compatible with previous versions of Hyper-V. This means that you cannot use it with Hyper-V 2008 and 2012 R1 You must not have any hypervisors of these previous versions registered in Abiquo when you install the plugin.

Hyper-V 2012 R2 features

One connection to each Hyper-V server

Abiquo cannot make multiple concurrent connections to Windows-based machines.
For Hyper-V, set the Abiquo Configuration Property "abiquo.virtualfactory.openSession" to 1.

Shared datastore disks not deleted by Hyper-V

When you undeploy VMs with a shared datastore, Abiquo does not delete shared datastore files due to a limitation of WMI that the disks "cannot be found".  The VM cannot be deployed again because the deploy fails saying that the disk already exists. You can   access the shared datastore to delete the disks directly after you undeploy.


Hyper-V General Features

NUMA configurations(error) NUMA configurations for processors are not supported
Active Directory Integration

(tick) You can log in with an AD user or a local user. Use an Administrator account

High Availability

(tick) Abiquo High Availability supports Hyper-V
(error) Abiquo High Availability does not support Hyper-V with Microsoft Failover Clustering
(tick) Microsoft Failover Clustering can be used instead of Abiquo HA

Live Migration(tick)Abiquo detects live migration of virtual machines with storage migration and Failover
  • Before moving from Hyper-V manager, check the destination datastore is enabled in Abiquo, or the move will not be detected.
    • VM Moves in the same datastore are not supported
  • Abiquo uses Msvm_MigrationJob to detect moved VMs. These jobs exist for 5 minutes.  
    • Set the VSM polling interval for Hyper-V to less than 5 minutes or detection cannot be guaranteed

(tick) VHD templates
(tick) VHDX templates, but:

(error) No conversions from VHDX to other formats or vice versa
(error) No persistent VHDX templates

Network Controllers 
Virtual Machine NICs
  • Synthetic Ethernet Port is used
    • NO limit of 4 NICs per virtual machine
Disk Resize

(error) VHD system disk resize (VHD format does not support resize)
(error) VHDX system disk resize (not yet supported by Abiquo)
(tick) Auxiliary hard disks are VHDX and resize is permitted
(tick) External storage volumes resized outside of Abiquo are detected

Dynamic Memory

(error) Dynamic Memory is disabled for R2 in relation to unsupported NUMA processors

Remote Access

(tick) Remote access through the eye icon is supported with FreeRDP-WebConnect, which is a FreeRDP proxy for access to Hyper-V. This requires you to Configure FreeRDP for Hyper-V

Hyper-V Storage Features

  • Local disk
  • SMB share
  • Clustered shared volumes (CSV)
Clustered shared volumes
  • Abiquo can detect datastores with CSV enabled
  • Users can deploy on CSV-enabled datastores
  • Abiquo will detect movements between physical machines in a Failover Cluster
  • Abiquo can discover virtual machines that are deployed on CSV


  • Administrators cannot configure failover clusters within Abiquo
  • Administrators cannot manage failover clusters within Abiquo, for example, they cannot remove a VM
  • Abiquo High Availability is not compatible with Hyper-V Failover 
Disk Controllers
  • The primary system disk must be mounted on IDE controller to ensure compatibility
  • Secondary disks or volumes can be mounted on IDE or SCSI controllers
  • Each of the 2 available IDE controller support 2 disks, making a maximum IDE disks of 4
System Disks

(tick) IDE

Non-persistent Storage

(tick) Auxiliary hard disks on the Hyper-V datastore are always created in VHDX format

Persistent Storage

(tick) iSCSI integrated storage
(tick) Generic iSCSI storage
(error) NFS persistent storage is not available on Hyper-V

Persistent Virtual

(error) VHDX
(tick) VHD

Live Migration

(tick) Live migration is supported if the VM storage is moved to a different datastore
(tick) Abiquo will detect movements between physical machines in a Failover cluster

Hyper-V 2012 R2 important notes

Compatible Hyper-V Profiles

Before installing Hyper-V, check the Hypervisors Section of the Compatibility Tables for the profiles that are compatible with Abiquo.

Support for Hyper-V CSV in Abiquo 3.6 and above

Abiquo 3.6 introduced support for Hyper-V clustered shared volumes (CSV). Datastores with CSV enabled can be detected by Abiquo. And users can deploy in these datstores. Abiquo will detect movements between physical machines in a Failover Cluster. And Abiquo can discover virtual machines that are deployed on clustered shared volumes.

Administrators cannot configure failover clusters within Abiquo. In addition they cannot manage failover clusters, for example, they cannot remove a VM from a cluster. Abiquo High Availability is not compatible with CSV enabled datastores. 

This section explains how to configure Hyper-V for use with Abiquo.

The basic steps for Hyper-V configuration are:

  1. Configure Registry 
    1. Add the Hyper-V to a Windows domain 
    2. Run the powershell as the domain admin
  2. Enable remote desktop (optional)
  3. Configure Network 
    1. Configure firewall to allow incoming connections
    2. Create vSwitch in Hyper-V Manager
  4. Configure Storage 
    1. Enable iSCSI
    2. Change initiator IQN
    3. Mount shared datastore (samba)

This configuration requires registry modifications.

Hyper-V configuration steps for management through DCOM

Abiquo uses the WMI API, through J-Interop and JWbem libraries.

See  http://sourceforge.net/p/j-interop/code/138/tree/trunk/j-interop/src/readme.htm

Therefore, you will need to make the registry modifications described below to enable remote management and monitoring of Hyper-V.

Add Hyper-V to a Windows Domain

Add the Hyper-V server to a Windows Domain. 

Automatically Edit the Registry

Download the powershell script in the attached file change_registry.ps1

Log in as the domain admin. Use the fully qualified domain name, e.g. MY-DOMAIN\administrator

Run the powershell script.

This script will set the owner of the following registry keys to be changed to the user who runs the script. 

The manual process to change domain owner and edit registry keys is described in  Hyper-V Manual Registry Configuration

Registry Changes

These registry changes are included in the attached file hypervconfig.reg.

Windows Registry Editor Version 5.00


@="WBEM Scripting Locator"







Configure Network for Hyper-V

Configure the network in Hyper-V Manager by checking the MAC addressing and add a new network attached to the service network interface.

Configure VLANs

To allow Abiquo to manage VLANs in this Hyper-V server, add a new network attached to the service network interface. The network name should use appropriate characters and can be chosen by the network administrator. 

In Hyper-V Manager, go to Virtual Switch Manager -> New virtual network switch. Use the default options with 'External' type

Configure Persistent iSCSI Storage

This section describes how to configure persistent iSCSI storage.

Disk Management is in Win8MetroUI + Settings + "Create and format hard disk partitions"


Install iSCSI Service

The first thing you need to do is enable the iSCSI service and set it to start automatically

C:\Users\Administrator> sc config msiscsi start= auto
ChangeServiceConfig SUCCESS

C:\Users\Administrator> net start msiscsi
The Microsoft iSCSI Initiator Service service is starting.
The Microsoft iSCSI Initiator Service service was started successfully.
Manually Set Initiator IQN

iSCSI Configuration

Run iscsicpl   to open the iSCSI configuration popup on a Core installation

Once the iSCSI service is enabled, you must manually set the initiator IQN for the machine. To do this, go to Start > Administrative tools > iSCSI Initiator, and select the Configuration tab. Click the Change button. The following dialog appears:

You can accept the default value. You MUST do these steps manually even if the value of the initiator IQN field does not change. If this is not done manually, the initiator IQN will be dynamically computed based on the host and domain name, and may change without any warning, making the external storage volumes inaccessible.

iSCSI Firewall Rule

See Configure Firewall below to set the iSCSI firewall rules via netsh.

SAN Policy Configuration

Open a command line and run the following commands to set the appropriate SAN Policy:

san policy=OfflineAll

Configure Firewall for Abiquo and Hyper-V

For information about configuring Windows Firewall, please contact Abiquo Support.

Check Abiquo Configuration Properties File and Samba Service

Open an SSH session to the Abiquo server and check the following items:

Samba Server
  • Is the SAMBA server up and running?
    Start the service with the following command.
 /etc/init.d/smb start
  • Samba server must be started at boot
 chkconfig smb on
Abiquo Configuration Properties

Set the maximum number of open virtual factory sessions to 1.

Abiquo cannot make multiple concurrent connections to Windows-based machines.
The Abiquo Configuration Property "abiquo.virtualfactory.openSession" must be set to 1 to enable the Hyper-V plugin to work correctly.

abiquo.virtualfactory.openSession = 1

Check the SMB path in the config file /opt/abiquo/config/abiquo.properties

abiquo.appliancemanager.localRepositoryPath = /opt/vm_repository/
abiquo.appliancemanager.repositoryLocation =

abiquo.virtualfactory.hyperv.repositoryLocation = //<SERVER_IP>/vm_repository
abiquo.virtualfactory.xenserver.repositoryLocation =
abiquo.virtualfactory.vmware.repositoryLocation =

Restart the Abiquo Tomcat server

 /etc/init.d/abiquo-tomcat restart

Hyper-V in the Abiquo Platform

This page describes aspects of Hyper-V in the Abiquo platform

Remote Access

There are two options for remote access to Hyper-V virtual machines on the Abiquo platform.

FreeRDP Proxy

You can Configure FreeRDP for Hyper-V to set up remote access through the eye icon.

Default Configuration

Without this configuration, by default, in Hyper-V 2012, there is no VNC/RDP access through the eye icon. Abiquo provides RDP connection details for VMs. Users will require access to the hypervisor to connect to VMs.

Abiquo recommends xfreerdp. When you click the eye icon, Abiquo opens a popup displaying the connection details in xfreerdp format.

xfreerdp /d:my.domain.com /u:Administrator /p:abiqu0! /vmconnect:27b6f5f6-7c83-447c-83c3-b4093dc16f14 /v:


Best Practices

Abiquo will allow you to configure a system drive as the datastore. However, this is not recommended because of disk latency or potential disk space problems. You can use a local datastore or an SMB share.

Linux Guests

Linux Integration Services are required for disk controller detection.

Prepare to Add a Hyper-V Hypervisor to Abiquo

Create a virtual switch for use by Hyper-V before you add it to Abiquo, for example, using Hyper-V Manager.

Create a Network Service Type in Abiquo before you add the hypervisor.

Adding Hyper-V to the Abiquo GUI

Create a physical machine with a hypervisor type of Hyper-V.

General Information

Enter the User name. It can be an Active Directory login or local user. 

Use an Administrator account.

Network Interfaces

Select the network service type for your virtual switch.


The datastore must be a mapped drive. It can be:

  • local datastore (e.g. D:\)
    • Abiquo recommends that you do not use C:\ 
  • SMB share (e.g. X: which has the share \\SMB_SERVER\sharefolder mounted)
    • this configuration is suitable for a shared datastore