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:
review OS info in the win7-32/64 cat file of virtio-win-1.6.5-4.el6_4,find that the OS info is win2k8x86/x64 instead of win7x86/x64.

Version-Release number of selected component (if applicable):
virtio-win-1.6.5-4.el6_4

How reproducible:
100%

Steps to Reproduce:
1.boot win7-32/64 guest with -cdrom /usr/share/virtio-win/virtio-win-1.6.5.iso
2.review OS info in .cat file of win7-32/64 serial

Actual results:
OS info is  win2k8x86/x64 instead of win7x86/x64.

Expected results:
OS info should be win7x86/x64.

Additional info:

This should have that fixed:

https://brewweb.devel.redhat.com/buildinfo?buildID=279390

reproduced this issue on virtio-win-1.6.5-4.el6_4
Verified this issue on virtio-win-1.6.5-5.el6_4

steps same as comment #0

Actual Results:
on virtio-win-1.6.5-4.el6_4,OS info of win7-32/64 .cat file is win2k8 server;
on virtio-win-1.6.5-5.el6_4,the OS info of the cat file is right for win7-32/64.

Based on above ,this issue has been fixed already .

Move status to VERIFIED according to comment #4

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.

http://rhn.redhat.com/errata/RHBA-2013-1729.html