Description of problem: A subset of virtio-win binaries doesn't have their symbol files persisted anywhere. Not even in the raw prewhql build. They are lost forever after a build is completed and the build machine recycled. netkvmco.pdb viorngci.pdb viorngum.pdb Version-Release number of selected component (if applicable): any recent version of virtio-win
Fixed in commits: https://github.com/virtio-win/kvm-guest-drivers-windows/commit/c9a3abccc854a8e1c7223b3ee6d1ebff0a6940cc https://github.com/virtio-win/kvm-guest-drivers-windows/commit/9286da9e4a98712ca64aa3040ee204f8caf9ad92 I'll update virtio-win packaging scripts once a raw build with these fixes is available. Note that the build validator output that uncovered this will disappear after two more builds (when the build used for comparison - "previous" build - has the fixes).
Check in build141 and build142,netkvmco.pdb,viorngci.pdb,viorngum.pdb are available in Win10,Win7,Win8,Win8.1 and Wlh folders. Wnet,Wxp folders do not have these files,considering we freezed the support of winxp and win2003,this should be ok. So change status to verified. I will clone this bug to distribution sub-component as it affects virtio-win packaging as well
(In reply to lijin from comment #4) > Check in build141 and build142,netkvmco.pdb,viorngci.pdb,viorngum.pdb are > available in Win10,Win7,Win8,Win8.1 and Wlh folders. > Wnet,Wxp folders do not have these files,considering we freezed the support > of winxp and win2003,this should be ok. There's no viorng driver for Wnet and Wxp, hence no viorng*.pdb. NDIS5 netkvm does not have the userspace dlls, hence no netkvmco.pdb. > So change status to verified. > > > I will clone this bug to distribution sub-component as it affects virtio-win > packaging as well Thank you!
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-2018:0657