Just my current notes, unfinished.
Tested with Kubuntu 26.04.
Only virt-install needs root priviliges, unless something else is said.
Before virt-install:
Uncompress:
xz -d haos_ova-XX.X.qcow2.xz
Should be before "Start up your virtual machine":
I did something wrong, I want to start from the beginning.
virsh destroy haos #Pulls the plug of the VM, no normal shutdown.
virsh undefine haos #Remove the VM but drive images won't be deleted.
If undefine doesn't work with something like "cannot undefine domain with nvram":
virsh edit haos #Maybe you have to choose an editor, this setting is for your whole Linux user profile.
#Search for the line starting with "<nvram". You need the path of the file you have to delete, something like /var/lib/libvirt/qemu/nvram/haos_VARS.fd and close the editor without changing anything.
rm /var/lib/libvirt/qemu/nvram/haos_VARS.fd #Delete the file in the path you found in the step before as, maybe as root.
#Try the virsh undefine line above again.
#Delete the QCOW2 file, there're all the files of the VM inside.
#Now you can start over again with a untouched QCOW2 file, e.g. freshly uncompressed from the archive.
Don't forget that if the VM should be started at boot:
virsh autostart haos
Troubleshooting for virt-install:
WARNING /home/user/Downloads/haos_ova-XX.X.qcow2 may not be accessible by the hypervisor. You will need to grant the 'libvirt-qemu' user search permissions for the following directories: ['/home/user']
virt-install doesn't like the folder. We recommend something like (as root):
mkdir /vm #Then "ls -la /" should have a line like "drwxr-xr-x 2 root root 4096 [date/time] vm"
mv <PATH TO QCOW2 FILE> /vm
#Now use virt-install with this new QCOW2 path /vm/...
WARNING Using -- osinfo generic, VM performance may suffer. Specify an accurate OS for optimal results.
Only the people creating the image can tell you that.
In "No access to the frontend" directly after the symptom description:
Login locally into the VM at first. The command for virsh is:
virsh console haos
This won't work if the console is already open somewhere else, e.g. in the console where you did virt-install. Close the other already open virsh console with Ctrl+5 or Ctrl+AltGr+9.
If you don't get something like "homeassistent login:" press enter. If you have that prompt, login as "root" (no password required). Now you can do all the things like a Linux admin, e.g. network troubleshooting from inside the VM. Before doing anything like port opening e.g. in ufw, check if the VM network settings are correct. E.g. virt-install has parameters to change how the VM is connected to the network. Maybe NAT is active so you need port forwarding of the ports you want to access (e.g. 8123 to have web-browser access) from that one IP where all VMs are hiding behind it to the internal IP:port. Or you want that the VM looks for the network like a normal additional machine (that mode is usually called something with bridge).
