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.

Created attachment 567464 [details]
ISOandFloopy_contrast

Description of problem:
 As we all know,there will be two files for customer after we get signature from MS,one is VFD another is ISO.But the folder's name style isn't consistent between the two files.It is necessary for us to enhance User Experience while they are using our product,so we had better resolve the issue for the future packages.
 Many thanks.

Version-Release number of selected component (if applicable):
virtio-win-1.4.0-1.el6.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1.installed on host and check the package's path
2.boot a guest with CDROM and Floppy
3.login guest and check CDROM and Floppy
  
Actual results:
The folder named by OS's name in Floppy 
Win7
Win2008
Win2003
WinXP

The folders in ISO 
2k3
2k8
w7
xp

Expected results:

QE propose these folder's name have a same style.
Eg.the folders in ISO should be 

Win2003
Win2008
Win7
Winxp 

Additional info:

Closing as this cannot be resolved.
There are Gaps between MSFT VFD standard and our PM requirements (readability of file names).
The installers for ISO and VFD require a different structure.
Thanks, Ronen.