"Autoforward" USB-Devices into a headless guest?

[smartysmart34]

Hi all,

I am running under Linux here. The only WIndows I use is on my server (as a headless guest). I only connect to that Windows7 guest via rdp (native windows, not the VBox-vrdp).
Now I bought a Navigation device (TomTom that I want to upgrade (Firmware / Maps). This requires Windows and I know that I can not pass it into the guest via rdp.

My Idea was to configure it in a way that I can plug in the TomTom into a USB port on teh server and then the device would automatically be forwarded into the guest. Then I could rdp into that guest and use the tomtom software with the locally attached device.

Is this possible and how do I ensure that - whenever I attach the device - it will be loaded into the guest?

Thank you in advance,
Martin

[Perryg]

If you have the Extension Pack and have your login name in the vboxusers group on the host. just plug in the device.
When you want to use the device go to the device menu of the guest (rdp will work for this) under USB and select the device you want. If it is going to work that is the easiest way to make it happen.

Remember that if you have to change permissions like adding your login name to vboxusers group a minimum of log off and on is required for permissions to take effect.

[smartysmart34]

Hi Perryg,

maybe I am looking stupid right now but: I have no idea what you mean with "device menu"? Are you talking about the icons on the lower right where mouse-integration is indicated as well? These are not available when connecting via rdesktop to a windows guest using standard windows rdp server.
Are you talking about the top menu items where "install guest additions" is located as well? This menu is not available when connecting to the windows rdp server via rdesktop.

[Perryg]

Yes you are right. Sorry I was going off memory and well that is sometimes not the right way to go.
Let me look at the source of the guests service and see what you can do.

[Perryg]

These are the commands that you can use on the host to control a running guest. So you can attach/detach the USB device from the host CLI.

Code: Select all

VBoxManage controlvm <uuid>|<name>
pause|resume|reset|poweroff|savestate|
acpipowerbutton|acpisleepbutton|
keyboardputscancode <hex> [<hex> ...]|
setlinkstate<1-N> on|off |
nic<1-N> null|nat|bridged|intnet|generic
[<devicename>] |
nictrace<1-N> on|off
nictracefile<1-N> <filename>
nicproperty<1-N> name=[value]
natpf<1-N> [<rulename>],tcp|udp,[<hostip>],
<hostport>,[<guestip>],<guestport>
natpf<1-N> delete <rulename>
guestmemoryballoon <balloonsize in MB>]
gueststatisticsinterval <seconds>]
usbattach <uuid>|<address> |
usbdetach <uuid>|<address> |
vrde on|off |
vrdeport <port> |
vrdeproperty <name=[value]> |
vrdevideochannelquality <percent>
setvideomodehint <xres> <yres> <bpp> [display] |
screenshotpng <file> [display] |
setcredentials <username> <password> <domain>
[--allowlocallogon <yes|no>] |
teleport --host <name> --port <port>
[--maxdowntime <msec>] [--password password]
plugcpu <id>
unplugcpu <id>
cpuexecutioncap <1-100>

With the device attached on the host run VBoxManage list usbhost from CLI to get the information you need.

Here are some interesting commands that you can use inside the guest. Just type the following in a command window to see what they do.
vboxservice -help
vboxcontrol --help

[smartysmart34]

Hi Perryg

Thank you for your investigation. I just used another approach which seems to work OK for now:
I shut down the Windows guest on that server.
I connected to the Linux-Host via ssh with x-forwarding.
su to the user running the guest
startet the VirtualBox-GUI
Went to the USB settings and selected the USB-Device.

Now, whenever i plug that device in it is automatically availabe in the guest. So I plug it in at the host computer (server), and then rdp to the guest from my workstation.
They are not too far away so that is not a major problem. But I'm still thinking about getting a longer usb cable

cheers,
martin

[Perryg]

Until the next boot is my guess. You could try setting a filter but the plugging and unplugging should cause an issue sooner if not later.
Anyway the info is there should you need it in the future.