Issue with USB devices in Spice client being grayed out

Latest response

I'm trying to assist a customer with their RHEV deployment.

They have RHEV 3.0 on RHEL 6.3. In the hypervisor they have 3 VMs configured with Windows 7 32bit.

They can access the VMs through the UserPortal via the Spice client without issue. Keyboard and sound work great.


The problem is USB devices are grayed out when right-clicking on the top Spice frame. The USB devices are all listed, but you cannot click on them to make them available in the VM.


The usbfilter.txt file has the -1,-1,-1,-1,1 appened to the end of it in the /usr/share/rhevm/rhevm.ear/userportal.war/org.ovirt.engine.ui.userportal.UserPortal/consoles/spice directory.

The USB policy is enabled on each VM

Each VM has USB Auto-share checked.

Port 32023 is open and according to their network admin, traffic is available to go across that port.


I'm stuck on where to go for this. Where else can I check for logging to see what may be preventing the USB devices from being available in the VM. I've not had much luck searching for this in Google or even here.





Looks like you're not having much luck finding an answer from the community on this one either. I'll see if I can help track down an answer for you.



Are you using the legacy or native USB support for this VM?

I am the customer in this case.


How do I check for legacy/native USB in the VM?


We have installed RHEV-USB-Client-4_7_8 on the client and RHEV-toolsSetup_3.0_34 on the VM guest.

edit the desktop VM, look at the Console tab, the setting should be there

I only have Enable/Disable.


We are running RHEV 3.0. I believe the new Legacy/Native settings are in beta 3.1?

You're right, sorry, was looking at the wrong setup


I think this is more of a support case and not a discussion, have you opened a case yet?

Yes, I have a case open. I was hoping that someone else might have run into similar issues.

Hi! Have you figured out - what was the issue in your case? 

I have similar situation with 3.1.

Hi Dmitry,

We have a fairly complex setup... 28 remote locations connected via MPLS to a central datacenter (including vpns, vlans, etc.). If all was local, we wouldn't have had any issues.

We are currently finding that some of our newer camera/video devices connect okay initially, but are then deactivated. Performance hasn't quite been adequate for us, but suspect it may be more application-level than spice. We were hoping to keep the VMs in the central datacenter, but will likely put a host locally at the remote site in the future.

We had to make sure to set one of the vlan'd Logical Networks in the Datacenter to be the Display Network. If this wasn't set to the correct Logical Network/vlan, we would get black screen when logging in and no connection to the VM. Some changes also had to be made to route between some vlans, the proper firewall port had to be opened, and exceptions added to the Windows firewalls.

You might give a try with the Windows firewall turned off to try to eliminate that as a possibility.