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 972379 - [virtio-win][serial]cannot upgrade/downgrade the vioser driver on win2k3-32guest.
Summary: [virtio-win][serial]cannot upgrade/downgrade the vioser driver on win2k3-32gu...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Gal Hammer
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-09 03:01 UTC by Min Deng
Modified: 2013-09-16 16:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
It is not possible to downgrade a driver using the Search for the best driver in these locations option because the newer and installed driver will be selected as the "best" driver. If you want to force installation of a particular driver version, use the "Don't search option" and the "Have Disk" button to select the folder of the older driver. This method will allow you to install an older driver on a system that already has a driver installed.
Clone Of:
Environment:
Last Closed: 2013-08-27 09:14:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Min Deng 2013-06-09 03:01:31 UTC 
Description of problem:
Cannot upgrade driver in win2k3-32 guest.
Version-Release number of selected component (if applicable):
Build64
How reproducible:
3 times failed 3 times

Steps to Reproduce:
1.boot up guest and install vioser driver with build 64
2.go to Device Manager -> select serail driver -> right click it -> select upgrade driver,here,I choose build 59 for the target one -> "search for the best driver in these locations" -> folder->Wxp->x86 (59)
3.The driver could not be installed successfully.

Actual results:
Cannot continue the hardware Upgrade wizard pops up

Expected results:
The driver can be upgraded/downgraded

Additional info:
It should be a regression issue.
Comment 3 Gal Hammer 2013-06-09 06:41:25 UTC 
(In reply to dengmin from comment #0)
> Description of problem:
> Cannot upgrade driver in win2k3-32 guest.
> Version-Release number of selected component (if applicable):
> Build64
> How reproducible:
> 3 times failed 3 times
> 
> Steps to Reproduce:
> 1.boot up guest and install vioser driver with build 64
> 2.go to Device Manager -> select serail driver -> right click it -> select
> upgrade driver,here,I choose build 59 for the target one -> "search for the
> best driver in these locations" -> folder->Wxp->x86 (59)

It probably not the problem, but the Wxp->x86 is not the right folder for Windows 2003. You should use the wnet folder.

> 3.The driver could not be installed successfully.

I think that's the expected behavior, no? Windows should tell you that you have a newer driver already installed.
 
> Actual results:
> Cannot continue the hardware Upgrade wizard pops up
> 
> Expected results:
> The driver can be upgraded/downgraded
> 
> Additional info:
> It should be a regression issue.
Comment 5 Min Deng 2013-06-13 02:12:49 UTC 
(In reply to Gal Hammer from comment #3)
> (In reply to dengmin from comment #0)
> > Description of problem:
> > Cannot upgrade driver in win2k3-32 guest.
> > Version-Release number of selected component (if applicable):
> > Build64
> > How reproducible:
> > 3 times failed 3 times
> > 
> > Steps to Reproduce:
> > 1.boot up guest and install vioser driver with build 64
> > 2.go to Device Manager -> select serail driver -> right click it -> select
> > upgrade driver,here,I choose build 59 for the target one -> "search for the
> > best driver in these locations" -> folder->Wxp->x86 (59)
> 
> It probably not the problem, but the Wxp->x86 is not the right folder for
> Windows 2003. You should use the wnet folder.
  Hi Gal,
     I don't think I install driver from wrong folder and please have a look on the following mapping tables.
     https://docspace.corp.redhat.com/docs/DOC-97715 
> > 3.The driver could not be installed successfully.
> 
> I think that's the expected behavior, no? Windows should tell you that you
> have a newer driver already installed.
  I know what's your mean but I really do not see such a dialog at this time.Any issues please let me know.
>  
> > Actual results:
> > Cannot continue the hardware Upgrade wizard pops up
> > 
> > Expected results:
> > The driver can be upgraded/downgraded
> > 
> > Additional info:
> > It should be a regression issue.
Comment 6 Ronen Hod 2013-07-23 13:59:06 UTC 
We would like to close this bug
- A workaround for downgrade should be to uninstall first
- We try to avoid non-urgent 2003 work
Any objection?
Is it really a regression?
Comment 7 Mike Cao 2013-07-24 02:24:05 UTC 
(In reply to Ronen Hod from comment #6)
> We would like to close this bug
> - A workaround for downgrade should be to uninstall first
> - We try to avoid non-urgent 2003 work
> Any objection?
> Is it really a regression?

May not .
Deng Min, Pls try to upgrade driver via following ways :
2.go to Device Manager -> select serail driver -> right click it -> select upgrade driver,here,I choose build 59 for the target one -> "No not search ,I will install the driver manually ---> have disks -> folder->Wxp->x86 (59)
Comment 8 Min Deng 2013-07-24 07:46:43 UTC 
(In reply to Mike Cao from comment #7)
> (In reply to Ronen Hod from comment #6)
> > We would like to close this bug
> > - A workaround for downgrade should be to uninstall first
> > - We try to avoid non-urgent 2003 work
> > Any objection?
> > Is it really a regression?
> 
> May not .
> Deng Min, Pls try to upgrade driver via following ways :
> 2.go to Device Manager -> select serail driver -> right click it -> select
> upgrade driver,here,I choose build 59 for the target one -> "No not search
> ,I will install the driver manually ---> have disks -> folder->Wxp->x86 (59)

Hi All,
   If I did this "Not search and install driver manually -> folder -> Wxp -> x86",it worked well.
   Besides,I could get the same error to comments0 where using "search for the best driver in these locations"...
   Anyway,the search option doesn't work properly for this driver in my opinion,it should be a shortcoming while user want to install driver by this way.
   Any issues please let me know.Thanks.

Best Regards,
Min
Comment 9 Gal Hammer 2013-07-25 14:03:04 UTC 
The "Search for the best driver in these locations" should not be used to search for a driver under a directory tree that contains drivers for multiple OSes (the tree layout that we're using).
Comment 10 Min Deng 2013-07-26 03:38:23 UTC 
(In reply to Gal Hammer from comment #9)
> The "Search for the best driver in these locations" should not be used to
> search for a driver under a directory tree that contains drivers for
> multiple OSes (the tree layout that we're using).

Hi Gal,

   Could you please double check the issue before close it as Not a bug ? 
I described as the following on the original info,
"search for the best driver in these locations" -> folder->Wxp->x86 (59).The driver is under folder "x86" directly but not contains a directory tree.
   Any issues please let me know.

Thanks
Min
Comment 11 Gal Hammer 2013-08-08 08:59:42 UTC 
(In reply to dengmin from comment #10)
> (In reply to Gal Hammer from comment #9)
> > The "Search for the best driver in these locations" should not be used to
> > search for a driver under a directory tree that contains drivers for
> > multiple OSes (the tree layout that we're using).
> 
> Hi Gal,
> 
>    Could you please double check the issue before close it as Not a bug ? 
> I described as the following on the original info,
> "search for the best driver in these locations" -> folder->Wxp->x86 (59).The
> driver is under folder "x86" directly but not contains a directory tree.
>    Any issues please let me know.

My mistake, sorry.
 
> Thanks
> Min

It seem that you can't downgrade a driver using the "Search for the best driver in these locations" option because the newer (and installed) driver will be selected the as "best" driver.

So if want to force installation of a you should use the "Don't search" option and the "Have Disk" button to select the folder of the older driver. This method will allow you to install an older driver on a system that already have a driver installed.
Note You need to log in before you can comment on or make changes to this bug.