Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
I have checked the Windows version of virt-viewer 8.0 with both oVirt and virt-manager (after installing USBDk).
In both versions you can see the USB devices, but with version 8.0 it gives a random minus error while in version 7.0 it works.
Thanks
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
@victor, do your need more info or is the log from Hetz adequate?
I've tried to use USB redirection on both Win7 and Win10 with and without usbDK installed.
Works find with remote viewer 7.
Yuri Benditovich took a look at my log and had the following comments, I don't know if they would be of any help, but here they are:
"I see the virt-viewer 8.0 uses only WinUSB as it includes libusb 1.0.22 (which uses dynamic configuration of backend with WinUSB as default) and spice-gtk 0.35 (which does not configure libusb to use UsbDk). I suggest to try virt-viewer 7.0 instead, then libusb will work with UsbD"
and
"I see in your case libusb DLL uses WinUSB (I think it is typically available out of the box). And it looks like (from the logs) there is some missing API in WinUSB path that makes the redirection to fail. "
Hi, sorry huge delay. Easy to reproduce, on nested client (Win 10 on Fedora 31) I got error -5 and on bare metal Windows 10 I got error -12, this with virt-viewer 8.0. virt-viewer 7.0 worked fine.
Let's see if we can get this fixed by soon and get a new release of virt-viewer out.