Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-910

the network in win2016/win2012r2 guest can't work after failover vf migraion between QL41000 and SFC9220 network cards

    • virtio-win-prewhql-0.1-242
    • Normal
    • sst_virtualization_windows
    • ssg_virtualization
    • 16
    • 18
    • None
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      .Broadcom network adapters now work correctly on Windows VMs after a live migration

      Previously, network adapters from the Broadcom family of devices, such as Broadcom, Qlogic, or Marvell, could not be hot-unplugged during live migration of Windows virtual machines (VMs). As a consequence, the adapters worked incorrectly after the migration was complete. This problem affected only adapters that were attached to Windows VMs using Single-root I/O virtualization (SR-IOV). With this update, the underlying code has been fixed and the problem no longer occurs.
      Show
      .Broadcom network adapters now work correctly on Windows VMs after a live migration Previously, network adapters from the Broadcom family of devices, such as Broadcom, Qlogic, or Marvell, could not be hot-unplugged during live migration of Windows virtual machines (VMs). As a consequence, the adapters worked incorrectly after the migration was complete. This problem affected only adapters that were attached to Windows VMs using Single-root I/O virtualization (SR-IOV). With this update, the underlying code has been fixed and the problem no longer occurs.
    • Done
    • None

      Description of problem:

      After live migrating win2016/win2012r2 guest with failover vf between QL41000 and SFC9220 network cards separately on src and dst hosts, ping will fail in windows guest and the network info of Device manager is src netowrk card info, not the dst network card info.

      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

      src host nic info
      FastLinQ QL41000 Series 10/25/40/50GbE Controller

      dst host nic info:
      SFC9220 10/40G Ethernet Controller

      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/win2012r2 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 step5, after migration, ping will fail and network info of vf is
      QLogic FastLinQ QL41112-DE 10GbE Adapter(src nic info), not the Solarflare Flareon Ultra 8000 Series 10G Adapter(dst nic info).

      ping 192.168.200.254

      Pinging 192.168.200.254 with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.

      Ping statistics for 192.168.200.254:
      Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

      C:\Windows\system32>ipconfig /all

      Windows IP Configuration

      Host Name . . . . . . . . . . . . : WIN-GB4G3MJFSG1
      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 3:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      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 2:

      Connection-specific DNS Suffix . : lab.eng.pek2.redhat.com
      Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter #2
      Physical Address. . . . . . . . . : 52-54-00-01-16-16
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      IPv6 Address. . . . . . . . . . . : 2620:52:0:49d2:70c4:4922:e7f2:78b(Preferred)
      Link-local IPv6 Address . . . . . : fe80::70c4:4922:e7f2:78b%4(Preferred)
      IPv4 Address. . . . . . . . . . . : 10.73.211.161(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.254.0
      Lease Obtained. . . . . . . . . . : Thursday, May 26, 2022 6:35:05 PM
      Lease Expires . . . . . . . . . . : Friday, May 27, 2022 6:35:04 AM
      Default Gateway . . . . . . . . . : fe80::52c7:903:533b:88e1%4
      10.73.211.254
      DHCP Server . . . . . . . . . . . : 10.73.2.108
      DHCPv6 IAID . . . . . . . . . . . : 106058752
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-1D-60-4C-9A-1B-C6-8F-35-F3
      DNS Servers . . . . . . . . . . . : 10.73.2.107
      10.73.2.108
      10.66.127.10
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Ethernet adapter Ethernet Instance 0 5:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : QLogic FastLinQ QL41112-DE 10GbE Adapter (VBD Client SR-IOV VF)
      Physical Address. . . . . . . . . : 52-54-00-AA-1C-EF
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::8dd9:4cf7:421:cdd8%15(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.200.26(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : Thursday, May 26, 2022 6:35:33 PM
      Lease Expires . . . . . . . . . . : Friday, May 27, 2022 6:35:32 PM
      Default Gateway . . . . . . . . . : 192.168.200.254
      DHCP Server . . . . . . . . . . . : 192.168.200.254
      DHCPv6 IAID . . . . . . . . . . . : 273830912
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-1D-60-4C-9A-1B-C6-8F-35-F3
      DNS Servers . . . . . . . . . . . : 192.168.200.253
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Tunnel adapter Teredo Tunneling Pseudo-Interface:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes
      IPv6 Address. . . . . . . . . . . : 2001:0:34f1:8072:383d:20ca:f5b6:2c5e(Preferred)
      Link-local IPv6 Address . . . . . : fe80::383d:20ca:f5b6:2c5e%2(Preferred)
      Default Gateway . . . . . . . . . :
      DHCPv6 IAID . . . . . . . . . . . : 134217728
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-1D-60-4C-9A-1B-C6-8F-35-F3
      NetBIOS over Tcpip. . . . . . . . : Disabled

      Tunnel adapter Reusable ISATAP Interface

      {9EF5D6D7-56AD-44E7-AF94-F90258691408}

      :

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      Tunnel adapter isatap.lab.eng.pek2.redhat.com:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . : lab.eng.pek2.redhat.com
      Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      After step 6, the guest can't be rebooted, and the scan for hardware changes will not quit. Pls see attachments.

      Expected results:
      After migration, the network should works well in windows guest.

      Additional info:

      There is not the issue for RHEL guest.

            yuri.benditovich Yuri Benditovich
            yama@redhat.com Yanhui Ma
            virt-maint virt-maint
            Yanhui Ma Yanhui Ma
            Daniel Vozenilek Daniel Vozenilek
            Votes:
            0 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: