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.
Description of problem:
In bug 1898985 the documentation for upgrading the virtio-win drivers was updated to recommend using Windows update or using "netsh dump" to save the network configuration and then restore it.
This is risky or not feasible for several reasons:
- Windows update only works for Windows 2019. Older versions like 2016 are not getting the drivers.
- netsh dump poses some risk for VMs with multiple NICs for iSCSI, Windows clustering, backup etc.
- Dump transfer via netsh is not identical (this is problem of the netsh utility).
- netsh method is a potencial risky operation when you have to update hundreds of production VMs.
Version-Release number of selected component (if applicable):
virtio-win-1.9.19-1.el8.noarch
How reproducible:
Always
Steps to Reproduce:
1. Have Windows VM with static IP and an old version of virtio-win.
2. Run the installer virtio-win-guest-tools.exe
Actual results:
IP configuration is lost.
Expected results:
IP configuration preserved and drivers and qemu-ga updated.
Additional info:
We have seen that if you first update the NIC drivers and then run the installer, the IP configuration is preserved.
So the proposal for this bug is to modify the installer so it performs these steps in order:
1. Update NIC driver.
2. Remove old versions of the agent.
3. Upgrade everything else.
Comment 1leidwang@redhat.com
2021-11-26 03:07:08 UTC
Comment 3leidwang@redhat.com
2022-01-04 02:49:45 UTC
According to comment2,close this bz as duplicate of bz2005220.
Please reopen it if I misunderstood something.
*** This bug has been marked as a duplicate of bug 2005220 ***
Comment 7leidwang@redhat.com
2022-02-08 03:09:39 UTC
(In reply to Peixiu Hou from comment #22)
> Hi Vadim,
>
> Do we have any progress for this bug? It's ITR is 9.3.0~
>
> Thanks~
> Peixiu
Hi Peixiu,
It is an installer related issue. I'm going to start working on it
after virtio-win drivers code freeze.
Best,
Vadim.
(In reply to Vadim Rozenfeld from comment #23)
> (In reply to Peixiu Hou from comment #22)
> > Hi Vadim,
> >
> > Do we have any progress for this bug? It's ITR is 9.3.0~
> >
> > Thanks~
> > Peixiu
>
> Hi Peixiu,
> It is an installer related issue. I'm going to start working on it
> after virtio-win drivers code freeze.
>
ok, thanks~
> Best,
> Vadim.
the static ip backup/restoring functionally has been implemented. If other settings like DHCP, DNS, WINS or even storage related settings need to be preserved and restored during the virtio-win drivers update, then please open a new bug/jira issue with the exact list of parameters.
Best,
Vadim.
Hi Germano and Juan,
We suppose that keeping IP configurations would be sufficient to fix this bz, would you please help check the above comment 29 and confirm if there is other requirement from customer side? Thanks.
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 (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6388