Dear experts,
since I have a rather bored Tumbleweed server I want to install HA on Qemu. I need HACS for my Goodwe and my Zubadan and in the meantime I am desparate: with Copilot’s help I have succeded to get HA running but even the first user was no admin and therefore (at least from what I read) addons could not be installed.
I have tried the images haos_generic-x86-64-17.3.img.xz, haos_generic-86_64-17.3.qcow2.img, haos_generic-x86-64-18.2.img, haos_ova-17.3.ova and haos_ova-17.1.qcow2.xz; had various problems with /usr/share/qemu/ovmf-x86_64-4m-code.bin and var/lib/libvirt/qemu/nvram/homeassistant_VARS.
My last hope now is to use NI in the community here instead of AI…
Add-ons were renamed to Apps earlier this year. Copilot’s being a bit slow to catch up.
Go to the settings page & you should see Apps listed there
(In other words, the AI you were relying on doesn’t even know about a change that happened a year ago…)
Make sure it’s not trying to install in the deprecated core or supervised modes, as those are also deprecated and without support. You need to run HAOS or Container install.
many thanks for your replies, I try to outline what I did and what the results were:
- I installed haos_ova-17.3.qcow2 using the VM Manager by “importing an existing image” already at the end of March
- it booted and ran but my 1st user did not become an admin and there was no addon “button”
- later I read that the image must be resized to at least 60GB what I did not know back then; could this be the reason for no admin/addons" ?
- a few weeks ago I tried sudo wget https://github.com/home-assistant/operating-system/releases/download/18.2/haos_ova-18.2.qcow2.xz, unpacked it
- qemu-img create -f qcow2 /var/lib/libvirt/images/haos_disk.qcow2 80G
- qemu-img create -f raw /var/lib/libvirt/images/haos_disk.img 80G
- did not even boot
Frankly the more I read about it the more confused I become. Please help me to find the right path. Which is the right image ? Or do I need for my system another way in the 1st place ? What else do I have to provide so that you can give me hints ?
I find that hard to believe. You mean the same user you created at the onboarding page when you fired up HA the first time? If you go to Settings > People > Users tab, that user should belong to the Owner group, which has full Admin permissions.
Where are you looking for ‘Addons’ button? Hint it doesn’t exist anymore. Look under ‘Settings’ and is now called ‘Apps’.
many thanks for the hints but the 1st user really was no admin for sure. But first I must get the system back which is not bootable now:
- is [haos_ova-18.2.qcow2.xz from github the right image for Qemu ?
- are the 2 create commands (see above) for Qemu the right ones ?
Have you tried following the official docs for a KVM install? Should give you some pointers.
Although you DM’d me, I thought I would respond here in case it can help others down the road…
I haven’t done this is a few years (but I did take some notes on what I did) and I did this using virt-manager and I did this on an Ubuntu system which is likely different than Tumbleweed…
Yes, just unzipped it and place it in the appropriate directory for virt to get to.
No, I don’t think that makes a file bootable…
I use Ubuntu, and Ubuntu comes with a variety of UEFI files (located at /usr/share/) that can be used to boot the HAOS image from. These have filenames like:
OVMF_CODE_4M.ms.fd
OVMF_CODE_4M.secboot.fd
OVMF_CODE_4M.fd
but you have to pick one that does not use secure boot as this is a HAOS requirement. In this example, it would be the last one.
For RHEL, and CentOS, I believe you have to install OVMF to get these files, so Tumbleweed may have to do similarly.
You then somehow have to come up with the correct XML to get libvirt to use it.
Since virt-manager creates the XML automagically, here is the relevant part of what it came up with (in my case):
<os firmware="efi">
<type arch="x86_64" machine="pc-i440fx-focal">hvm</type>
<firmware>
<feature enabled="no" name="enrolled-keys"/>
<feature enabled="no" name="secure-boot"/>
</firmware>
<loader readonly="yes" type="pflash">/usr/share/OVMF/OVMF_CODE_4M.fd</loader>
<nvram template="/usr/share/OVMF/OVMF_VARS_4M.fd">/var/lib/libvirt/qemu/nvram/hassio_VARS.fd</nvram>
<boot dev="hd"/>
</os>
qemu-img resize haos_ova-18.2.qcow2 32G