![]() I’m not sure which of these instructions may apply to my setup. VirtualBox.Org USB Troubleshooting Instructions (Chapter 12.8.7) in Whonix Gateway and Workstation – System Settings- Removable Devices I checked the boxes for all USB mounting settings. Also used the USB device filter settings to add a generic filter which is supposed to mount any type of connected USB drive. in VirtualBox Manager I used the Settings in both Gateway and Workstation to enable automatic or manual USB mounting. successful install of VirtualBox 5.0.8 Extension Pack on Ubuntu for USB support (is this the only install I need?) ![]() newest versions of VirtualBox, Whonix Gateway and Whonix Workstation – Whonix and VirtualBox – all running fine. ![]() When I connect a USB drive to my PC running Ubuntu, and then run VirtualBox/Whonix, the drive is not found by VB/Whonix (USB status icon says “no USB devices connected). I'll update this in case there are further disruptions to connectivity in the host nut-server scenario currently running, so far successfully.I’ve followed Whonix documentation but haven’t been able to get USB drives enabled. I may try some additional tests in a libvirt/kvm VM just for comparison. Or perhaps other users here have experienced similar sporadic disconnects with USB equipment passed through to their guest VMs. I am happy to run nut-server on the host (hopefully this situation will remain stable), but I thought I should report this in case devs might see some issue that could be of interest. I only noticed one very recent, one being a NAS UPS configuration. There have been numerous reports of various problems with these UPS's and the apcupsd and nut software packages, though most of those seem to go back 5 or 10 years. I am not sure my issue warrants a bug report. ![]() However, I am not sure what impact this might have on virtualbox's USB subsystem. NUT allows me to configure each APC by specifying additional information beyond the VID:PID, such as serial number, so it can distinguish the units. OTOH, since I'm not seeing further disconnects with the same physical arrangement running the nut-server on the host, I think any loose connectors is probably beside the point.Īnother factoid that may be relevant is that both are APC units with the same USB VID:PID pair. I just thought it might be useful to include here. I did find, at one point (while nut-server was running in the guest) that by applying a little pressure to the clip end of the cable at the back of the UPS, connectivity might resume. That unit is physically connected to the linux host via an unusual cable, one end being USB A connector and the other resembling a standard ethernet connector. A recent power outage proved that both units function correctly. The other unit, an APC es650, is only a few years old. Note that the one unit, an APC xs1300 is probably about 15 years old now. I am not experiencing any instability with the host, guest, or virtualbox in general. Since these are older units, I am guessing they do not require USB 3, so I've only enabled USB 2 for the guest. I have also updated all packages on both to the latest from the devuan repos. The host and guest are both devuan chimaera, running virtualbox 6.1.30. I am suspicious that this may have something to do with the particular devices being passed-through to the guest. It has been at least 6 hours since I started nut on the vbox host and I have not experienced a loss in communications. I am now running the exact same 2 units on the linux host, using the exact same nut configuration. And, of course, I finally resorted - a couple of times, I am ashamed to admit - to rebooting the whole box, something not ordinarily required or even desired with unixy systems. even if I had known exactly how to do this, there were reams of packets, far more than what I usually observe even when looking at a busy vnet. Either way, I did notice that USB is extremely noisy. I even tried running the problem down using wireshark, but either that software does not have full support for USB, or my own wireshark skills are lacking. I checked system logs on both the host and guest frequently and observed nothing unusual, other than disconnect messages indicating I had unchecked the USB devices in the VM device menu. I found that by restarting nut-server, I could get connectivity immediately again. Other times, the 2nd unit would also lose connectivity but not as frequently. Using virtualbox's handy USB passthrough, I would typically get 45 mins or an hour or so of runtime until there was a loss of connectivity with one of the units, but the longevity varied widely sometimes I had to restart the VM from cold boot. There are reasons I'd like to be able to do this, but that matter is actually aside from the problem. I was trying to run 2 UPS units with nut (and previously, apcupsd) within a vbox VM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |