* Bharata B Rao (bhar...@linux.vnet.ibm.com) wrote: > > Where we have iterable, but non-postcopiable devices (e.g. htab > > or block migration), complete them before forming the 'package' > > but with the CPUs stopped. This stops them filling up the package. > > That helps and the migration suceeds now when I switch to postcopy > immediately after starting the migration.
Excellent. > However after postcopy migration, when I attempt to start an incoming > instance again to migrate the guest back, I see this failure: > > qemu-system-ppc64: cannot set up guest memory 'ppc_spapr.ram': Cannot > allocate memory > > The same doesn't happen with normal migration. Huh that's fun; that's the original source guest that's running out of RAM? It's original QEMU should be gone by that point. > > I will see if I can debug this more tomorrow. Thanks. Dave > > Regards, > Bharata. > -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
