qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Steven Sistare <steven.sistare@oracle.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH V2] migration: file URI
Date: Thu, 22 Jun 2023 08:28:36 -0400	[thread overview]
Message-ID: <0632be05-6184-eaf8-7bd6-fd986ffe1e35@oracle.com> (raw)
In-Reply-To: <ZJQenKR1aMJzaLCu@redhat.com>

On 6/22/2023 6:12 AM, Daniel P. Berrangé wrote:
> 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.
>>
>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
> 
> In the cases where libvirt wants to save/restore QEMU migration state
> to a file, we also need to have libvirt header and XML document at the
> front of the file.
> 
> IOW, if libvirt is to be able to use this new 'file:' protocol, then
> it neeeds to have the ability to specify an offset too. eg so libvirt
> can tell QEMU to start reading/writing at, for example, 4MB offset
> from the start.
> 
> Should be fairly easy to add on top of this - just requires support
> for a URI parameter, and then a seek once the file is opened.

Will do, probably today - steve


  reply	other threads:[~2023-06-22 12:29 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
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 [this message]
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=0632be05-6184-eaf8-7bd6-fd986ffe1e35@oracle.com \
    --to=steven.sistare@oracle.com \
    --cc=berrange@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --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).