Description of problem: Migrate vm with freePageReporting='on', error message reports "0x130000022 unsupported" Version-Release number of selected component (if applicable): Source: libvirt-daemon-7.0.0-8.module+el8.4.0+10233+8b7fd9eb.x86_64 qemu-kvm-5.2.0-10.module+el8.4.0+10217+cbdd2152.x86_64 Target: libvirt-daemon-6.6.0-13.1.module+el8.3.1+10185+675b2148.x86_64 qemu-kvm-5.1.0-20.module+el8.3.1+9918+230f5c26.x86_64 How reproducible: Always Steps to Reproduce: 1.Start domain with "freePageReporting='on'" added in memballoon. <memballoon model='virtio' freePageReporting='on'> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> 2. Migrate vm from RHEL-AV8.4 to RHEL-AV8.3.1 Actual results: [root@rhelav-8-4 ~]# virsh migrate avocado-vt-vm1 qemu+ssh://10.0.151.184/system --verbose root.**.**'s password: Migration: [ 91 %]error: internal error: qemu unexpectedly closed the monitor: 2021-03-15T10:38:10.610933Z qemu-kvm: -numa node,nodeid=0,cpus=0-1,mem=2048: warning: Parameter -numa node,mem is deprecated, use -numa node,memdev instead 2021-03-15T10:38:12.425475Z qemu-kvm: Features 0x130000022 unsupported. Allowed features: 0x179000002 2021-03-15T10:38:12.425509Z qemu-kvm: Failed to load virtio-balloon:virtio 2021-03-15T10:38:12.425515Z qemu-kvm: error while loading state for instance 0x0 of device '0000:00:02.4:00.0/virtio-balloon' 2021-03-15T10:38:12.449317Z qemu-kvm: warning: TSC frequency mismatch between VM (2693706 kHz) and host (2693670 kHz), and TSC scaling unavailable 2021-03-15T10:38:12.449525Z qemu-kvm: warning: TSC frequency mismatch between VM (2693706 kHz) and host (2693670 kHz), and TSC scaling unavailable 2021-03-15T10:38:12.449633Z qemu-kvm: load of migration failed: Operation not permitted Expected results: The error message can be more clear that "freePageReporting=on" is not supported Additional info: Migrate vm from RHEL-AV 8.4 to RHEL7.9 succeeded. version: libvirt-daemon-4.5.0-36.el7_9.3.x86_64 qemu-kvm-rhev-2.12.0-48.el7_9.2.x86_64
The freePageReporting feature was introduced in v6.8.0-312-gfee8a61d29, so the destination ignores the element and doesn't reject migration. Closing as duplicate of 1371747 which covers this case in a more general approach. *** This bug has been marked as a duplicate of bug 1371747 ***