From: Peter Xu <peterx@redhat.com>
To: Steve Sistare <steven.sistare@oracle.com>
Cc: qemu-devel@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH V2] migration: file URI
Date: Mon, 12 Jun 2023 14:44:31 -0400 [thread overview]
Message-ID: <ZIdnj7Hr1L3iDVUG@x1n> (raw)
In-Reply-To: <1686163139-256654-1-git-send-email-steven.sistare@oracle.com>
Hi, Steve,
On Wed, Jun 07, 2023 at 11:38:59AM -0700, Steve Sistare wrote:
> Extend the migration URI to support file:<filename>. This can be used for
> any migration scenario that does not require a reverse path. It can be used
> as an alternative to 'exec:cat > file' in minimized containers that do not
> contain /bin/sh, and it is easier to use than the fd:<fdname> URI. It can
> be used in HMP commands, and as a qemu command-line parameter.
I have similar question on the fixed-ram work, on whether we should assume
the vm stopped before doing so. Again, it leaves us space for
optimizations on top without breaking anyone.
The other thing is considering a very busy guest, migration may not even
converge for "file:" URI (the same to other URIs) but I think that doesn't
make much sense to not converge for a "file:" URI. The user might be very
confused too.
--
Peter Xu
next prev parent reply other threads:[~2023-06-12 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 18:38 [PATCH V2] migration: file URI Steve Sistare
2023-06-12 18:44 ` Peter Xu [this message]
2023-06-12 19:39 ` Steven Sistare
2023-06-12 19:55 ` Peter Xu
2023-06-14 15:47 ` Fabiano Rosas
2023-06-14 15:50 ` Peter Xu
2023-06-14 17:59 ` Fabiano Rosas
2023-06-14 18:38 ` Peter Xu
2023-06-15 14:50 ` Fabiano Rosas
2023-06-20 18:36 ` Steven Sistare
2023-06-20 19:35 ` Peter Xu
2023-06-21 12:40 ` Daniel P. Berrangé
2023-06-22 10:12 ` Daniel P. Berrangé
2023-06-22 12:28 ` Steven Sistare
2023-06-22 12:20 ` Fabiano Rosas
2023-06-22 20:39 ` Steven 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=ZIdnj7Hr1L3iDVUG@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).