Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1018652

Summary: [virtio-win][scsi]Remove win2003 virtio-scsi related code from txtsetup.oem
Product: Red Hat Enterprise Linux 6 Reporter: Mike Cao <bcao>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.5CC: acathrow, bcao, bsarathy, chayang, lijin, michen, pm-rhel, rhod, tlavigne
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virtio-win-1.6.7-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-01 16:31:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike Cao 2013-10-14 05:34:20 UTC
Version-Release number of selected component (if applicable):
virtio-win-1.6.5-5.el6_4

How reproducible:


Steps to Reproduce:
1.As virtio-scsi is not supported for win2k3 . We would like to remove win2k3 scsi related code txtsetup.oem in virtio-win package

to verify this bug , We need to check
1.Whether win2k3 scsi driver is removed from virtio-win-XXX_x86.VFD
2.Whether win2k3 scsi driver is removed from virtio-win-xxx_amd64.VFD

Comment 1 RHEL Program Management 2013-10-18 08:32:29 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 2 Ronen Hod 2013-10-26 07:15:05 UTC
PM, the decision was to remove the support for Win2003 virtio-win-scsi.
Please ack, Ronen.

Comment 3 lijin 2013-11-04 05:36:30 UTC
Reproduced this issue on virtio-win-1.6.5-5.el6_4 version
Verified this issue on virtio-win-1.6.7-2.el6 verion

steps same as comment #0

Actual Results:
on virtio-win-1.6.5-5.el6_4,vioscsi driver is existing in the x86 and amd64 vfd file.
on virtio-win-1.6.7-2.el6,win2k3 scsi driver is removed from virtio-win-1.6.7_x86.VFD and virtio-win-1.6.7_amd64.VFD

Based on above ,this issue has been fixed already .

Comment 4 Mike Cao 2013-11-04 06:09:08 UTC
Move status to verified according to commment #3