All of lore.kernel.org
 help / color / mirror / Atom feed
From: phind.uet@gmail.com
To: Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Lukas Straub <lukasstraub2@web.de>, Peter Xu <peterx@redhat.com>,
	"Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>,
	Mark Kanda <mark.kanda@oracle.com>,
	Ben Chaney <bchaney@akamai.com>
Cc: Nguyen Dinh Phi <phind.uet@gmail.com>, qemu-devel@nongnu.org
Subject: [PATCH 0/3]  Support chain migration in test
Date: Thu,  9 Jul 2026 21:00:24 +0800	[thread overview]
Message-ID: <20260709130032.58667-1-phind.uet@gmail.com> (raw)

From: Nguyen Dinh Phi <phind.uet@gmail.com>

This series adds test infrastructure and test cases for multi-hop chain
migration, where a VM migrates from host A to B and then from B to C.

The migration test TODO list mentions ping-pong migration (A→B→A) as a
desirable scenario; the true ping-pong (A→B→A) would require the original
source A to become a destination for the return leg.
This is not possible: a QEMU process launched without -incoming cannot
later accept an incoming migration stream. Instead, this series implements
chain migration (A→B→C): B was already launched with -incoming and can
be re-wired as the source for the next hop, while a fresh QEMU instance C
is started as the new destination.

Nguyen Dinh Phi (3):
  tests/migration: Factor out per-process launch and setup helpers
  tests/migration: Retrieve serial path from QTestState
  tests/migration: Add chain (A to B to C) precopy migration tests

 tests/qtest/libqtest.c                |  16 +
 tests/qtest/libqtest.h                |   8 +
 tests/qtest/migration/colo-tests.c    |  14 +-
 tests/qtest/migration/cpr-tests.c     |   8 +-
 tests/qtest/migration/framework.c     | 475 ++++++++++++++++----------
 tests/qtest/migration/framework.h     |  21 +-
 tests/qtest/migration/misc-tests.c    |   4 +-
 tests/qtest/migration/precopy-tests.c |  51 ++-
 8 files changed, 389 insertions(+), 208 deletions(-)

-- 
2.50.1 (Apple Git-155)



             reply	other threads:[~2026-07-09 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 13:00 phind.uet [this message]
2026-07-09 13:00 ` [PATCH 1/3] tests/migration: Factor out per-process launch and setup helpers phind.uet
2026-07-09 13:00 ` [PATCH 2/3] tests/migration: Retrieve serial path from QTestState phind.uet
2026-07-09 13:00 ` [PATCH 3/3] tests/migration: Add chain (A to B to C) precopy migration tests phind.uet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260709130032.58667-1-phind.uet@gmail.com \
    --to=phind.uet@gmail.com \
    --cc=bchaney@akamai.com \
    --cc=lukasstraub2@web.de \
    --cc=lvivier@redhat.com \
    --cc=maciej.szmigiero@oracle.com \
    --cc=mark.kanda@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.