From: Peter Xu <peterx@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Michal Privoznik <mprivozn@redhat.com>
Subject: Re: [PATCH v5 0/8] virtio-mem: Handle preallocation with migration
Date: Tue, 17 Jan 2023 10:40:02 -0500 [thread overview]
Message-ID: <Y8bBUsn9oILkEr91@x1n> (raw)
In-Reply-To: <20230117112249.244096-1-david@redhat.com>
On Tue, Jan 17, 2023 at 12:22:41PM +0100, David Hildenbrand wrote:
> While playing with migration of virtio-mem with an ordinary file backing,
> I realized that migration and prealloc doesn't currently work as expected
> for virtio-mem. Further, Jing Qi reported that setup issues (insufficient
> huge pages on the destination) result in QEMU getting killed with SIGBUS
> instead of failing gracefully.
>
> In contrast to ordinary memory backend preallocation, virtio-mem
> preallocates memory before plugging blocks to the guest. Consequently,
> when migrating we are not actually preallocating on the destination but
> "only" migrate pages. Fix that be migrating the bitmap early, before any
> RAM content, and use that information to preallocate memory early, before
> migrating any RAM.
>
> Postcopy needs some extra care, and I realized that prealloc+postcopy is
> shaky in general. Let's at least try to mimic what ordinary
> prealloc+postcopy does: temporarily allocate the memory, discard it, and
> cross fingers that we'll still have sufficient memory when postcopy
> actually tries placing pages.
>
> Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Cc: Juan Quintela <quintela@redhat.com>
> Cc: Peter Xu <peterx@redhat.com>
> Cc: Michael S. Tsirkin <mst@redhat.com>
> Cc: Michal Privoznik <mprivozn@redhat.com>
For patch 1-5:
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2023-01-17 15:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 11:22 [PATCH v5 0/8] virtio-mem: Handle preallocation with migration David Hildenbrand
2023-01-17 11:22 ` [PATCH v5 1/8] migration/savevm: Move more savevm handling into vmstate_save() David Hildenbrand
2023-02-02 11:46 ` Juan Quintela
2023-01-17 11:22 ` [PATCH v5 2/8] migration/savevm: Prepare vmdesc json writer in qemu_savevm_state_setup() David Hildenbrand
2023-02-02 11:48 ` Juan Quintela
2023-01-17 11:22 ` [PATCH v5 3/8] migration/savevm: Allow immutable device state to be migrated early (i.e., before RAM) David Hildenbrand
2023-02-02 11:49 ` Juan Quintela
2023-01-17 11:22 ` [PATCH v5 4/8] migration/vmstate: Introduce VMSTATE_WITH_TMP_TEST() and VMSTATE_BITMAP_TEST() David Hildenbrand
2023-02-02 11:50 ` Juan Quintela
2023-01-17 11:22 ` [PATCH v5 5/8] migration/ram: Factor out check for advised postcopy David Hildenbrand
2023-02-02 11:51 ` Juan Quintela
2023-01-17 11:22 ` [PATCH v5 6/8] virtio-mem: Fail if a memory backend with "prealloc=on" is specified David Hildenbrand
2023-02-02 11:52 ` Juan Quintela
2023-01-17 11:22 ` [PATCH v5 7/8] virtio-mem: Migrate immutable properties early David Hildenbrand
2023-02-02 11:54 ` Juan Quintela
2023-01-17 11:22 ` [PATCH v5 8/8] virtio-mem: Proper support for preallocation with migration David Hildenbrand
2023-02-02 11:56 ` Juan Quintela
2023-01-17 15:40 ` Peter Xu [this message]
2023-01-23 14:27 ` [PATCH v5 0/8] virtio-mem: Handle " David Hildenbrand
2023-02-02 11:04 ` Juan Quintela
2023-02-02 12:58 ` David Hildenbrand
2023-02-02 11:11 ` Michael S. Tsirkin
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=Y8bBUsn9oILkEr91@x1n \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mprivozn@redhat.com \
--cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.