From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Wei Wang <wei.w.wang@intel.com>,
qemu-devel@nongnu.org,
Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: [PATCH v2] virtio-balloon: always indicate S_DONE when migration fails
Date: Wed, 22 Jul 2020 08:04:17 -0400 [thread overview]
Message-ID: <20200722080356-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200629080615.26022-1-david@redhat.com>
On Mon, Jun 29, 2020 at 10:06:15AM +0200, David Hildenbrand wrote:
> If something goes wrong during precopy, before stopping the VM, we will
> never send a S_DONE indication to the VM, resulting in the hinted pages
> not getting released to be used by the guest OS (e.g., Linux).
>
> Easy to reproduce:
> 1. Start migration (e.g., HMP "migrate -d 'exec:gzip -c > STATEFILE.gz'")
> 2. Cancel migration (e.g., HMP "migrate_cancel")
> 3. Oberve in the guest (e.g., cat /proc/meminfo) that there is basically
> no free memory left.
>
> While at it, add similar locking to virtio_balloon_free_page_done() as
> done in virtio_balloon_free_page_stop. Locking is still weird, but that
> has to be sorted out separately.
>
> There is nothing to do in the PRECOPY_NOTIFY_COMPLETE case. Add some
> comments regarding S_DONE handling.
>
> Fixes: c13c4153f76d ("virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT")
> Reviewed-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
> Cc: Wei Wang <wei.w.wang@intel.com>
> Cc: Alexander Duyck <alexander.duyck@gmail.com>
> Signed-off-by: David Hildenbrand <david@redhat.com>
IIUC this is superceded by Alexander's patches right?
If not pls rebase ...
> ---
> hw/virtio/virtio-balloon.c | 26 ++++++++++++++++++++------
> 1 file changed, 20 insertions(+), 6 deletions(-)
>
> diff --git a/hw/virtio/virtio-balloon.c b/hw/virtio/virtio-balloon.c
> index 10507b2a43..8a84718490 100644
> --- a/hw/virtio/virtio-balloon.c
> +++ b/hw/virtio/virtio-balloon.c
> @@ -628,8 +628,13 @@ static void virtio_balloon_free_page_done(VirtIOBalloon *s)
> {
> VirtIODevice *vdev = VIRTIO_DEVICE(s);
>
> - s->free_page_report_status = FREE_PAGE_REPORT_S_DONE;
> - virtio_notify_config(vdev);
> + if (s->free_page_report_status != FREE_PAGE_REPORT_S_DONE) {
> + /* See virtio_balloon_free_page_stop() */
> + qemu_mutex_lock(&s->free_page_lock);
> + s->free_page_report_status = FREE_PAGE_REPORT_S_DONE;
> + qemu_mutex_unlock(&s->free_page_lock);
> + virtio_notify_config(vdev);
> + }
> }
>
> static int
> @@ -653,17 +658,26 @@ virtio_balloon_free_page_report_notify(NotifierWithReturn *n, void *data)
> case PRECOPY_NOTIFY_SETUP:
> precopy_enable_free_page_optimization();
> break;
> - case PRECOPY_NOTIFY_COMPLETE:
> - case PRECOPY_NOTIFY_CLEANUP:
> case PRECOPY_NOTIFY_BEFORE_BITMAP_SYNC:
> virtio_balloon_free_page_stop(dev);
> break;
> case PRECOPY_NOTIFY_AFTER_BITMAP_SYNC:
> if (vdev->vm_running) {
> virtio_balloon_free_page_start(dev);
> - } else {
> - virtio_balloon_free_page_done(dev);
> + break;
> }
> + /*
> + * Set S_DONE before migrating the vmstate, so the guest will reuse
> + * all hinted pages once running on the destination. Fall through.
> + */
> + case PRECOPY_NOTIFY_CLEANUP:
> + /*
> + * Especially, if something goes wrong during precopy or if migration
> + * is canceled, we have to properly communicate S_DONE to the VM.
> + */
> + virtio_balloon_free_page_done(dev);
> + break;
> + case PRECOPY_NOTIFY_COMPLETE:
> break;
> default:
> virtio_error(vdev, "%s: %d reason unknown", __func__, pnd->reason);
> --
> 2.26.2
next prev parent reply other threads:[~2020-07-22 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 8:06 [PATCH v2] virtio-balloon: always indicate S_DONE when migration fails David Hildenbrand
2020-07-22 12:04 ` Michael S. Tsirkin [this message]
2020-07-22 12:05 ` David Hildenbrand
2020-07-22 12:11 ` David Hildenbrand
2020-07-22 14:55 ` Alexander Duyck
2020-07-23 4:10 ` Michael S. Tsirkin
2020-07-23 3:59 ` 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=20200722080356-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wei.w.wang@intel.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).