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.

Description of problem:
[RFE]Add virtio-vsock drivers to virtio-win

Version-Release number of selected component (if applicable):
virtio-win-1.9.25-2.el9_0.noarch

How reproducible:
100%

Steps to Reproduce:
1. Check the drivers in virtio-win, there is no virtio-vsock drivers

# ls /usr/share/virtio-win/drivers/by-driver/
Balloon  pvpanic    qemupciserial  qxldod  viofs     vioinput  vioscsi    viostor
NetKVM   qemufwcfg  qxl            sriov   viogpudo  viorng    vioserial


Expected results:
As above description

Additional info:
virt-v2v supports adding virtio-vsock to linux guests now, pls refer to bug2070186

Quick note. 
To have this job done, the virtio-vsock driver needs to 
be WHQL and functional tested and Microsoft WHQL signed.

This is only a nice to have, it is not needed for virt-v2v.

qa_ack- as we don't have such a plan to whql it.

Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.