Hide Forgot
Description of problem: Build 71driver viostor.sys has not been digitally signed after running "sigverif" in win2012. Version-Release number of selected component (if applicable): kernel-2.6.32-419.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.404.el6.x86_64 virtio-win-prewhql-0.1.70 spice-server-0.12.4-3.el6.x86_64 seabios-0.6.1.2-28.el6.x86_64 vgabios-0.6b-3.7.el6.noarch How reproducible: 100% Steps to Reproduce: 1.Boot guest with CLI: /usr/libexec/qemu-kvm \ -M rhel6.5.0 \ -m 2G \ -smp 2,cores=2 \ -cpu 'SandyBridge' \ -usb \ -device usb-tablet \ -enable-kvm \ -drive file=win2012.qcow2,format=qcow2,if=none,id=drive-blk,cache=none,rerror=stop,werror=stop,serial=disk0 \ -device virtio-blk-pci,drive=drive-blk,id=blk0-0-0-0,bootindex=1 \ -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no \ -device e1000,netdev=hostnet0,mac=fe:23:40:21:22:31,id=net0 \ -uuid 8ff96365-d565-4304-8534-f1282aa90267 \ -no-kvm-pit-reinjection \ -chardev socket,id=111a,path=/tmp/monitor-win2012-block,server,nowait \ -mon chardev=111a,mode=readline \ -name win2012-block-71 \ -vnc :2 \ -vga cirrus \ -drive file=disk1.qcow2,format=qcow2,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop \ -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 \ -rtc base=localtime,clock=host,driftfix=slew \ -global PIIX4_PM.disable_s3=0 \ -global PIIX4_PM.disable_s4=0 \ -monitor stdio 2.running "sigverif" in guest cmd 3. Actual results: Show "viostor.sys" has not been digitally signed Expected results: the viostor driver is digitally signed, a dialog box appears indicating “Your Files Have Been Scanned And Verified As Digitally Signed. Additional info:
I suppose it should work fine with build 74. Can we close it?
(In reply to Vadim Rozenfeld from comment #3) > I suppose it should work fine with build 74. > Can we close it? win2012 still hit the same issue with build74,both vioscsi and viostor are not digitally signed.
(In reply to lijin from comment #4) > (In reply to Vadim Rozenfeld from comment #3) > > I suppose it should work fine with build 74. > > Can we close it? > > win2012 still hit the same issue with build74,both vioscsi and viostor are > not digitally signed. Please post sigverif.txt file.
Created attachment 840690 [details] sigverif.txt Hi Vadim, Attachment is the sigverif.txt file,anything else please let me know.
(In reply to lijin from comment #6) > Created attachment 840690 [details] > sigverif.txt > > Hi Vadim, > > Attachment is the sigverif.txt file,anything else please let me know. Thanks, let's wait when drivers from build74 will be signed by MS Windows Hardware Compatibility Publisher and then recheck it again. (Hopefully in the first part of January 2014) Best regards, Vadim
(In reply to Vadim Rozenfeld from comment #7) > (In reply to lijin from comment #6) > > Created attachment 840690 [details] > > sigverif.txt > > > > Hi Vadim, > > > > Attachment is the sigverif.txt file,anything else please let me know. > > Thanks, > let's wait when drivers from build74 will be signed by MS Windows Hardware > Compatibility Publisher and then recheck it again. (Hopefully in the first > part of January 2014) > > Best regards, > Vadim Do you mean we only need to run sigverif test cases for virtio-win whql'ed builds ?
(In reply to Mike Cao from comment #11) > (In reply to Vadim Rozenfeld from comment #7) > > (In reply to lijin from comment #6) > > > Created attachment 840690 [details] > > > sigverif.txt > > > > > > Hi Vadim, > > > > > > Attachment is the sigverif.txt file,anything else please let me know. > > > > Thanks, > > let's wait when drivers from build74 will be signed by MS Windows Hardware > > Compatibility Publisher and then recheck it again. (Hopefully in the first > > part of January 2014) > > > > Best regards, > > Vadim > > Do you mean we only need to run sigverif test cases for virtio-win whql'ed > builds ? Right. sigverif is a tool for searching system files not digitally signed by Microsoft. Best regards, Vadim.