What were you trying to do that didn't work?

A Windows server 2022 VM is configured with multiple IPv4 addresses. One of these addresses is considered the primary.

After updating the netkvm driver, the IP address order is not preserved and another IP address is now the primary.

What is the impact of this issue to you?

This IP address reordering affects some services that depend on the primary IP address for authorization.

Please provide the package NVR for which the bug is seen:

virtio-win-1.9.49-0.el9_6.noarch

How reproducible is this bug?:

Always

Steps to reproduce

1. Windows 2022 VM running on a RHEL 9.6 hypervisor
2. Configure the virtio interface with multiple IP addresses:

1. Upgrade the virtio-win driver using the installer in the virtio-win-1.9.49 ISO. Also tested using the msi instead of the installer.

Expected results

Network configuration preserved exactly as is.

Actual results

The interface now has a different IP address as primary.

Checking the file "C:\Program Files\Virtio Win\viocfg.cfg" I can confirm that the new primary IP is now the first in the list: