qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, "Leonardo Bras" <leobras@redhat.com>,
	"Peter Xu" <peterx@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
	"Li Zhijian" <lizhijian@fujitsu.com>,
	qemu-s390x@nongnu.org,
	"Steve Sistare" <steven.sistare@oracle.com>,
	"Michael Galaxy" <mgalaxy@akamai.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PULL 09/11] migration: file URI
Date: Wed, 04 Oct 2023 11:04:38 -0300	[thread overview]
Message-ID: <87o7hepjpl.fsf@suse.de> (raw)
In-Reply-To: <87cyxu33fp.fsf@secure.mitica>

Juan Quintela <quintela@redhat.com> writes:

> Fabiano Rosas <farosas@suse.de> wrote:
>> Juan Quintela <quintela@redhat.com> writes:
>>
>>> From: Steve Sistare <steven.sistare@oracle.com>
>>>
>>> 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.
>>>
>>> For best performance, guest ram should be shared and x-ignore-shared
>>> should be true, so guest pages are not written to the file, in which case
>>> the guest may remain running.  If ram is not so configured, then the user
>>> is advised to stop the guest first.  Otherwise, a busy guest may re-dirty
>>> the same page, causing it to be appended to the file multiple times,
>>> and the file may grow unboundedly.  That issue is being addressed in the
>>> "fixed-ram" patch series.
>>>
>>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>>> Tested-by: Michael Galaxy <mgalaxy@akamai.com>
>>> Reviewed-by: Michael Galaxy <mgalaxy@akamai.com>
>>> Reviewed-by: Fabiano Rosas <farosas@suse.de>
>>> Reviewed-by: Peter Xu <peterx@redhat.com>
>>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>>> Reviewed-by: Juan Quintela <quintela@redhat.com>
>>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>>> Message-ID: <1694182931-61390-2-git-send-email-steven.sistare@oracle.com>
>>
>> Juan, FYI we have tests for this feature already reviewed and ready to
>> merge:
>>
>> [PATCH v5 0/6] migration: Test the new "file:" migration
>> https://lore.kernel.org/r/20230712190742.22294-1-farosas@suse.de
>
> I searched for URI and didn't found it.
>
> Will got it on next PULL request.

Do you want me to do resend? It's no big deal.


  reply	other threads:[~2023-10-04 14:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 12:40 [PULL 00/11] Migration 20231004 patches Juan Quintela
2023-10-04 12:40 ` [PULL 01/11] migration/vmstate: Introduce vmstate_save_state_with_err Juan Quintela
2023-10-04 12:40 ` [PULL 02/11] migration: Update error description outside migration.c Juan Quintela
2023-10-04 12:40 ` [PULL 03/11] MAINTAINERS: Add entry for rdma migration Juan Quintela
2023-10-04 12:40 ` [PULL 04/11] migration: Add co-maintainers for migration Juan Quintela
2023-10-04 12:40 ` [PULL 05/11] migration/rdma: zore out head.repeat to make the error more clear Juan Quintela
2023-10-04 12:40 ` [PULL 06/11] i386/a-b-bootblock: factor test memory addresses out into constants Juan Quintela
2023-10-04 12:40 ` [PULL 07/11] i386/a-b-bootblock: zero the first byte of each page on start Juan Quintela
2023-10-04 12:40 ` [PULL 08/11] s390x/a-b-bios: " Juan Quintela
2023-10-04 12:40 ` [PULL 09/11] migration: file URI Juan Quintela
2023-10-04 13:45   ` Fabiano Rosas
2023-10-04 13:47     ` Juan Quintela
2023-10-04 14:04       ` Fabiano Rosas [this message]
2023-10-04 14:20         ` Juan Quintela
2023-10-04 12:40 ` [PULL 10/11] migration: file URI offset Juan Quintela
2023-10-04 12:40 ` [PULL 11/11] migration: Unify and trace vmstate field_exists() checks Juan Quintela
2023-10-04 18:33 ` [PULL 00/11] Migration 20231004 patches Stefan Hajnoczi

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=87o7hepjpl.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=berrange@redhat.com \
    --cc=leobras@redhat.com \
    --cc=lizhijian@fujitsu.com \
    --cc=mgalaxy@akamai.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=steven.sistare@oracle.com \
    --cc=thuth@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).