fix live migration issues in qemu

[woojoong88]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

There is a gap between qemu centos distro and azl distro, which makes the live migration test failed in KubeVirt.

Change Log

• Sun Apr 05 2026 Woojoong Kim woojoongkim@microsoft.com - 9.1.0-2

• Add 23 QEMU patches from RHEL qemu-kvm 9.1.0-20 for KubeVirt live migration
• Post-migration networking: fix announce_self ARP/GARP (RHEL-73891),
  add virtio-net queues before loading during incoming migration (RHEL-69477)
• Migration stability: fix UAF on cancelled incoming migration (RHEL-69775),
  ensure vmstate_save sets error pointer (RHEL-67844)
• Disk activation: add migration target runstate helper, delay disk activation
  until migration completes, extend late-block-active to postcopy, fix race
  with block_inactive, rewrite disk activation logic, per-node activation state
• Block layer inactive node framework: expose active/inactive status via QMP,
  add blockdev-set-active command, support creating/inactivating inactive nodes,
  fix crash on block_resize of inactive node, drain I/O before inactivation,
  support NBD export of inactive nodes for storage daemon

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• N/A

Test Methodology

• Pipeline buddy build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1087213&view=results