-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
rhel-9.6
-
None
-
None
-
Important
-
rhel-virt-windows
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
A Windows sever 2022 machine has several IP addresses configured in the same interface. The first one is considered the primary address. This machine is using the virtio-win drivers version 1.9.40
After updating the virtio-win drivers to 1.9.53 (errata RHBA-2026:2280), the IP address order is not preserved, in fact they are reversed, so the last one is now the primary.
What is the impact of this issue to you?
This affects applications that depend on the primary IP address.
Please provide the package NVR for which the bug is seen:
virtio-win-1.9.53-0.el9_6.noarch.rpm
VirtIO Ethernet Adapter 100.102.104.29400
How reproducible is this bug?:
Always
Steps to reproduce
- Install Windows server 2022 VM with virtio-win 1.9.40, configure multiple IP addresses in one interface
- Run the installer virtio-win-guest-tools.exe from virtio-win-1.9.53 to upgrade, then reboot
- Check IPs
Expected results
IP order respected
Actual results
IP order is reversed: the last IP is now the primary.
Initial state:

After upgrade:

- is related to
-
RHEL-137934 [virtio-win] IP address order is not preserved on driver update
-
- Release Pending
-
- relates to
-
RHEL-151323 [virtio-win] Network interface name is not preserved after driver update
-
- Planning
-