Hyper‑V Configuration for Apporto OVA Cluster Nodes
This page adds first‑class Hyper‑V guidance to the Deployment section and aligns with the uploaded “Hypervisor Guide OVA Settings.” It also includes cross‑cutting recommendations that apply to all hypervisors.
Security note:
-
SSH access to OVA cluster nodes is not permitted for security purposes. Nodes are built on Ubuntu LTS.
-
Configure NTP time servers to UTC on all nodes.
Before you begin
-
Download the Apporto VM file for your environment from the installer’s Step 1 on the Running the on‑prem cluster install wizard page.
-
Time synchronization: Configure host/hypervisor NTP to use UTC for all cluster nodes.
-
Networking: A DMZ network is not required for Apporto nodes (use if your environment mandates it). VLAN tagging may be used as needed.
Workflow overview
-
Convert the Apporto disk image from VMDK to VHDX for Hyper‑V.
-
Create separate folders per node and copy a unique VHDX into each folder.
-
Provision new Generation 1 VMs using IDE disks, attach the corresponding VHDX, and configure CPU/RAM/Network.
-
Adjust Hyper‑V settings (vCPU limits, VLAN, Integration Services – Guest Services) before first boot.
-
Power on each node and complete the Network Config screen, then proceed with the cluster install wizard.
Step 1 — Convert VMDK to VHDX
Hyper‑V requires VHDX disks. Convert the provided VMDK using the Windows build of qemu‑img from cloudbase.it.
-
Download: https://cloudbase.it/qemu-img-windows/
# Example conversion command (dynamic VHDX)
qemu-img.exe convert source.vmdk -O vhdx -o subformat=dynamic dest.vhdx
Create one converted VHDX per node (e.g., Manager.vhdx, Worker1.vhdx, Worker2.vhdx, Worker3.vhdx). Store each in its own folder to avoid mis-attachment.
Step 2 — Create the VM (Generation 1 with IDE)
-
Open Hyper‑V Manager → New → Virtual Machine, provide a Name for each Node to be used.
-
It’s suggested to store each VM or .vhdx in separate folders for each node.
-
Generation: Select Generation 1. Generation 2 and SCSI disks are not yet supported for these images.
-
Memory: Static memory. Dynamic Memory has not been fully tested; do not enable.
-
Networking: Connect to the appropriate virtual switch. If your environment uses VLANs, set the VLAN ID after creation (see Step 3).
-
Storage: “Use an existing virtual hard disk,” then browse to the .VHDX located in the separate VM folders for each Node. IDE Controller (IDE 0). It’s also suggested that each Node have at least 60-70Gb HDD Disk size be used.
Step 3 — VM settings to adjust before first boot
-
Processor: Set the required number of virtual processors per node according to your sizing. Consider setting a vCPU cap consistent with cluster sizing guidance in Prerequisites → Components.
-
Enable VLAN identification and specify the VLAN ID if required by your environment.
-
Integration Services: Enable Guest Services.
-
Disks: Ensure the converted VHDX is attached to an IDE controller (not SCSI).
Do not power on the VM until all settings above are applied. Powering on with incomplete settings can lead to rework and unnecessary troubleshooting.
Step 4 — Power on and configure the node
-
Power on the Manager node first.
-
Network Config
-
IP configuration (static recommended for all nodes)
-
DNS, Default Gateway
-
Control plane FQDN (your Apporto instance domain)
-
-
Repeat for each Worker node.
-
Open https://[your_manager_node] in a browser to access the On‑Premises Cluster Management tool and proceed with the cluster install wizard.
Notes and recommendations
-
Operating system: Use Windows Server 2025 with Hyper‑V Manager. Windows Server Core has not been tested/supported for this workflow.
-
DMZ placement: Not required. Place nodes per your networking/security policies.
-
VLAN tagging: Supported; configure as your environment requires.
-
NTP/Time: Keep hypervisor host time in UTC for consistency across all cluster nodes.