WSL vs. Hyper-V vs. AnyOtherHost usage..

[tbone2k-git]

Hello everyone! o)

Hope you don't mind a small question, I don't fully understand the description, it states:
"Windows software for sharing locally connected USB devices to other machines, including Hyper-V guests and WSL 2"

I don't get why "Hyper-V guests" are mentioned in the description. Is connecting to the "usbipd-win" server any different from a Hyper-V guest compared to trying to connect from another real physical machine or any other virtual machine on the network (with usbip e.g.)?

Example:
I run "Debian v12" in the local Hyper-V instance and have a USB device attached to the local physical computer.
Is it wrong to use the generic "usbip" package in the Hyper-V Debian to connect to the USB device on the host machine?
Is there a better way for local Hyper-V guests? I guess there is not, but I need to make sure! o)

Thank you for taking the time! o)

[dorssel]

No, it isn't different. It's just that hyper-V doesn't have a native USB forwarding function, and this was the first use case. I wanted to be explicit about the fact that this could be used. WSL support was added later.

Is it wrong to use the generic "usbip" package in the Hyper-V Debian to connect to the USB device on the host machine?

No, that exactly what I originally created the package for! Works fine!

[tbone2k-git]

Hello Mr. dorssel.. o)

Ok, thank you for clarifying! o) I also used "usbipd-win" for exactly that in the first place, bridging an USB device into a Hyper-V Linux virtual machine. I had to ask, because the Hyper-V hypervisor is somehow involved when running WSL (even though it is not obvious / visible), so I wasn't sure if what I did, was what you had in mind. If the Hyper-V guest (Linuc VM) is to be treated as a regular Linux machine and the regular "usbip" package is to be used, I did the right thing.

Thank you for doing this and helping out!
It was a fun experience! o)

Kinda offtopic:
Your program worked quite well so far! I was in the need to read a mini-sd card from a raspberry pi, so I bridged the USB card reader into the virtual machine and was able to work on it inside the Linux VM. The sd-card had a faulty filesystem and data on it was lost, but I learned a new trick! o) Your software will be used more often, now that I know it exists. o)

The client side software on Linux was kind of easy to use as well, this is not your part, but you and the other people involved did a great job! It's always nice when server / client things match up, in this case it worked even with two different operating systems, very awesome! o)

I also tried to bridge an additional USB mouse (HID), I had the hope it would allow me to play older 3D games like QuakeIII over RDP (which does not work because RDP sends absolute mouse cursor positions or something). This is total nonsense test of course! o) The mouse was in the list of USB devices on the Linux VM, but it did not help while inside the RDP session. But, the mouse worked on the root console (the Hyper-V native machine video output / screen)! It was a fun test, because I had 2 mouse cursors during this. Both could move independently. The regular one in Windows OS and the one from the second USB mouse showed and worked for the Hyper-V console screen.

I disconnected the second mouse rather soon, because I don't seem to be capable of controlling two mice at the same time! o)
Who can? o)

Thanks again and take care! o)