Debian 11 - KVM Install - haos_ova-10.3.qcow2

[henrya]

Hello, i have tried to install HAOS 10.3 as KVM install.

Linux

I don’t get suggest.
Should haos_ova-10.3.qcow2 work’s with Debian 11 KVM install?

virt-install --name hass --description "Home Assistant OS" --os-variant=generic --ram=2048 --vcpus=2 --disk <PATH TO QCOW2 FILE>,bus=sata --import --graphics none --boot uefi

https://wiki.debian.org/KVM

KVM installation failed [RESOLVED]

I’m running Debian/Bullseye (11) on an AMD64 system. I downloaded haos_ova-9.3.qcow2.xz (and unzipped it) then I followed the howto at Linux - Home Assistant using the KVM (virt-manager) tab. The only inconsistency I found was that the org.qemu.guest_agent.0 seemed to already exist. However, once I stopped trying to add it, the installation seemed to proceed. Unfortunately I can’t connect to it using a homeassistant address. When I try to get the IP address to try that, the “details” tab on th…

@garydale

It seems that only one boot option works out of the 4 UEFI options available.

https://sources.debian.org/src/edk2/2020.05-3~bpo+1/debian/README.Debian/

How can i select the Bios option with cli?
Which should i choice for my Debian KVM haos_ova-10.3.qcow2 system?

Thank you.

[wmaker (Tommy Long)]

Pick the file /usr/share/OVMF/OVMF_CODE.fd

[henrya]

Can you create a template cli line for me?
Thank you

[os.habitats.tech (Habitats Tech)]

Not certain if this guide might be of use. It is centred around Debian using KVM.

3. HAOS - Install OS - Habitats Open Tech

[henrya]

@os.habitats.tech

Not certain if this guide might be of use. It is centred around Debian using KVM.

No, isn’t a solution for me, i will install HAOS with KVM.

[wmaker (Tommy Long)]

While you were editing, you pulled up a screen shot of virt-manager. If you are using virt-manager then use it to select that file.

If you are wanting to only use CLI, are you saying that --boot uefi did not work?
Depending on which version of libvirt is being used, it will auto-pick the file I suggested, but newer versions are auto-selected the secure boot versions. If you need to specify the file in the CLI, I don’t know what the syntax is, but it will be something like:
--boot uefi loader=/usr/share/OVMF/OVMF_CODE.fd,loader.readonly=yes,loader.type=pflash,nvram.template=/usr/share/OVMF/OVMF_VARS.fd,loader_secure=no
`

[henrya]

cd /var/lib/libvirt/images
wget https://github.com/home-assistant/operating-system/releases/download/10.3/haos_ova-10.3.qcow2.xz
unxz haos_ova-10.3.qcow2.xz

I get now

virt-install --name haoskvm --description "Home Assistant OS" --os-variant=generic --ram=4048 --vcpus=2 --disk /var/lib/libvirt/images/haos_ova-10.3.qcow2,bus=sata --import --graphics none --boot uefi

network 'default' is not active

virsh net-start default

Success

Welcome to Home Assistant
homeassistant login: root
Last login: Tue Jul 18 18:49:09 UTC 2023 on ttyS0
Last login: Tue Jul 18 18:51:22 on ttyS0
Welcome to Home Assistant OS.

Use `ha` to access the Home Assistant CLI.
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:9e:3a:1b brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.144/24 brd 192.168.122.255 scope global dynamic noprefixroute enp0s2
       valid_lft 3388sec preferred_lft 3388sec
    inet6 fe80::841:e6e0:f2d9:11b3/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:74:f7:eb:c6 brd ff:ff:ff:ff:ff:ff
    inet 172.30.232.1/23 brd 172.30.233.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:74ff:fef7:ebc6/64 scope link 
       valid_lft forever preferred_lft forever
5: vethce52a69@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether 16:e4:4c:36:90:78 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::14e4:4cff:fe36:9078/64 scope link 
       valid_lft forever preferred_lft forever
6: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:52:7c:e5:21 brd ff:ff:ff:ff:ff:ff
    inet 172.30.32.1/23 brd 172.30.33.255 scope global hassio
       valid_lft forever preferred_lft forever
    inet6 fe80::42:52ff:fe7c:e521/64 scope link 
       valid_lft forever preferred_lft forever
8: veth72b8888@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP group default 
    link/ether be:75:0f:38:b1:23 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::bc75:fff:fe38:b123/64 scope link 
       valid_lft forever preferred_lft forever
10: vetha056abb@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP group default 
    link/ether 96:5a:1c:74:00:89 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::945a:1cff:fe74:89/64 scope link 
       valid_lft forever preferred_lft forever
12: veth06e0332@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP group default 
    link/ether 6a:e0:d3:95:3b:17 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::68e0:d3ff:fe95:3b17/64 scope link 
       valid_lft forever preferred_lft forever
14: vethbaec8dc@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP group default 
    link/ether 3a:be:ae:43:82:10 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80::38be:aeff:fe43:8210/64 scope link 
       valid_lft forever preferred_lft forever
16: veth16f2f2e@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP group default 
    link/ether 32:51:ba:e6:66:46 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet6 fe80::3051:baff:fee6:6646/64 scope link 
       valid_lft forever preferred_lft forever
# 

How can if find the login IP for my HAOS 10.3 system in my home network?

https://wiki.archlinux.org/title/network_bridge#With_NetworkManager

now with —> 4. virbr0

https://www.linux-kvm.org/page/Networking#Public_Bridge

`

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:59:b4:74 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.158/24 brd 192.168.178.255 scope global dynamic noprefixroute enp0s3
       valid_lft 860504sec preferred_lft 860504sec
    inet6 fe80::a1be:f6fd:3d0f:1e15/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:d1:30:6c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::48c5:99fd:941f:c276/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:02:c4:45 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever

How can i get a IP adress for my HAOS 10.3 from my home net, such as 192.168.178.xxx?

Home Assistant OS in KVM Hypervisor

My next stop was Configuring Guest Networking page of KVM documentation. It offered several options corresponding to different scenarios, helping me confirm I wanted “Public Bridge”. This page had a few Linux distribution-specific scripts, including one for Debian. Unfortunately, it wanted me to edit a file /etc/network/interfaces which doesn’t exist on Ubuntu 22.04.

https://www.linux-kvm.org/page/Networking

https://www.linux-kvm.org/page/Networking#Public_Bridge

Info

virsh version
Kompiliert gegen die Bibliothek: libvirt 7.0.0
Verwende Bibliothek: libvirt 7.0.0

Verwende API: QEMU 7.0.0
Laufender Hypervisor: QEMU 5.2.0

@wmaker Did you have more input for me?

[wmaker (Tommy Long)]

@henrya

virt-install --name haoskvm --description "Home Assistant OS" --os-variant=generic --ram=4048 --vcpus=2 --disk /var/lib/libvirt/images/haos_ova-10.3.qcow2,bus=sata --import --graphics none --boot uefi

So it looks like you did NOT have to select a boot file, correct?

@henrya

How can i get a IP adress for my HAOS 10.3 from my home net, such as 192.168.178.xxx?

Here is a thread I recommend you take a look at. It is based on Ubuntu which is also a Debian deriviative, but take a look particularly at section 2 for setting up a Network on your Host machine, namely br0 bridge.

Install Home Assistant OS with KVM on Ubuntu headless (CLI only)

Installing KVM and deploying Home Assistant OS Since the install page only describes how to use KVM via a GUI, and I am using KVM in a server setting, I thought I’d share a quick guide to how to do this from CLI only. NOTE: This is for Ubuntu Server LTS 20.04 (though I upgraded after installing this to 22.04 (do-release-upgrade, and others have reported this working on 22.04 de novo, e.g., here. I had an issue with my ConBeeII stick that I passed to HA, but no other issues, and I now use a PoE …

[henrya]

You can create bridges in different ways, if you’re familiar with others, that shouldn’t make a difference. I used Netplan. Edit the Netplan config:

@wmaker
Why did you have choice netplan?

https://wiki.debian.org/BridgeNetworkConnections

[wmaker (Tommy Long)]

@henrya

You can create bridges in different ways

Correct!
The author of that Guide choose Netplan.
I myself used nmcli.
Be aware that some of these techniques use older and deprecated commands. The Debian Wiki you pointed to is using old commands.

[henrya]

Netplan is a Ubuntu way

x KVM QEMU Installation & Configuration Guide ⋆ Zack's

Bridge Network - Ubuntu Netplan

Ubuntu (Canonical) developed Netplan as an alternative (replacement) to configuring network interfaces over flat configuration files. Before Netplan, you had to manually modify /etc/network/interfaces file to either modify/remove an existing interface or to add a new one. IMHO I don’t like it, and I consider it just another layer of abstraction and an unnecessary replacement for something that worked just fine.

I’m search, prefer a only Debian 11 way with nmcli

xx KVM QEMU Installation & Configuration Guide ⋆ Zack's

Bridge Network - Network Manager

The bridge network will allow you to use the IP range of your home or office router, providing your virtual machines with the IP addresses from that range. If you installed KVM QEMU on a desktop system, your network is probably managed by the Network Manager. To create a bridge network interface with Network Manager, we will use the Network Manager’s command line interface command called nmcli.