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.
Hi Vadim, I found two related bugs.The current solution is to warn users when they want to remove or upgrade the driver. But currently bz2005220 has not been fixed.So we can not recive any warning now. So is this bug a duplicate of 2005220? https://bugzilla.redhat.com/show_bug.cgi?id=1965552 https://bugzilla.redhat.com/show_bug.cgi?id=2005220
(In reply to leidwang from comment #1) > Hi Vadim, > > I found two related bugs.The current solution is to warn users when they > want to remove or upgrade the driver. > But currently bz2005220 has not been fixed.So we can not recive any warning > now. > So is this bug a duplicate of 2005220? > > https://bugzilla.redhat.com/show_bug.cgi?id=1965552 > https://bugzilla.redhat.com/show_bug.cgi?id=2005220 Well, technically the problem with warning the user needed to be split into two different parts : - .msi (https://bugzilla.redhat.com/show_bug.cgi?id=1965552) - FIXED - and the bundler (.exe) https://bugzilla.redhat.com/show_bug.cgi?id=2005220 - this problem is a way more complicated than .msi and is not fixed yet. All the best, Vadim.
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 ***
The bug reproducer is the same as https://bugzilla.redhat.com/show_bug.cgi?id=2005220, so I set qa_ack to +. Thanks!
Hi Vadim, Do we have any progress for this bug? It's ITR is 9.3.0~ Thanks~ Peixiu
(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.