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. Rm -f /etc/udev/rules.d/*lesĮcho Log out and log in to see if the issue go fixed.īe sure to have VM VirtualBox Extension Pack installed and at least USB 2.0 (EHCI) Controller enabled at VM's USB settings.Īfter these requirements are met, run the above script with sudo.I was trying to run 2 UPS units with nut (and previously, apcupsd) within a vbox VM. Vboxusers_gid=$(getent group vboxusers | awk -F: '=\"usb_device\", RUN+=\"$vbox_usbnode_path -remove \$major \$minor\""Įcho "$vbox_rules" > /etc/udev/rules.d/les Vbox_usbnode_path=$(find / -name VBoxCreateUSBNode.sh 2> /dev/null | head -n 1)Įcho Warning: VBoxCreateUSBNode.sh file has not been found. The same problem occurred when I had VirtualBox 4.3.30 installed.Īfter numerous searching I've concluded with the help of this wiki to the below script that fixed the problem: #!/bin/bash The VBox.log does not report anything suspicious regarding the USB, and VirtualBox does not throw any error either. The USB mouse I have is working in both the host and the guest, but that's probably a device that is treated differently. Since no USB devices are listed there I assume the problem is with the host, not with the guest. I've tried different options as USB controller, even tried to attach theĭevices to different USB ports (2.0 instead of 3.0), but that didn't changeĪnything. If I select the VM, then Settings -> USB and I try to add a filter, a tooltip is displayed: However, when running VirtualBox, no USB device is actually detected ( Enable USB Controller is obviously checked). they are in the list outputted by the lsusb command. I've been trying with a USB flash drive and a Garmin sports watch: when connected to the host, they are both recognised by the system, i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |