-
Notifications
You must be signed in to change notification settings - Fork 48
Description
I followed the comprehensive guide from "The Hook Up" channel on YouTube that I think many people have followed. In it, they outline how to get Home Assistant running on a Windows 7/10 machine using Oracle VirtualBox as the VM host for Ubuntu/hassio. At the end of the guide there are steps directing users to download the VBoxVmService in order to get Home Assistant to automatically start and run as a background service in the event of a machine reboot.
Well, here's the issue. As long as VBoxVmService was in the mix, I had no way to go into the VirtualBox settings, under USB, and enable devices to pass through to the VM. It did not matter if I stopped the VM from running, then loaded up the VirtualBox GUI, the settings would only ever show "no devices available"

My theory is that the initialization code for the background service within VBoxVmService is spinning up too early in the kernel load process, before it's had a chance to load USB drivers for attached devices. As a result it initializes a permanent empty index of available USB devices.
To test, I had my ZigB / ZWave stick installed that I needed for Home Assistant, but I also had a basic USB flash drive as a known-good secondary device, as well as the Logitec Keyboard and Mouse USB dongle.
Once I uninstalled VBoxVMService (without changing anything else), the USB tab in VirtualBox was able to properly display the list of attached USB devices, and allow me to pass them into the VM. As you can see, all 3 devices appeared:

A few final points:
- No, it did not matter whether I was using USB 1.1, 2.0, or 3.0
- Yes, Virtualbox and the extension packs were at the latest version
- Yes, all of the chipset and OS drivers were up-to-date