* Castelino, Manohar R (manohar.r.castelino@intel.com) wrote:
It's very similar to the trick that NEMU uses for templating. With the x-ignore-shared-ram migration capability enabled, migration will not write to the migration stream any RAM block that had the shared=on flag on the qemu commandline. So you should then be able to restart from the migration stream and existing RAM image.
So does it mean we can drop our vm-templating patches and move to using " x-ignore-shared-ram" on QEMU 4.0.
Today we only need two patches, which will come down to a single patch which would bring up closer to upstream QEMU 4.0 which would be ideal. https://github.com/kata-containers/packaging/blob/master/qemu/patches/4.0.x/... https://github.com/kata-containers/packaging/blob/master/qemu/patches/4.0.x/...
Yes, I'm hoping that with 4.0 you can avoid 0002 - but I've not tried it; I'd be interested in your results. Dave
-- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK