On Wed, Sep 20, 2023 at 12:26:51PM +0400, marcandre.lur...@redhat.com wrote: > From: Marc-André Lureau <marcandre.lur...@redhat.com> > > Implementing RAMFB migration seems quite straightforward. Unfortunately, > current QEMU didn't block migration when RAMFB was used. > > Having an extra "ramfb" VMState doesn't seem to "break" migration > forward compatibility. Surprisingly, missing sections are being ignored? > > Backward compatiblity however will have this extra error: > qemu: Unknown savevm section or instance 'ramfb' 0. Make sure that your > current VM setup matches your saved VM setup, including any hotplugged > devices.
I guess that is only fixable by making old machine types bug-compatible, i.e. register the ramfb vmstate only for qemu 8.2+ machine types. Otherwise looks fine to me. take care, Gerd
