Created attachment 1235576 [details] failed logs Description of problem: Many jobs failed on win2012R2/ws2016 when running core mode w/o GUI Version-Release number of selected component (if applicable): virtio-win-prewhql-129 qemu-kvm-rhev-2.6.0-29.el7.x86_64 kernel-3.10.0-537.el7.x86_64 seabios-1.9.0-5.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot w/ vioinput device /usr/libexec/qemu-kvm -name 126INP2012R2LYD -enable-kvm -m 6G -smp 8 -uuid 20a97ea6-a417-4bac-944d-78e6518ff478 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/126INP2012R2LYD,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -drive file=126INP2012R2LYD,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_server_2012_r2_x64_dvd_2707946.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=126INP2012R2LYD.vfd,if=floppy,id=drive-fdc0-0-0,format=raw,cache=none -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:52:56:39:e4:f3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:2 -vga cirrus -M pc -device virtio-tablet-pci,id=tablet0,serial=virtio-tablet 2.submit jobs 3. Actual results: Failed Error 12/26/2016 3:06:49.775 AM WDTF_TEST : Found a device that has a non-zero problem code or is phantom. Logging device info. "WDTF_TEST : Status: Status Flags=0x1806400 (DN_HAS_PROBLEM DN_DISABLEABLE DN_REMOVABLE DN_NT_ENUMERATOR DN_NT_DRIVER) Problem Code=27 (CM_PROB_DRIVER_FAILED_LOAD)" Expected results: Pass Additional info: 1 these jobs can pass when it boot with a GUI guest on win2012R2/2016. 2 hit the same issue using build 126 3 Could you help to check if virtio-input device could be supported w/o GUI?
Here's a forum thread about the issue and according to the person who hit this Microsoft acknowledged it to be a problem with the test requirements: https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/7152107d-46ef-4aa1-9539-23d375b90a45/how-to-pass-whql-hlk-tests-for-kmdf-hid-minidriver-on-server-core-2016 The problem is that mshidkmdf.sys does not come in-box with Server Core installations, contrary to the documentation which says that it's present on Windows 7 and up. We *could* build and ship our own mshidkmdf.sys. That would get us not only Server Core, but also Vista and XP support. The cost/benefit is questionable though. Unless there's a strong reason for supporting the input driver on Core/no-GUI Windows, I suggest that we get errata for this.
In order to open ticket with MS, please provide logs for Windows Server 2016 as well
Created attachment 1239693 [details] 129-vioinput-ws2016-hckxlog please refer to attachment Thanks Yu Wang
Build 132 no longer depends on mshidkmdf.sys so the driver will work on Windows Core w/o GUI now.
Hi, Verify this bug w/ build 132 , steps as comment#0, all the vioinput jobs passed on win2012R2 and ws2016 w/o GUI. So this bug has been fixed. Thanks for your great support! Thanks Yu Wang
from QE's testing result,all windows platforms with&without GUI need viohidkmdf.sys file,is this the expected result?
(In reply to lijin from comment #11) > from QE's testing result,all windows platforms with&without GUI need > viohidkmdf.sys file,is this the expected result? Yes, this is expected. We can't really provide two separate .inf files, one which references mshidkmdf.sys and another with viohidkmdf.sys, based on whether the OS has GUI or not. And even if we could, it would be simpler to use viohidkmdf.sys everywhere. Thanks!
(In reply to Ladi Prosek from comment #12) > (In reply to lijin from comment #11) > > from QE's testing result,all windows platforms with&without GUI need > > viohidkmdf.sys file,is this the expected result? > > Yes, this is expected. We can't really provide two separate .inf files, one > which references mshidkmdf.sys and another with viohidkmdf.sys, based on > whether the OS has GUI or not. And even if we could, it would be simpler to > use viohidkmdf.sys everywhere. Thanks! Thanks for the explanation. change status to verified according to comment10 and comment#12
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2341