Add the Hyper-V server to a Windows Domain.
Download the powershell script in the attached file change_registry.ps1
Log in the hypervisor as domain administrator (DOMAIN\USER or USER@DOMAIN) and run the powershell script.
This script will change some registry keys values and set their owner to the user who runs it. This allows Abiquo administer the hypervisor remotely with the domain user.
Abiquo newest versions use WinRM for some management operations. Among others:
Clone VM template disks from VM repository during VM deploy
Allow unmapped Samba shares to be used as datastores
To enable WinRM, use the commands below:
Enable the WinRM service and set some basic properties
Create a new certificate for the WinRM service and copy the certificate thumbprint:
Create an HTTPS listener for WinRM using this certificate to encrypt service requests:
The new copy disk procedure requires CredSSP to be enabled in WinRM. To that end, you’ll need to run the following in every HV added in Abiquo:
The WinRM configuration and requirements are detailed here:
You need to open the following ports in HyperV for the RS appliance to be able to manage it remotely:
|2179||VM RDP||VM console remote access|
WMI uses a dynamic port range to provide WMI services on top of the DCOM service. It is possible to configure this service to use an static port, but this is out of Abiquo scope.
Check Microsoft documentation for further details on this.
Configure the network in Hyper-V Manager by checking the MAC addressing and add a new network attached to the service network interface.
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
Launch a cmd command line to enable the iSCSI service and set it to start automatically:
Once the iSCSI service is enabled, you must set the initiator IQN for the machine manually. Go to Start > Administrative tools > iSCSI Initiator > Configuration and Click the Change button.
The dialog below will appear. You can accept the default value.
See Configure Firewall (above) to set the iSCSI firewall rules via netsh.
Open a command line and run the following commands to set the appropriate SAN Policy:
Edit the /opt/abiquo/config/abiquo.properties and update its contents as described below:
Enable WinRM related properties if needed
Configure the appliance library related properties
To use cloud-init, you will need to add a hyperv-iso folder to the VM repository. After the Abiquo server is up and running, check if this folder is present, for example in the default location.
If the hyperv-iso folder is not present, then create it, and set its owner to "tomcat"
When using HyperV, you must take Generation 1 and Generation 2 VM features, requirements and capabilities into account when dealing with VMs and VM templates.
If the VM or VM template is not using the right settings, VMs might not be deployed, or they could be unable to boot:
Abiquo will deploy the VM as Gen2 if the primary disk is SCSI, otherwise, it will deploy it as Gen1. If the VM is Gen2, all the disks must be in VHDX or ISO format, and the template must be UEFI boot-capable.
Check the links below for the all the details.
For Hyper-V, enter the credentials as follows:
Remember that NTP is mandatory.
|Generation V1/V2 virtual machines|
Virtual machines V1 are supported
Virtual machines V2 are supported
|NUMA configurations||NUMA configurations for processors are not supported|
|Active Directory Integration|
You can log in with an AD user or a local user. Use an Administrator account
Abiquo High Availability
Microsoft Failover Clustering
Abiquo High Availability and Microsoft Failover Clustering can not be used at the same time
|Live Migration|| Abiquo detects VM live migrations with storage migration and Failover|
VHDX templates, but:
No conversions from VHDX to other formats or vice versa
No persistent VHDX templates
|Virtual Machine NICs|
VHD system disk resize (VHD format does not support resize)
VHDX system disk resize (not yet supported by Abiquo)
Auxiliary hard disks are VHDX and resize is permitted
External storage volumes resized outside of Abiquo are detected
Dynamic Memory is disabled for R2 in relation to unsupported NUMA processors
|Clustered shared volumes|
Auxiliary hard disks on the Hyper-V datastore are always created in VHDX format
iSCSI integrated storage
Generic iSCSI storage
NFS persistent storage is not available on Hyper-V
|Persistent Virtual |
Live migration is supported if the VM storage is moved to a different datastore
Abiquo will detect movements between physical machines in a Failover cluster