the network in win2016/win2022 guest can't work after failover vf migraion between MT2892 network cards

Description of problem:

After live migration win2016/win2022 guest with a failover vf between MT2892 network cards on both src and dst hosts, ping will fail in windows guest and the "network and sharing center" can't be opened, IP may will lost after a while. The guest also can't be rebooted, it will cause black screen.

Version-Release number of selected component (if applicable):

1. rpm -q qemu-kvm
   qemu-kvm-7.0.0-3.el9.x86_64
2. uname -r
   5.14.0-92.el9.x86_64
   host nic info:
   Mellanox Technologies MT2892 Family [ConnectX-6 Dx]

How reproducible:
100%

Steps to Reproduce:
1.create vf on both src host and dst host

echo 1 > /sys/bus/pci/devices/0000\:1a\:00.1/sriov_numvfs

2.create failover-vf and failover-bridge network on both src and dst host

1. virsh net-dumpxml failover-bridge
   <network connections='1'>
   <name>failover-bridge</name>
   <uuid>1943a508-b0b7-4274-be5a-6f0143d10f40</uuid>
   <forward mode='bridge'/>
   <bridge name='br0'/>
   </network>

1. virsh net-dumpxml failover-vf
   <network connections='1'>
   <name>failover-vf</name>
   <uuid>4319b666-8f4b-410a-886f-17b6df772224</uuid>
   <forward mode='hostdev' managed='yes'>
   <address type='pci' domain='0x0000' bus='0x1a' slot='0x08' function='0x2'/>
   </forward>
   </network>

3.boot win216/win2022 guest with failover vf on src host
<interface type='network'>
<mac address='52:54:00:aa:1c:ef'/>
<source network='failover-bridge'/>
<model type='virtio'/>
<teaming type='persistent'/>
<alias name='ua-test'/>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</interface>
<interface type='network'>
<mac address='52:54:00:aa:1c:ef'/>
<source network='failover-vf'/>
<teaming type='transient' persistent='ua-test'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
</interface>

4. live migrating the guest
5. after migration, check the network in guest
6. reboot the guest or scan the hardware changes via Device manager in guest

Actual results:

After step 5, ping will fail, can't open "network and sharing center", see the attachment.

1. ipconfig /all
   Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN-A1AR6C3G7HJ
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lab.eng.pek2.redhat.com

Ethernet adapter Ethernet Instance 0 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lab.eng.pek2.redhat.com
Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter #3
Physical Address. . . . . . . . . : 52-54-00-AA-1C-EF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet Instance 0 13:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ConnectX Family mlx5Gen Virtual Function #3
Physical Address. . . . . . . . . : 52-54-00-AA-1C-EF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a5f1:2227:8917:709f%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.43.200(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, May 30, 2022 3:58:52 AM
Lease Expires . . . . . . . . . . : Monday, May 30, 2022 4:08:52 AM
Default Gateway . . . . . . . . . : 192.168.43.2
DHCP Server . . . . . . . . . . . : 192.168.43.6
DHCPv6 IAID . . . . . . . . . . . : 853941549
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-3A-24-B9-9A-9B-AB-AE-4E-E3
DNS Servers . . . . . . . . . . . : 192.168.43.2
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : lab.eng.pek2.redhat.com
Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter #2
Physical Address. . . . . . . . . : 52-54-00-01-22-22
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2620:52:0:49d2:78cd:cab3:51da:bf42(Preferred)
Link-local IPv6 Address . . . . . : fe80::78cd:cab3:51da:bf42%23(Preferred)
IPv4 Address. . . . . . . . . . . : 10.73.211.223(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Lease Obtained. . . . . . . . . . : Monday, May 30, 2022 3:58:36 AM
Lease Expires . . . . . . . . . . : Tuesday, May 31, 2022 3:58:35 AM
Default Gateway . . . . . . . . . : fe80::52c7:903:533b:88e1%23
10.73.211.254
DHCP Server . . . . . . . . . . . : 10.73.2.108
DHCPv6 IAID . . . . . . . . . . . : 122835968
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-3A-24-B9-9A-9B-AB-AE-4E-E3
DNS Servers . . . . . . . . . . . : 10.73.2.107
10.73.2.108
10.66.127.10
NetBIOS over Tcpip. . . . . . . . : Enabled

1. ping 192.168.43.6
   Pinging 192.168.43.6 with 32 bytes of data:
   Reply from 192.168.43.200: Destination host unreachable.
   Request timed out.
   Request timed out.
   Request timed out.

Ping statistics for 192.168.43.6:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss)

1. ping 192.168.43.101
   Pinging 192.168.43.101 with 32 bytes of data:
   Request timed out.
   Request timed out.
   Reply from 192.168.43.200: Destination host unreachable.
   Reply from 192.168.43.200: Destination host unreachable.

Ping statistics for 192.168.43.101:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)

After step 6, the guest can't be rebooted, it will cause black screen.

Expected results:

After migration, the ping src host ip and dst host ip can work well.
Additional info:

RHEL9.1 guest doesn't have the issue.