The last command should output a list of bridges, and the newly created br0 should be among them. If none, then apply changes, and check: netplan apply OBS! He also recommends doing netplan generate to catch any errors before netplan apply!Ĭheck for any errors with: netplan generate OBS! If using static IP, it might be different. Of course replacing eno1 with your interface. Edit the Netplan config: nano /etc/netplan/00-installer-config.yamlīefore editing, it looked like this: # This is the network config written by 'subiquity'Īdd lines for the bridge, so the file looks like this afterwards: # This is the network config written by 'subiquity' You can create bridges in different ways, if you’re familiar with others, that shouldn’t make a difference. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The one you’re looking for is the that has a line that starts with inet followed by the local IP of the machine. Start by finding the network interface you are using for network access. 2 - Set up networkįrom what I’ve seen, unless you know you have a specific reason not to, you should create a new network bridge (that we’ll call br0 here). Where is the name you want (for this guide, I used hassos). mkdir -vp /var/lib/libvirt/images/hassos-vm & cd /var/lib/libvirt/images/hassos-vmġ.5 - Set up a storage pool virsh pool-create-as -name -type dir -target /var/lib/libvirt/images/hassos-vm Find the current qcow2 image from the Home Assistant install page, and replace the link after the wget command. The image shown to download here is the one available when I tried. If not, then systemctl enable -now libvirtdġ.4 - Create directories and download image Where is the user that will deploy VMs 1.3 - Check that install was successful systemctl status libvirtd apt install -y qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils ovmf virt-managerġ.2 - Add user to libvirt and kvm groups adduser libvirt KVM might be installed already, the same with OVMF (needed to start a VM with UEFI) but just in case. Next, check that it can use KVM acceleration kvm-ok egrep -c '(vmx|svm)' /proc/cpuinfoĪs long as it doesn’t return 0, then you’re good. If not, add a sudo to commands as needed.įirst, check that your CPU can run VMs. I’ll also assume you are working as root. I’ll assume you have your OS installed, and have sudo rights. The reason I made this guide is because I could have used one If there is something wrong, or something that could be done smarter, please let me know! 1 - Preparation Please report both if you have success on other systems, and if not. I had an issue with my ConBeeII stick that I passed to HA, but no other issues, and I now use a PoE zigbee coordinator, so have not tried to fix), but I suspect it will work for many Debian-based systems. 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. 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. Installing KVM and deploying Home Assistant OS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |