From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
peterx@redhat.com, "Daniel P . Berrangé" <berrange@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Leonardo Bras Soares Passos" <lsoaresp@redhat.com>,
"David Hildenbrand" <david@redhat.com>
Subject: [PATCH v2 0/4] migration/hostmem: Allow to fail early for postcopy on specific fs type
Date: Wed, 19 Apr 2023 12:17:35 -0400 [thread overview]
Message-ID: <20230419161739.1129988-1-peterx@redhat.com> (raw)
v2:
- Replace the hostmem patch to use qemu_fd_getfs() instead [David]
- Define enum instead of using string for fs type [Dan]
- One more patch added to deliver error to QMP response (rather than
keeping some of it in STDERR), so the response should contain richer
information and looks prettier.
Postcopy can fail in a weird way when guest mem is put onto a random file:
https://bugzilla.redhat.com/show_bug.cgi?id=2057267
It's because we only check userfault privilege on dest QEMU but don't check
memory types. We do so only until the UFFDIO_REGISTER right after we
switch to postcopy live migration from precopy but it could be too late.
This series tries to make it fail early by checking ramblock fs type if
backed by a memory-backend-file.
Now when it happens it'll fail the dest QEMU from the start:
./qemu-system-x86_64 \
-global migration.x-postcopy-ram=on \
-incoming defer \
-object memory-backend-file,id=mem,size=128M,mem-path=$memfile \
-machine memory-backend=mem
qemu-system-x86_64: Postcopy is not supported: Host backend files need to be TMPFS or HUGETLBFS only
It will also fail e.g. QMP migrate-set-capabilities properly:
{ "execute": "migrate-set-capabilities" , "arguments": { "capabilities": [ { "capability": "postcopy-ram", "state": true } ] } }
{"error": {"class": "GenericError", "desc": "Postcopy is not supported: Host backend files need to be TMPFS or HUGETLBFS only"}}
Please have a look, thanks.
Peter Xu (4):
util/mmap-alloc: qemu_fd_getfs()
vl.c: Create late backends before migration object
migration/postcopy: Detect file system on dest host
migration: Allow postcopy_ram_supported_by_host() to report err
include/qemu/mmap-alloc.h | 7 +++
migration/migration.c | 9 ++--
migration/postcopy-ram.c | 89 +++++++++++++++++++++++++++------------
migration/postcopy-ram.h | 3 +-
migration/savevm.c | 3 +-
softmmu/vl.c | 9 +++-
util/mmap-alloc.c | 28 ++++++++++++
7 files changed, 111 insertions(+), 37 deletions(-)
--
2.39.1
next reply other threads:[~2023-04-19 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 16:17 Peter Xu [this message]
2023-04-19 16:17 ` [PATCH v2 1/4] util/mmap-alloc: qemu_fd_getfs() Peter Xu
2023-04-19 16:31 ` David Hildenbrand
2023-04-19 19:34 ` Juan Quintela
2023-04-19 16:17 ` [PATCH v2 2/4] vl.c: Create late backends before migration object Peter Xu
2023-04-19 16:31 ` David Hildenbrand
2023-04-19 19:35 ` Juan Quintela
2023-04-19 16:17 ` [PATCH v2 3/4] migration/postcopy: Detect file system on dest host Peter Xu
2023-04-19 19:42 ` Juan Quintela
2023-04-19 16:17 ` [PATCH v2 4/4] migration: Allow postcopy_ram_supported_by_host() to report err Peter Xu
2023-04-19 19:51 ` Juan Quintela
2023-04-26 1:10 ` Peter Xu
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=20230419161739.1129988-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=pbonzini@redhat.com \
--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).