There are some hardcoded migration blockers in libvirt, like having a net
vhost-vdpa device. While it's true that they cannot be migrated at the moment,
there are plans to be able to migrate them soon.

They'll put a migration blockers in the cases where you cannot migrate them.
Ask qemu about then before rejecting the migration. In case the question is not
possible, assume they're not migratable.

Eugenio Pérez (4):
  qemu_monitor_json: Add qemuMonitorJSONGetMigrationBlockers
  qemu_monitor: add support for get qemu migration blockers
  qemu_migration: get migration blockers before hardcoded checks
  qemu_migrate: Do not forbif vDPA devices if can query blockers

Jonathon Jongsma (1):
  qemu: introduce capability QEMU_MIGRATION_BLOCKED_REASONS

 src/qemu/qemu_capabilities.c                  |  2 +
 src/qemu/qemu_capabilities.h                  |  1 +
 src/qemu/qemu_migration.c                     | 38 ++++++++++++++++++-
 src/qemu/qemu_monitor.c                       | 11 ++++++
 src/qemu/qemu_monitor.h                       |  4 ++
 src/qemu/qemu_monitor_json.c                  | 35 +++++++++++++++++
 src/qemu/qemu_monitor_json.h                  |  3 ++
 .../caps_6.0.0.aarch64.xml                    |  1 +
 .../qemucapabilitiesdata/caps_6.0.0.s390x.xml |  1 +
 .../caps_6.0.0.x86_64.xml                     |  1 +
 .../caps_6.1.0.x86_64.xml                     |  1 +
 .../caps_6.2.0.aarch64.xml                    |  1 +
 .../qemucapabilitiesdata/caps_6.2.0.ppc64.xml |  1 +
 .../caps_6.2.0.x86_64.xml                     |  1 +
 .../caps_7.0.0.aarch64.xml                    |  1 +
 .../qemucapabilitiesdata/caps_7.0.0.ppc64.xml |  1 +
 .../caps_7.0.0.x86_64.xml                     |  1 +
 .../caps_7.1.0.x86_64.xml                     |  1 +
 18 files changed, 104 insertions(+), 1 deletion(-)

-- 
2.31.1