Bug 1502035
| Summary: | USBDK v1.0.15 is having various failures at customer site with Windows 10 clients. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Frank DeLorey <fdelorey> | ||||
| Component: | spice-usbdk-win | Assignee: | Default Assignee for SPICE Bugs <rh-spice-bugs> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SPICE QE bug list <spice-qe-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | --- | CC: | bdoran, bsanford, dblechte, djasa, fdelorey, lsurette, michal.skrivanek, mtessun, rduda, rh-spice-bugs, rmcswain, tmichett, tpelka, uril, victortoso, ybendito | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | spice-usbdk-win-1.0-19 (RHV-4.2) | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-01-28 12:23:09 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1444605 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Created attachment 1340130 [details]
Check list + info to collect
UsbDk v1.0.15 has known problems with Win 10. So in this BZ we'll focus only on UsbDk v1.0.19 (even it is not officially supported). I've verified UsbDk_1.0.19_x64.msi on 2 systems with UEFI secure boot and Windows 10 1703 and did not reproduce any failure in UsbDk functionality over restarts,shutdowns,hibernations etc. So, we are looking for root cause on specific systems under test. I believe this is not clean Windows install, but the image that was prepared by org's IT. First question is whether the same effect happens on clean Windows image. For the case when the problem happens I've prepared a check list (attached), please fill it and attach the collected information. If there are specific devices that affected by UsbDk install/uninstall flow, this is separate issue and should be filed/solved independently of UsbDk functionality (often such devices present problem during sharing also). If possible, please disable/unplug these devices when working on this specific issue. When filing device-specific bugs please refer exact model/name of the device; if needed we will provide recording instruction to collect logs for these failures. I am not sure we need a hotfix. If we know that the currently shipping version, 1.0.15 does not work well with a Windows 10 client then we should not have listed Windows 10 as a supported client or at least had a note about the usbdk issues with Windows 10. So in my opinion we should open a doc bug and I will create a KCS to document the current problems and just wait for the real GA fix. My question is do we have anything listing the problems with usbdk v1.0.15 and Windows 10? Frank So that makes sense. I didn't know that the problems started with a new release for Windows 10 from MS. As a plan we would give them a new version of 1.0.19 that can run on rhev 4.1? I am guessing that this would not be signed? If this is the case I can start the hotfix process. Frank Frank/David - In terms of a HotFix and Windows 10 we would most likely need some type of fix that would work and be considered as "supported". Currently, we had several/most machines on 1607 version of Windows, but I believe they will be having the 1703 version on machines soon. I can get exact details of the Windows 10 versions on Monday, but I can confirm that the lowest version of Windows 10 is 1607. In terms of functionality, we need to be able to use Windows 10 clients to connect to the VMs and re-direct USB devices. Currently that doesn't work with USBDk 1.0.15 but we are having some successes (still have problems) with USBDk 1.0.19. The plan is to next week take a checklist for verification and use a brand new (untouched) machine for testing and getting results. Travis (In reply to ybendito from comment #2) > UsbDk v1.0.15 has known problems with Win 10. > > So in this BZ we'll focus only on UsbDk v1.0.19 (even it is not officially > supported). > > I've verified UsbDk_1.0.19_x64.msi on 2 systems with UEFI secure boot and > Windows 10 1703 and did not reproduce any failure in UsbDk functionality > over restarts,shutdowns,hibernations etc. So, we are looking for root cause > on specific systems under test. I believe this is not clean Windows install, > but the image that was prepared by org's IT. > > First question is whether the same effect happens on clean Windows image. > > For the case when the problem happens I've prepared a check list (attached), > please fill it and attach the collected information. > > If there are specific devices that affected by UsbDk install/uninstall flow, > this is separate issue and should be filed/solved independently of UsbDk > functionality (often such devices present problem during sharing also). If > possible, please disable/unplug these devices when working on this specific > issue. > When filing device-specific bugs please refer exact model/name of the > device; if needed we will provide recording instruction to collect logs for > these failures. ybendito - I can verify we have Windows 10 1607 installed on the machines we are having issues. I've been able to collect the data as requested for the attachment, but it is quite a large amount of data. I would like to provide targeted *scrubbed* data for use with this bug. Unfortunately, based on customer policies, we can only provide limited amounts of scrubbed data. Thanks, Travis (In reply to Travis Michette from comment #12) > I can verify we have Windows 10 1607 installed on the machines we are having > issues. I've been able to collect the data as requested for the attachment, > but it is quite a large amount of data. I would like to provide targeted > *scrubbed* data for use with this bug. Unfortunately, based on customer > policies, we can only provide limited amounts of scrubbed data. > > > Thanks, > > Travis Please attach max of what you can provide. We will try to work with this. setting needinfo for Comment 13 oVirt 4.2.0 has been released on Dec 20th 2017. Please consider re-targeting this bug to next milestone This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. sync2jira sync2jira |
Description of problem: Customer reporting that when using a Windows 10 client with the v1.0.15 USBDK that detaching devices is not working correctly. Version-Release number of selected component (if applicable): RHEV 4.1 USBDK v1.0.15 (upstream) USBDK 1.0.19 How reproducible: Very Steps to Reproduce: 1.Install the USBDK from the RHV 4.1 downloads section 2.Attach a USB device from a Windows 10 client to any VM 3.Detach the USB device Actual results: The USBDK software will not see/release USB devices properly from a Windows 10 client. Additionally, some versions of the USBDK software must be re-installed if the system gets rebooted. When attempting to return the USB device to the physical machine, the drivers are totally gone and it will no longer work. Expected results: USB Device connected to physical computer -> can be redirected to VM USB Device can be deselected for USBRedirect from the VM and it should return the USB device to the physical computer. Additional info: 1. Did customer use usbdk v15 on Win 7 and win 10, and it worked ? 2. Does it work on Win 7 now, but stopped working on win 10? I wasn't involved with this on Windows 7, but I understand whatever was used worked. We have yet to find a working combination of software that works on Windows 10. The version from the REHV portal v15 throws a driver signature error. Interestingly enough, it even throws this error in disable driver signature enforcement mode. If installed in normal mode it will kill the usb bus and someone has to RDP into the machine and clean up the mess in devmgmt.msc. If installed in disable driver signature enforcement mode, it seems to at least load the kernel driver despite the error it throws and will continue to function while in disable driver signature enforcement mode. I've only tested that mode once, as getting into disable driver signature enforcement mode is a pain. In any case, upon reboot the kernel driver fails to load and attempting to manually start it results in a driver signature error. See below: PS system32>sc.exe queryex usbdk SERVICE_NAME: usbdk TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 1077 (0x435) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 PID : 0 FLAGS : PS system32>sc.exe start usbdk [SC] StartService FAILED 577: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a ile that is signed incorrectly or damaged, or that might be malicious software from an unknown source. PS system32> This error was already sent in by Travis. 3. We don't support v19 yet, but customer already downloaded from upstream: What are the exact problems with this version? We downloaded and are using the upstream on systems that require this functionality, because it is the closest to working. Interestingly enough, this version does not throw a driver signature error. Installing it will work. However, after a restart or 2, it will foul up and need reinstalled. See output below: PS system32>sc.exe query usbdk SERVICE_NAME: usbdk TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 1077 (0x435) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 PS system32>sc.exe start usbdk [SC] StartService FAILED 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. PS system32>sc.exe query usbdk SERVICE_NAME: usbdk TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 1058 (0x422) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 PS system32> This is the info on 1058: ERROR_SERVICE_DISABLED 1058 (0x422) The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. When this occurs usbdk seems to require the driver be reinstalled, although there is a command line utility that will do this installed with the usbdk msi that will do this. Some devices will need unplugged and plugged back in after the driver is reinstalled.