Reproducer using upstream QEMU: source: # qemu-4.2 -M pc-i440fx-4.2 -cpu EPYC -smp 8,sockets=1,cores=8 -numa node,cpus=0-3 -numa node,cpus=4-7 -m 2048 -snapshot -monitor stdio -enable-kvm /vmimage (qemu) stop (qemu) migrate "exec:gzip -c > STATEFILE.gz" target: # qemu-5.1 -cpu EPYC -smp 8,sockets=1,cores=8 -numa node,cpus=0-3 -numa node,cpus=4-7 -m 2048 -snapshot -monitor stdio -enable-kvm -M pc-i440fx-4.2 -incoming "exec: gzip -c -d STATEFILE.gz" /vmimage migration fails with: qemu-system-x86_64: Unknown savevm section or instance 'apic' 4. Make sure that your current VM setup matches your saved VM setup, including any hotplugged devices qemu-system-x86_64: load of migration failed: Invalid argument
Replicated on downstream: qemu-kvm-core-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.x86_64 /usr/libexec/qemu-kvm -M pc-q35-rhel8.2.0 -cpu EPYC -smp 8,sockets=1,cores=8 -numa node,cpus=0-3 -numa node,cpus=4-7 -m 2048 -nographic (qemu) migrate "tcp:vl721:4444" qemu-kvm-core-5.1.0-4.module+el8.3.0+7846+ae9b566f.x86_64 /usr/libexec/qemu-kvm -M pc-q35-rhel8.2.0 -cpu EPYC -smp 8,sockets=1,cores=8 -numa node,cpus=0-3 -numa node,cpus=4-7 -m 2048 -nographic -incoming tcp::4444 qemu-kvm: warning: Default splitting of RAM between nodes is deprecated, Use '-numa node,memdev' to explictly define RAM allocation per node qemu-kvm: Unknown savevm section or instance 'apic' 4. Make sure that your current VM setup matches your saved VM setup, including any hotplugged devices qemu-kvm: load of migration failed: Invalid argument
Can we fix this just by turning off '.use_epyc_apic_id_encoding' on the CPU models?
(In reply to Dr. David Alan Gilbert from comment #5) > Can we fix this just by turning off '.use_epyc_apic_id_encoding' on the CPU > models? We can do that. It will be good if we can fix couple of decoding issues in CPUID 0x8000001e with that. I think we are almost there. https://lore.kernel.org/qemu-devel/56d9a7fb-d88a-258d-1c67-768d63369643@amd.com/ Hopefully it will resolved soon. thanks
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virt:8.3 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5137