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

[vfio migration][seabios-1.16.3-1.el9] The Q35 + SEABIOS VM with a mlx VF can not be migrated

    • qemu-kvm-8.2.0-1.el9
    • Blocker
    • TestOnly, Regression
    • sst_virtualization
    • ssg_virtualization
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • Red Hat Enterprise Linux
    • x86_64
    • Unspecified

      What were you trying to do that didn't work?
      The Q35 + SEABIOS VM with a mlx5_vfio_pci VF can not be migrated when using seabios-1.16.3-1.el9

      Version-Release number of selected component (if applicable):
      host:
      5.14.0-402.el9.x86_64
      qemu-kvm-8.1.0-4.el9.x86_64
      libvirt-9.9.0-1.el9.x86_64
      seabios-1.16.3-1.el9
      VM:
      5.14.0-402.el9.x86_64

      How reproducible:
      100%

      Steps to reproduce
      1. create a MT2910 VF and setup the VF for migration

      2. start a Q35 + SEABIOS VM with a mlx5_vfio_pci VF

      3. check the MT2910 VF in the VM

      4. migrate the VM

      # virsh migrate --live --verbose --domain rhel94 --desturi qemu+ssh://10.73.212.98/system
      

      The migration process is hung

      related qmp:

      > {"execute":"getfd","arguments":{"fdname":"migrate"},"id":"libvirt-448"} (fd=21)
      <  {"return": {}, "id": "libvirt-448"}
      > {"execute":"migrate","arguments":{"detach":true,"resume":false,"uri":"fd:migrate"},"id":"libvirt-449"}
      !  {"timestamp": {"seconds": 1703741835, "microseconds": 924774}, "event": "MIGRATION", "data": {"status": "setup"}}
      <  {"return": {}, "id": "libvirt-449"}
      !  {"timestamp": {"seconds": 1703741835, "microseconds": 931893}, "event": "MIGRATION_PASS", "data": {"pass": 1}}
      !  {"timestamp": {"seconds": 1703741835, "microseconds": 965797}, "event": "MIGRATION", "data": {"status": "active"}}
      !  {"timestamp": {"seconds": 1703741835, "microseconds": 965844}, "event": "MIGRATION", "data": {"status": "failed"}}
      > {"execute":"query-migrate","id":"libvirt-450"} <-- The migration process is hung here
      

      5. Destroying the VM and then check the qemu-kvm log

      ...
      2023-12-28 05:08:46.219+0000: initiating migration
      2023-12-28T05:08:46.226485Z qemu-kvm: 0000:e1:00.1: Failed to start DMA logging, err -95 (Operation not supported)
      2023-12-28T05:08:46.226653Z qemu-kvm: vfio: Could not start dirty page tracking, err: -95 (Operation not supported)
      2023-12-28 05:54:02.734+0000: shutting down, reason=destroyed
      

      Expected results
      The Q35 + SEABIOS VM with a mlx VF can be migrated

      Actual results
      The Q35 + SEABIOS VM with a mlx VF can not be migrated

            rh-ee-clegoate Cédric Le Goater
            yanghliu@redhat.com YangHang Liu
            virt-maint virt-maint
            YangHang Liu YangHang Liu
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: