On Tue, 2026-09-29 at 14:22 -0400, Peter Xu wrote: > On Tue, Sep 29, 2026 at 08:23:23PM +0300, Andrey Drobyshev wrote: > > The snapshot RAM-saving path does not support Xen's memory mappings. > > Refuse 'savevm' and 'loadvm' when running as a Xen device model, the > > same way they are refused for CPR migration modes. > > > > Suggested-by: Akihiko Odaki <[email protected]> > > Signed-off-by: Andrey Drobyshev <[email protected]> > > Acked-by: Peter Xu <[email protected]> > > Cc: David Woodhouse <[email protected]> > Cc: Paul Durrant <[email protected]>
Hm, but surely if QEMU is running as a device model for a Xen domain, all it should be saving and restoring is that device model. It's then up to Xen and its toolstack to migrate the domain and its memory. We've had guest-transparent live migration working on Xen, as well as in-place update of QEMU on the same host. Surely all of those require save/load support?
smime.p7s
Description: S/MIME cryptographic signature
