Bug 1395696

Summary: Handle UsbDk failures without hanging
Product: Red Hat Enterprise Virtualization Manager Reporter: Victor Toso <victortoso>
Component: mingw-virt-viewerAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED ERRATA QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: astepano, bsanford, cfergeau, dblechte, dfleytma, eheftman, gklein, lsurette, rbalakri, rh-spice-bugs, srevivo, uril, ykaul
Target Milestone: ovirt-4.1.0-beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mingw-spice-gtk-0.31-5.el7ev mingw-virt-viewer-2.0-12.el7ev spice-client-msi-4.1-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Victor Toso 2016-11-16 13:16:51 UTC
Description of problem:

This bug is a clone of upstream bug [0].

[0] https://bugs.freedesktop.org/show_bug.cgi?id=98686

Using UsbDk without "Disable Driver Signature Enforcement" option in Windows boot, spice-gtk hang on startup.

How reproducible:

100%

Expected results:

If UsbDk is unavailabe, we can't redirect usb devices but we should be able to proper connect to the remote VM.

Additional info:

This is already fixed upstream.

Following patches fixes the issue and improve handling the errors:

82ed594a0143370630d6d71ac484d66475cdb96c
eba83a7056d4213b60466f692a03e515115b0826
d3c29773b1654085ef6653643b1f790985b8454b
d6275ccfc43993365b601aaab6238e7a447c90d8
bd530d0feeedff39fbf8cafedd011a7abc53ac01
95031c6cfce51b0cff58a476fe462d7a99e707b3

Comment 3 Bill Sanford 2017-02-21 16:46:51 UTC
I have seen this. I have installed the 4.1-12 build and when I install the virt-viewer and USBdk for Win7, upon reboot after I install the USBdk, I have NO mouse or keyboard and can do nothing but reinstall Win7.

Comment 4 Victor Toso 2017-02-22 09:00:08 UTC
(In reply to Bill Sanford from comment #3)
> I have seen this. I have installed the 4.1-12 build and when I install the
> virt-viewer and USBdk for Win7, upon reboot after I install the USBdk, I
> have NO mouse or keyboard and can do nothing but reinstall Win7.

You can boot windows with driver signature enforcement disabled and uninstall USBDk.

Are you saying this failedQA? If so, please provide the client logs and the versions of each component.

Comment 5 Bill Sanford 2017-02-22 13:27:58 UTC
Victor, when I reboot, I have NO mouse and NO keyboard on a Windows 7 client. I can't even log into the machine.

Windows 7x64
RHEL 7.3z
rhv-4.1.0-12
virt-viewer 2.0-208
spice-client-msi-x64-4.1-4.el7ev.noarch

I have no logs, yet. I want to finish a testing run and will install the USBdk and try to boot to safe mode and see if I can get in from there.

Comment 6 Victor Toso 2017-02-22 13:35:20 UTC
(In reply to Bill Sanford from comment #5)
> Victor, when I reboot, I have NO mouse and NO keyboard on a Windows 7
> client. I can't even log into the machine.

Driver signature enforcement can be disabled before windows boots, you should have mouse and keyboard them. In order to do so, use the F8 option to get to Advance Boot Options then select Disable Driver Signature Enforcement

> Windows 7x64
> RHEL 7.3z
> rhv-4.1.0-12
> virt-viewer 2.0-208
> spice-client-msi-x64-4.1-4.el7ev.noarch
> 
> I have no logs, yet. I want to finish a testing run and will install the
> USBdk and try to boot to safe mode and see if I can get in from there.

This bug is about not being able to use remote-viewer while having the Disable Driver Signature Enforcement enabled, so you should have mouse and keyboard in the client in order to reproduce this bug.

Your issue is related to UsbDK driver signature and windows, not with remote-viewer.

Comment 7 Bill Sanford 2017-02-22 13:38:15 UTC
I actually just tested this. When I press F8 to start in Safe Mode, I can't since the PC opens the Windows Error Recovery screen where I can Launch Startup Repair or Start Windows Normally.

I just switched the component.

Comment 8 Victor Toso 2017-02-22 13:43:38 UTC
(In reply to Bill Sanford from comment #7)
> I actually just tested this. When I press F8 to start in Safe Mode, I can't
> since the PC opens the Windows Error Recovery screen where I can Launch
> Startup Repair or Start Windows Normally.
> 
> I just switched the component.

This one is a client side bug.

Comment 9 Emma Heftman 2017-03-14 12:55:36 UTC
Hi. Could you please set the requires_doc_text flag to - if no doc text is required, or ? if text should appear in the advisory. Then add the text to Doc Text field. Thanks.

Comment 10 Bill Sanford 2017-03-17 16:00:17 UTC
I tested this also with a Windows 10 client. 

I type the following at an elevated Command prompt:

bcdedit.exe /set nointegritychecks on and rebooted.