This article is intended for administrators wishing to create a 2x node + witness High Availability cluster utilizing Proxmox Virtual Environment (https://www.proxmox.com/en/proxmox-virtual-environment/overview) and StorMagic SvSAN (https://stormagic.com/svsan/).
Note: All images are clickable for enlarging, or can be opened in a new tab
Information
Guide Summary
This multipart guide will walk through the process to deploy 2x hyperconverged Proxmox VE nodes utilizing SvSAN virtualized block storage and a lightweight witness node, such as a Raspberry Pi.
Create the Guests
Via the same process to create the VSA VM, upload the install ISO, via the GUI or SCP/WinSCP to the below path:
scp /var/lib/vz/template/iso/en-us_windows_server_2022_x64_dvd_620d7eac.iso root@10.10.194.4:/var/lib/vz/template/iso/en-us_windows_server_2022_x64_dvd_620d7eac.iso
Creating a Ubuntu guest called ubuntu-1
Note: the storage on the below showing as Local is the storage of the ISO not the VM
Set the install ISO and guest OS type
Specify the graphics and storage controller:
Select the storage for the boot disk to sit on, e.g the shared storage
Select the disk size, in this example 32GiB
Specify the CPUs and cores
Specify the memory, in this example 4096MiB:
Specify the network bridge for the VM to attach to:
Review the Summary and Finish to create the VM
Install and set a static IP:
Install a Windows Guest
Installing a Windows VM on KVM requires a few extra steps which aren’t required for Linux VMs. This is a quick overview of those extra steps.
Two ISOs, copied to both hosts
1. A Windows installation ISO
2. The VirtIO Drivers ISO downloadable from the below URL:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
Creating the Windows VM:
Create the VM as a standard VM in Proxmox
Attach the Windows installation ISO and the Virtio ISO to the VM you are creating.
The VM will boot into the Windows installer, due to Windows being the first attached ISO.
Proceed to the “Which type of installation do you want” screen selecting Custom
No disks will be visible, with a warning "We couldn't find any drives. To get a storage driver, click Load driver."
Loading the Drivers
If the necessary driver is not shown select Rescan.
Select the driver for the version of Windows selecting Next to install the driver.
The drive should now display as a selectable location to install to.
If the drive does not appear then select refresh, select the drive to attach.
Select load driver again.
Select Browse, browsing to the NetKVM folder,
Select the OS, the AMD64 folder and select OK
Select next.
This will bring you back to the empty drive screen once more.
Select Load Driver.
Select Browse, browse to the Balloon folder, select your OS and AMD64
Click OK.
Continuing the installation
Note: This will need to be run on the KVM host where the VM is being created.
user@ubuntu:~$smcli vm eject-cdrom vmname
user@ubuntu:~$smcli vm insert-cdrom vmname hda /opt/StorMagic/ISOs/Windows<version>.iso
Once the CD for the Windows ISO remapped continue with the installation to completion.
Troubleshooting
If any drivers are missing these may be corrected after the installation.
Network
With Windows booted, open Device Manager.
There may be a Warning symbol next to the Network adapters. Should there be:
Right click the unknown device and select "update driver".
Select "Browse my computer for the driver software", selecting Browse
Select the VirtIO CDROM Drive. browse the netkvm folder/os type/amd64/and select install to install the driver.
Windows will scan for the best-suited driver with Windows utilizing a RedHat network adapter driver, select it and complete the setup.
There may be a Warning symbol also next to PCI devices. Should there be:
Right click the unknown device and select "update driver".
Select "Browse my computer for the driver software", selecting Browse
Select the VirtIO CDROM Drive. browse the netkvm folder/os type/amd64/and select install to install the driver.
Windows will scan for the best-suited driver with Windows utilizing a RedHat network adapter driver, select it and complete the setup.
Note from virtIO driver maintainers:
Fedora infrastructure hosts virtIO drivers and additional software agents for Windows virtual machines running on kernel-based virtual machines (KVM). virtIO is a virtualization standard for network and disk device drivers.
Fedora cannot ship Windows virtIO drivers because they cannot be built automatically as part of Fedora’s build system: the only way to build Windows virtIO drivers is on a machine running Windows. In addition, shipping pre-compiled sources is generally against Fedora policies. Microsoft does not provide virtIO drivers, you must download them yourself in order to make virtIO drivers available for Windows VMs running on Fedora hosts.
Detail here the needed ISO driver and how to get/use
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
Enable HA on the Guests
Select the guests to protect with HA
Failover time ~2min 30s
See Also
Comments
0 comments
Article is closed for comments.