On Wed, Nov 25, 2015 at 15:22:08 +0100, Pavel Hrdina wrote:
On Wed, Nov 25, 2015 at 10:29:32AM +0100, Jiri Denemark wrote:
> Traditionally, we pass incoming migration URI on QEMU command line,
> which has some drawbacks. Depending on the URI QEMU may initialize its
> migration state immediately without giving us a chance to set any
> additional migration parameters (this applies mainly for fd: URIs). For
> some URIs the monitor may be completely blocked from the beginning until
> migration is finished, which means we may be stuck in qmp_capabilities
> command without being able to send any QMP commands.
>
> QEMU solved this by introducing "defer" parameter for -incoming command
> line option. This will tell QEMU to prepare for an incoming migration
> while the actual incoming URI is sent using migrate-incoming QMP
> command. Before calling this command we can normally talk to the
> monitor and even set any migration parameters which will be honored by
> the incoming migration.
>
> Jiri Denemark (7):
> qemu: Introduce qemuProcessInit
> qemu: Introduce qemuProcessLaunch
> qemu: Introduce qemuProcessFinishStartup
> qemu: Separate incoming URI generation from qemuMigrationPrepareAny
> qemu: Kill QEMU process if Prepare phase fails
> qemu: Skip starting NBD servers for offline migration
> qemu: Use qemuProcessLaunch in migration Prepare phase
>
> src/qemu/qemu_migration.c | 247 +++++++++++++----------
> src/qemu/qemu_process.c | 489 +++++++++++++++++++++++++++++-----------------
> src/qemu/qemu_process.h | 20 ++
> 3 files changed, 466 insertions(+), 290 deletions(-)
ACK series
Thanks, pushed.
Jirka