From: Juan Quintela <quintela@redhat.com>
To: Steve Sistare <steven.sistare@oracle.com>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Leonardo Bras <leobras@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [PATCH V2 5/6] cpr: reboot mode
Date: Tue, 31 Oct 2023 14:21:25 +0100 [thread overview]
Message-ID: <87ttq76i7e.fsf@secure.mitica> (raw)
In-Reply-To: <1698263069-406971-6-git-send-email-steven.sistare@oracle.com> (Steve Sistare's message of "Wed, 25 Oct 2023 12:44:28 -0700")
Steve Sistare <steven.sistare@oracle.com> wrote:
> Add the cpr-reboot migration mode. Usage:
>
> $ qemu-system-$arch -monitor stdio ...
> QEMU 8.1.50 monitor - type 'help' for more information
> (qemu) migrate_set_capability x-ignore-shared on
> (qemu) migrate_set_parameter mode cpr-reboot
> (qemu) migrate -d file:vm.state
> (qemu) info status
> VM status: paused (postmigrate)
> (qemu) quit
>
> $ qemu-system-$arch -monitor stdio -incoming defer ...
> QEMU 8.1.50 monitor - type 'help' for more information
> (qemu) migrate_set_capability x-ignore-shared on
> (qemu) migrate_set_parameter mode cpr-reboot
> (qemu) migrate_incoming file:vm.state
> (qemu) info status
> VM status: running
>
> In this mode, the migrate command saves state to a file, allowing one
> to quit qemu, reboot to an updated kernel, and restart an updated version
> of qemu. The caller must specify a migration URI that writes to and reads
> from a file. Unlike normal mode, the use of certain local storage options
> does not block the migration, but the caller must not modify guest block
> devices between the quit and restart. To avoid saving guest RAM to the
> file, the memory backend must be shared, and the @x-ignore-shared migration
> capability must be set. Guest RAM must be non-volatile across reboot, such
> as by backing it with a dax device, but this is not enforced. The restarted
> qemu arguments must match those used to initially start qemu, plus the
> -incoming option.
>
> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2023-10-31 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 19:44 [PATCH V2 0/6] Live Update reboot mode Steve Sistare
2023-10-25 19:44 ` [PATCH V2 1/6] migration: mode parameter Steve Sistare
2023-10-31 13:17 ` Juan Quintela
2023-10-25 19:44 ` [PATCH V2 2/6] migration: per-mode blockers Steve Sistare
2023-10-25 19:44 ` [PATCH V2 3/6] cpr: relax blockdev migration blockers Steve Sistare
2023-10-31 15:41 ` Peter Xu
2023-10-25 19:44 ` [PATCH V2 4/6] cpr: relax vhost " Steve Sistare
2023-10-31 15:44 ` Peter Xu
2023-10-25 19:44 ` [PATCH V2 5/6] cpr: reboot mode Steve Sistare
2023-10-31 13:21 ` Juan Quintela [this message]
2023-10-25 19:44 ` [PATCH V2 6/6] tests/qtest: migration: add reboot mode test Steve Sistare
2023-10-31 13:19 ` Juan Quintela
2023-11-01 13:34 ` Fabiano Rosas
2023-11-01 13:57 ` Steven Sistare
2023-11-01 16:26 ` Steven Sistare
2023-11-01 16:52 ` Fabiano Rosas
-- strict thread matches above, loose matches on Subject: below --
2023-10-26 20:08 [PATCH V2 0/6] Live Update reboot mode Steve Sistare
2023-10-26 20:08 ` [PATCH V2 5/6] cpr: " Steve Sistare
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=87ttq76i7e.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.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).