VirtualHere makes it trivially easy to test this concept. In the picture below you see the client end which is a Manjaro XFCE desktop computer. At the server end is a Raspberry Pi4B that is exporting a HP T150 usb zeroclient. Manjaro treats the remote HP T150 exactly as it would treat it if it were plugged in locally.

My program still finds it, in this case the remote display adapter, rather than the internal usb hub parent of the child display adapter. This will cause Manjaro to add the remote display as either a mirror of the current session or an extension of its desktop.

copyleft, Lawrence E. Boothby (, 2019
under current GPL license

searching for usb DisplayLink device(s), if none, just exit

searching for internal hub of DisplayLink device
searching for first usb hub above, if exists
none found

Press any key to exit

VirtualHere generously donate a free license to test my unusual use case. While the trial version, which limits the usb server to one device worked perfectly to cause Manjaro to create a new login screen on the virtual usb zeroclient, the licensed version does not seem to be preserving the usb hierarchy of parent hub and child devices, something that was never intended for the use cases it was designed for. It also had trouble when there were multiple identical usb devices such as both a usb Logitech unifying receiver on the server and on the client usb zeroclient. This resulted in my losing keyboard and mouse control of the server with both Logitech unifying receivers being attached to the virtual usb zeroclient. VirtualHere has remarkably fast tech support! Adding “AutoAttachToKernel=1” to its config.ini (server end) causes the server to recapture the usb input devices when the usbclient end exits. This makes it useful for a single remote display adapter or usb zeroclient, but without preservation of the usb hub hierarchy, you get an extension of the remote desktop display instead of automatic creation of a new named seat. That can be useful if the real and the virtual display are mirrored or the virtual display is the primary display at least.

At the client end, configuration settings persist across boots and are saved in vhiu.ini .

This is peculiar to my use case and not the fault of VirtuallyHere who had not designed their software to be used this way. I am likely to encounter the same issues of virtual hub hierarchy with other usb server software and/ or hardware when trying to attach multiple identical usb zeroclients remotely. USBIP page.