Bugs item #2971166, was opened at 2010-03-16 05:32 Message generated for change (Comment added) made by jimatjtan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2971166&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: libkvm Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Peter Brooks (theneb) Assigned to: Nobody/Anonymous (nobody) Summary: usb passthrough fails with RDP Initial Comment: Base OS: Debian Etch 2.6.26-2-amd64 Processor: Intel(R) Xeon(TM) CPU 3.00GHz QEMU 0.9.1 Virt-manager 0.6.0 kvm 72+dfsg-5 Guest OS: Windows Server 2008 standard I've enabled USB pass through using virsh and editing the xml file for my vhost to add the usb device attached. When using the guest OS from virt-manager, the USB device works perfectly. When using the guest OS from RDP then the USB device fails to work. The device when failing to work it does still appear in the device manager. The device itself is a Safenet Sentinel dongle, sadly used for software copy protection. It is used with a Galaxy RS security system, the software fails to start without the dongle functioning perfectly. ---------------------------------------------------------------------- Comment By: Jim Paris (jimatjtan) Date: 2010-03-16 15:39 Message: Many Windows security systems specifically detect when a remote desktop session is attached, and refuse to allow access. Indeed, according to the Safenet Sentinel End User Guide at http://www2.safenet-inc.com/support/files/SafeNet_Sentinel_EndUser_Guide.pdf: "Please Note that if you attempt to run a Sentinel Key protected application in standalone mode via a remote client (Terminal Server, VNC, WinXP remote client...), the software protected with Sentinel keys will not allow this for security reasons if application is protected in Standalone mode. You will either need to run the software while directly logged into the machine, or need to get in touch with you software vendor for software protected in Network mode." So this is definitely not a libvirt or qemu or kvm problem. You'll have to bring this up with your DRM provider. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2971166&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
