Can't create VM following HA KVM(virt-manager) instructions

Installation
1

I got Ubuntu server 24.04 on a Dell i7-4790 cpu @ 3.60Ghz with 24G with 24GiB of RAM where i run some VMs for testing OS like Debian12, other ubuntu releases etc. For virtualization I use QEMU / KVM which I manage via Virtual Machine Manager with no issues.

Now I want to create a HA VM, and for that i was following the instalation info which gives me, in the end, a Shell promt and never install HA (like there’s no bootloader(?)) - this is what i got:

UEFI interactive Shell v2.2
EDK II
UEFI v2.70 (ubuntu distribution of EDK II, 0x00010000)
Mapping table
BLK1: Alias(s):
PciRoot (0x0) /Pci (0x1) /Ata (0x0)
BLK0: Alias(s):
PciRoot (0x0) /Pci (0x1) /Ata (0x0)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell>

NOTE: the only “big” difference between my configuration compared with the instrucions is that the firmware: it’s OVMF_CODE_4M.fd instead of OVMF_CODE.fd

If I play around with other settings in configuration, like using Generic Linux 2022 instead of the suggested Generic Default for the OS

I got to the same dead end.
Even forcing to enable boot menu and change the order so the SATA CDROM pointing to haos_ova-15.1.qcow2 goes first - i got the same result.

So summing it all up - what am I missing!?

Thanks for your time and support.

2

I just ended with the same problem…
Now it’s really late for the answer, but maybe helpful for another one.

This happens when you miss to decompress the downloaded file.
In this case use unxz for the image.

3

I ran into the very same issue, but I decompressed the .xy to a .qcow2 file. I’m very surprised the hypervisor setup even accepts the compressed file.

Might be a Linux distro packaging issue, but I had to install the OMV whatever package separately to get the UEFI boot option to even show up.

I would try downloading the image again, but expect if the DL were corrupted the .xy decompress would fail. T this point I’m at a lost what to try next. It’s been at least 7 years since I’ve seen an EFI shell, and it’s not so easy to navigate. I vaguely recall there is some way to list the commands from help thru a pager, b/c by default “help” rolls most out of view without it.
…
I didn’t read the tutorial carefully enough. Now that I did I see the qcow2 is an actual disk image file, and must be imported. Just below the download link are basic VM specs, one of which is a 32GB “storage” and that usually means disk space. Well if an actual disk image is imported, doesn’t define the storage? Anyway I’m gonna NOT create a new disk image but rather import the qcow2 and see if it can be booted.

Otherwise it’s possible (be seems unlikely) that you do need to create an empty container of sufficient size first, then import the qcow2 image into it.