RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1012429 - [virtio-win][viostor]Build 71driver viostor.sys has not been digitally signed in win2012
Summary: [virtio-win][viostor]Build 71driver viostor.sys has not been digitally signed...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-26 13:01 UTC by guo jiang
Modified: 2015-03-18 09:09 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-07 21:28:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
sigverif.txt (13.10 KB, text/plain)
2013-12-23 06:32 UTC, lijin 		no flags Details
View All

Description guo jiang 2013-09-26 13:01:04 UTC 
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:
Comment 3 Vadim Rozenfeld 2013-11-30 08:49:32 UTC 
I suppose it should work fine with build 74.
Can we close it?
Comment 4 lijin 2013-12-23 06:08:29 UTC 
(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.
Comment 5 Vadim Rozenfeld 2013-12-23 06:23:21 UTC 
(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.
Comment 6 lijin 2013-12-23 06:32:30 UTC 
Created attachment 840690 [details]
sigverif.txt

Hi Vadim,
    
    Attachment is the sigverif.txt file,anything else please let me know.
Comment 7 Vadim Rozenfeld 2013-12-23 06:58:20 UTC 
(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
Comment 11 Mike Cao 2014-06-18 06:18:31 UTC 
(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 ?
Comment 12 Vadim Rozenfeld 2014-06-18 10:07:50 UTC 
(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.
Note You need to log in before you can comment on or make changes to this bug.