From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Reiter <s.reiter@proxmox.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH] migration: only check page size match if RAM postcopy is enabled
Date: Thu, 4 Feb 2021 16:55:43 +0000 [thread overview]
Message-ID: <20210204165543.GL3039@work-vm> (raw)
In-Reply-To: <20210204163522.13291-1-s.reiter@proxmox.com>
* Stefan Reiter (s.reiter@proxmox.com) wrote:
> Postcopy may also be advised for dirty-bitmap migration only, in which
> case the remote page size will not be available and we'll instead read
> bogus data, blocking migration with a mismatch error if the VM uses
> hugepages.
>
> Fixes: 58110f0acb ("migration: split common postcopy out of ram postcopy")
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
Ah! That would explain a report on qemu-discuss a few days ago; yes this
makes sense.
(However you've literally just missed a migration pull; next time!)
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/ram.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 7811cde643..6ace15261c 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -3521,7 +3521,7 @@ static int ram_load_precopy(QEMUFile *f)
> }
> }
> /* For postcopy we need to check hugepage sizes match */
> - if (postcopy_advised &&
> + if (postcopy_advised && migrate_postcopy_ram() &&
> block->page_size != qemu_host_page_size) {
> uint64_t remote_page_size = qemu_get_be64(f);
> if (remote_page_size != block->page_size) {
> --
> 2.20.1
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2021-02-04 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 16:35 [PATCH] migration: only check page size match if RAM postcopy is enabled Stefan Reiter
2021-02-04 16:55 ` Dr. David Alan Gilbert [this message]
2021-02-08 10:59 ` Dr. David Alan Gilbert
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=20210204165543.GL3039@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=s.reiter@proxmox.com \
--cc=vsementsov@virtuozzo.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).