qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	Alexey Perevalov <a.perevalov@samsung.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	peterx@redhat.com
Subject: [Qemu-devel] [PATCH v7 04/23] migration: allow dst vm pause on postcopy
Date: Fri,  9 Mar 2018 17:15:16 +0800	[thread overview]
Message-ID: <20180309091535.13315-5-peterx@redhat.com> (raw)
In-Reply-To: <20180309091535.13315-1-peterx@redhat.com>

When there is IO error on the incoming channel (e.g., network down),
instead of bailing out immediately, we allow the dst vm to switch to the
new POSTCOPY_PAUSE state. Currently it is still simple - it waits the
new semaphore, until someone poke it for another attempt.

One note is that here on ram loading thread we cannot detect the
POSTCOPY_ACTIVE state, but we need to detect the more specific
POSTCOPY_INCOMING_RUNNING state, to make sure we have already loaded all
the device states.

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
---
 migration/migration.c  |  1 +
 migration/migration.h  |  3 +++
 migration/savevm.c     | 63 ++++++++++++++++++++++++++++++++++++++++++++++++--
 migration/trace-events |  2 ++
 4 files changed, 67 insertions(+), 2 deletions(-)

diff --git a/migration/migration.c b/migration/migration.c
index 84afed174d..91a4ebba8f 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -157,6 +157,7 @@ MigrationIncomingState *migration_incoming_get_current(void)
         memset(&mis_current, 0, sizeof(MigrationIncomingState));
         qemu_mutex_init(&mis_current.rp_mutex);
         qemu_event_init(&mis_current.main_thread_load_event, false);
+        qemu_sem_init(&mis_current.postcopy_pause_sem_dst, 0);
         once = true;
     }
     return &mis_current;
diff --git a/migration/migration.h b/migration/migration.h
index 5774b25358..9a2de4ba9b 100644
--- a/migration/migration.h
+++ b/migration/migration.h
@@ -61,6 +61,9 @@ struct MigrationIncomingState {
     /* The coroutine we should enter (back) after failover */
     Coroutine *migration_incoming_co;
     QemuSemaphore colo_incoming_sem;
+
+    /* notify PAUSED postcopy incoming migrations to try to continue */
+    QemuSemaphore postcopy_pause_sem_dst;
 };
 
 MigrationIncomingState *migration_incoming_get_current(void);
diff --git a/migration/savevm.c b/migration/savevm.c
index 358c5b51e2..babcff4844 100644
--- a/migration/savevm.c
+++ b/migration/savevm.c
@@ -1549,8 +1549,8 @@ static int loadvm_postcopy_ram_handle_discard(MigrationIncomingState *mis,
  */
 static void *postcopy_ram_listen_thread(void *opaque)
 {
-    QEMUFile *f = opaque;
     MigrationIncomingState *mis = migration_incoming_get_current();
+    QEMUFile *f = mis->from_src_file;
     int load_res;
 
     migrate_set_state(&mis->state, MIGRATION_STATUS_ACTIVE,
@@ -1564,6 +1564,14 @@ static void *postcopy_ram_listen_thread(void *opaque)
      */
     qemu_file_set_blocking(f, true);
     load_res = qemu_loadvm_state_main(f, mis);
+
+    /*
+     * This is tricky, but, mis->from_src_file can change after it
+     * returns, when postcopy recovery happened. In the future, we may
+     * want a wrapper for the QEMUFile handle.
+     */
+    f = mis->from_src_file;
+
     /* And non-blocking again so we don't block in any cleanup */
     qemu_file_set_blocking(f, false);
 
@@ -1646,7 +1654,7 @@ static int loadvm_postcopy_handle_listen(MigrationIncomingState *mis)
     /* Start up the listening thread and wait for it to signal ready */
     qemu_sem_init(&mis->listen_thread_sem, 0);
     qemu_thread_create(&mis->listen_thread, "postcopy/listen",
-                       postcopy_ram_listen_thread, mis->from_src_file,
+                       postcopy_ram_listen_thread, NULL,
                        QEMU_THREAD_DETACHED);
     qemu_sem_wait(&mis->listen_thread_sem);
     qemu_sem_destroy(&mis->listen_thread_sem);
@@ -2031,11 +2039,44 @@ void qemu_loadvm_state_cleanup(void)
     }
 }
 
+/* Return true if we should continue the migration, or false. */
+static bool postcopy_pause_incoming(MigrationIncomingState *mis)
+{
+    trace_postcopy_pause_incoming();
+
+    migrate_set_state(&mis->state, MIGRATION_STATUS_POSTCOPY_ACTIVE,
+                      MIGRATION_STATUS_POSTCOPY_PAUSED);
+
+    assert(mis->from_src_file);
+    qemu_file_shutdown(mis->from_src_file);
+    qemu_fclose(mis->from_src_file);
+    mis->from_src_file = NULL;
+
+    assert(mis->to_src_file);
+    qemu_file_shutdown(mis->to_src_file);
+    qemu_mutex_lock(&mis->rp_mutex);
+    qemu_fclose(mis->to_src_file);
+    mis->to_src_file = NULL;
+    qemu_mutex_unlock(&mis->rp_mutex);
+
+    error_report("Detected IO failure for postcopy. "
+                 "Migration paused.");
+
+    while (mis->state == MIGRATION_STATUS_POSTCOPY_PAUSED) {
+        qemu_sem_wait(&mis->postcopy_pause_sem_dst);
+    }
+
+    trace_postcopy_pause_incoming_continued();
+
+    return true;
+}
+
 static int qemu_loadvm_state_main(QEMUFile *f, MigrationIncomingState *mis)
 {
     uint8_t section_type;
     int ret = 0;
 
+retry:
     while (true) {
         section_type = qemu_get_byte(f);
 
@@ -2080,6 +2121,24 @@ static int qemu_loadvm_state_main(QEMUFile *f, MigrationIncomingState *mis)
 out:
     if (ret < 0) {
         qemu_file_set_error(f, ret);
+
+        /*
+         * Detect whether it is:
+         *
+         * 1. postcopy running (after receiving all device data, which
+         *    must be in POSTCOPY_INCOMING_RUNNING state.  Note that
+         *    POSTCOPY_INCOMING_LISTENING is still not enough, it's
+         *    still receiving device states).
+         * 2. network failure (-EIO)
+         *
+         * If so, we try to wait for a recovery.
+         */
+        if (postcopy_state_get() == POSTCOPY_INCOMING_RUNNING &&
+            ret == -EIO && postcopy_pause_incoming(mis)) {
+            /* Reset f to point to the newly created channel */
+            f = mis->from_src_file;
+            goto retry;
+        }
     }
     return ret;
 }
diff --git a/migration/trace-events b/migration/trace-events
index 7afbb3e791..8685a62c98 100644
--- a/migration/trace-events
+++ b/migration/trace-events
@@ -100,6 +100,8 @@ open_return_path_on_source(void) ""
 open_return_path_on_source_continue(void) ""
 postcopy_start(void) ""
 postcopy_pause_continued(void) ""
+postcopy_pause_incoming(void) ""
+postcopy_pause_incoming_continued(void) ""
 postcopy_start_set_run(void) ""
 source_return_path_thread_bad_end(void) ""
 source_return_path_thread_end(void) ""
-- 
2.14.3

  parent reply	other threads:[~2018-03-09  9:15 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  9:15 [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 01/23] migration: let incoming side use thread context Peter Xu
2018-03-12 17:27   ` Dr. David Alan Gilbert
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 02/23] migration: new postcopy-pause state Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 03/23] migration: implement "postcopy-pause" src logic Peter Xu
2018-03-09  9:15 ` Peter Xu [this message]
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 05/23] migration: allow src return path to pause Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 06/23] migration: allow fault thread " Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 07/23] qmp: hmp: add migrate "resume" option Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 08/23] migration: rebuild channel on source Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 09/23] migration: new state "postcopy-recover" Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 10/23] migration: wakeup dst ram-load-thread for recover Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 11/23] migration: new cmd MIG_CMD_RECV_BITMAP Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 12/23] migration: new message MIG_RP_MSG_RECV_BITMAP Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 13/23] migration: new cmd MIG_CMD_POSTCOPY_RESUME Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 14/23] migration: new message MIG_RP_MSG_RESUME_ACK Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 15/23] migration: introduce SaveVMHandlers.resume_prepare Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 16/23] migration: synchronize dirty bitmap for resume Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 17/23] migration: setup ramstate " Peter Xu
2018-03-12 17:29   ` Dr. David Alan Gilbert
2018-03-12 17:30   ` Dr. David Alan Gilbert
2018-03-13  8:36     ` Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 18/23] migration: final handshake for the resume Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 19/23] migration: init dst in migration_object_init too Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 20/23] qmp/migration: new command migrate-recover Peter Xu
2018-03-12 17:33   ` Dr. David Alan Gilbert
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 21/23] hmp/migration: add migrate_recover command Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 22/23] migration/qmp: add command migrate-pause Peter Xu
2018-03-12 17:36   ` Dr. David Alan Gilbert
2018-03-13  8:54     ` Peter Xu
2018-03-09  9:15 ` [Qemu-devel] [PATCH v7 23/23] migration/hmp: add migrate_pause command Peter Xu
2018-03-09  9:47 ` [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery no-reply
2018-03-09  9:48 ` no-reply
2018-03-09  9:49 ` no-reply
2018-03-09  9:51 ` no-reply
2018-03-09  9:56 ` no-reply
2018-03-09  9:57 ` no-reply
2018-03-09 16:54 ` Eric Blake
2018-03-09 16:59   ` Eric Blake
2018-03-12  4:45     ` Peter Xu
2018-03-15  8:19       ` Fam Zheng
2018-03-15  8:41         ` Peter Xu
2018-03-15  9:04           ` Fam Zheng

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=20180309091535.13315-5-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=a.perevalov@samsung.com \
    --cc=aarcange@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).