How to install HASS on OpenMediaVault on a Virtual Machine?

I would like to run Home Assistant (HASS) in a virtual machine on OpenMediaVault 5. Up until OMV 4, this was easy because OMV (and the underlying Debian) supported VirtualBox and VB apparently didn’t have any problems booting UEFI images. Because OMV 5 (and the underlying Debian 10) no longer support VirtualBox, OMV now uses KVM ( libvirt ) for virtual machines (and it supports Cockpit to manage them). Unfortunately, this entails that it is no longer trivial to boot UEFI images on OMV/Debian 10, and - you guessed it - the official Home Assistant image for KVM (QCOW2) needs UEFI and trying to import and boot it in Cockpit will fail. I was unable to find any button or command in Cockpit that allows me to set the boot mode to UEFI.

I somehow managed to figure it out and documented my solution here:

Book marked for future reference.

I’ve been pondering putting Hass on my OMV server for a wile. I updated OMV to ver 5 a few weeks ago. And was not aware of the underlying system changes to the virtual side of things.


@tophee I am also on the same path and plan to move my Home Assistant installation from my RPi3 to my server with an OMV installation.

Since you have already a working solution, how do to you do USB passthrough to Home Assistant in KVM? I have to pass through Bluetooth and ZigBee Stick to the Guest machine.

I also moved my installation to OMV.
Didn’t install home assistant in a VM, just followed this guide, it’s quick and easy: Installing Home Assistant Supervised on Debian 10

The connected hardware will be automatically found. Navigate to supervisor > system and click the hardware menu option under Host System.
Use the ‘by-id’ address of your device in your settings.


Thank you for the suggest. I was thinking of this solution, too. Can you tell me why you did not used the official Supervised Installation method?

And, did you have any problems running OMV and Home Assistant on the same machine parallely?

I think that community guide follows the official supervised installation method, it’s mentioned at the start of the guide that this will give you a supported official install. The installation documentation at still hasn’t been updated to include the supervised method.

As for issues, no not really. Occasionally the HA url will be unavailable for like 10-20 seconds, but I think that’s more down to the Nic on my motherboard.

Good to hear, I am a little bit worried because I heard so many horror stories about parallel installations. And I saw that HA is changing the /etc/network/interfaces files which is also changed by OMV.

However, today I run a test with this set up on my Desktop in a virtual machine which was quite successful. I will test a little bit more and consider a migration.

I’ve put my HA installation on ice and am currently trying OpenHAB… But USB passthrough is not specific to Home Assistant, so I think I can help you out nonetheless. I solved this as described here:

The reason why I did not install HA directly on Debian/OMV is because I want to keep my server OS (which is in charge of much more than home automation) separate from a specific software/task.

I understand this. However, I am currently really struggling to set up a bridged network on OMV to properly set up Home Assistant as KVM VM on OMV. As a consequence, I am properly put this on ice.

I am now focusing my endeavours to have it as supervised installation on OMV. Does anyone know if an uninstall is possible in case something goes wrong? Can I uninstall the Home Assistant Supervised Installation again if something goes wrong?

I described how I solved this here:

I suppose you can always try to uninstall or undo everything the installation script ( does with the reverse terminal commands.

I guess there’s upsides to a VM install that I don’t see, but personally I see no reason to fear the supervised install method. A lot of the Home Assistant components will be running in docker anyway, so also kinda separated from the OMV/Debian OS.