You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
I have the same setup, and found you MUST have the VM setup and working BEFORE starting the VBoxVMService for this to work.
Install the Service ( or shut it down if already installed). Just make sure the service is not running.
Get everything working with HA first. Start and stop the VM through the VBox interface a couple of times and make sure it captures the stick each time.
Shut the HA VM down.
Configure the VBoxService ini file.
Start the VBoxService service up.
Using the VBoxService tooltray (you may need to start the tray program) start HA.
The VM should start without issue.
Using the Windows Device Manager you can watch the com ports captured by the VM disappear when it starts up.
That way you'll know that it started up properly.
Remember, while using the VBoxService you will not be able to control the VM through the VBoxManger GUI.
If you need any help shutting down the VM and starting it back up via command line for backup purposes let me know.
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:
The text was updated successfully, but these errors were encountered: