Nutanix AHV
Nutanix AHV deployment
Section titled “Nutanix AHV deployment”For Nutanix AHV, ARROW ships a QCOW2 disk. AHV runs on KVM, and its image service accepts QCOW2 as it is, so deploying takes three steps: add the disk to the image service, create a VM that clones it onto a SCSI disk, and power the VM on. The README in the ZIP repeats these steps with your VM’s file names and the disk’s checksum already filled in.
What is in the download
Section titled “What is in the download”| File | What it is |
|---|---|
*.qcow2 | The VM’s disk image |
*-nutanix-deployment.txt | A summary of this build, the disk’s SHA-256, and the steps below with your names filled in |
The image service converts the QCOW2 to raw when it imports it, so the image takes more room in the storage container than the file does on your workstation.
Before you start
Section titled “Before you start”- An AHV cluster, managed from Prism Central or Prism Element.
- Port 2007 open on the cluster. The image service uses it.
- Room for a VM with 4 vCPUs and 8 GiB of memory.
- The boot mode for your image. It has to match the disk, or the VM finds nothing to boot:
| Image | Prism Central | Prism Element | aCLI |
|---|---|---|---|
| Kali, Parrot, Ubuntu | Legacy BIOS Mode | Legacy BIOS | (the default) |
| Windows 11 | UEFI BIOS Mode, Secure Boot unchecked | UEFI, Secure Boot unchecked | uefi_boot=true |
Step 1: Extract the ZIP and check the disk
Section titled “Step 1: Extract the ZIP and check the disk”Prism cannot read the ZIP, so extract the .qcow2 first, then confirm its hash matches the Disk SHA-256 line in the README:
# Linux or macOSunzip kali-arrow-client-nutanix-*.zipsha256sum kali-arrow-vm-ab12.qcow2# WindowsExpand-Archive .\kali-arrow-client-nutanix-*.zip -DestinationPath .Get-FileHash .\kali-arrow-vm-ab12.qcow2 -Algorithm SHA256Step 2: Add the disk to the image service
Section titled “Step 2: Add the disk to the image service”Nutanix advises against uploading images larger than 2 GB from a browser, because browsers limit the size of a file upload. ARROW disks are larger than that, so add the image from a URL instead. Prism Central accepts HTTP, HTTPS and NFS URLs; Prism Element accepts HTTP and NFS.
Whichever way you add it, give the image a name you will recognise, such as arrow-kali-arrow-client. You pick it by that name in Step 3.
From a machine the cluster can reach
Section titled “From a machine the cluster can reach”Serve the folder holding the .qcow2 over HTTP from any machine the cluster can reach. Python’s built-in server is enough:
python3 -m http.server 8000Then add the image:
- Prism Central: open Infrastructure > Compute > Images, click Add Image, choose URL as the Image Source, and enter
http://<that machine>:8000/<disk file>. - Prism Element: click the gear icon, open Image Configuration, click Upload Image, set Image Type to Disk, choose a Storage Container, choose From URL, and enter the same URL.
From a storage container
Section titled “From a storage container”- Connect to any Controller VM over SFTP on port 2222 (WinSCP, or
sftp -P 2222), signing in with your Prism credentials. - Upload the
.qcow2into a storage container. - Add the image From URL as above, with the URL
nfs://<Controller VM IP>/<container>/<disk file>.
With aCLI
Section titled “With aCLI”Over SSH to a Controller VM, with either kind of URL:
acli image.create arrow-kali-arrow-client \ source_url=http://<that machine>:8000/<disk file> \ container=<container> \ image_type=kDiskImage \ sha256_checksum=<Disk SHA-256 from the README>sha256_checksum makes the image service check the disk as it imports it.
Step 3: Create the VM
Section titled “Step 3: Create the VM”Prism Central
Section titled “Prism Central”- Open Infrastructure > Compute > VMs and click Create VM.
- Set vCPU(s) to 4 and Memory to 8 GiB.
- Under Disks, click Attach Disk. Set Type to Disk, Operation to Clone from Image, pick your image, and set Bus Type to SCSI.
- Under Networks, click Attach to Subnet and pick the subnet the VM should use. The VM takes its address by DHCP, or comes up on the static IP set on its device request.
- Set Boot Configuration from the table in Before you start.
- Leave Guest Customization off. The image is already configured.
- Click Create VM.
Prism Element
Section titled “Prism Element”Click Create VM on the VM dashboard and use the same values. The disk is added with Add New Disk and Operation set to Clone from Image Service, and the firmware is set to Legacy BIOS or UEFI from the table above.
acli vm.create arrow-kali-arrow-client num_vcpus=4 memory=8Gacli vm.disk_create arrow-kali-arrow-client clone_from_image=arrow-kali-arrow-client bus=scsiacli vm.nic_create arrow-kali-arrow-client network=<network name>For a Windows image, add uefi_boot=true to vm.create.
Step 4: Power on
Section titled “Step 4: Power on”Click Power On in Prism, or run:
acli vm.on arrow-kali-arrow-clientNo login is needed for normal operation. Once the VM has an address, it connects to ARROW on its own, and it appears on your Devices page.
Troubleshooting
Section titled “Troubleshooting”The VM finds nothing to boot. The boot mode does not match the disk. Power the VM off, set Boot Configuration (or the firmware, in Prism Element) from the table in Before you start, and power it on again.
A browser upload stalls or fails. Browsers limit file uploads to about 2 GB. Add the image from a URL instead, as in Step 2.
Which disk bus should I use? SCSI, the bus Nutanix recommends. Its Create VM dialog keeps SATA, PCI and IDE for guests without VirtIO SCSI drivers, and those are slower. ARROW images carry the VirtIO SCSI drivers, so they do not need them.
Is my guest OS on Nutanix’s support list? Nutanix lists Debian 10 to 13 and Ubuntu, with SCSI as the recommended bus. Kali Linux and Parrot OS are not on the list; both are built on Debian. Nutanix lists Windows 11 with Secure Boot and vTPM enabled, on AOS 6.5.1 and AHV 20220304.242 or later. ARROW’s Windows 11 image was installed without either, and runs with UEFI and Secure Boot off.
Windows drivers. The Windows image carries the Fedora VirtIO drivers, with the SCSI storage driver installed as a boot driver. Nutanix publishes its own VirtIO drivers: after the first boot you can install the Nutanix VirtIO MSI (Nutanix Support portal, Downloads, AHV, VirtIO) or Nutanix Guest Tools, which include it. Nutanix Guest Tools are otherwise not needed.
The VM needs a static IP. Set it in the device request, or by hand from the VM console. See Static IP addressing.