From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yury Kotov <yury-kotov@yandex-team.ru>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
yc-core@yandex-team.ru, "Juan Quintela" <quintela@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [RFC PATCH 0/1] Removing RAMBlocks during migration
Date: Tue, 7 Jan 2020 15:02:10 -0500 [thread overview]
Message-ID: <20200107145914-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191209074102.5926-1-yury-kotov@yandex-team.ru>
On Mon, Dec 09, 2019 at 10:41:01AM +0300, Yury Kotov wrote:
> Hi,
>
> I found that it's possible to remove a RAMBlock during migration.
> E.g. device hot-unplugging initiated by a guest (how to reproduce is below).
> And I want to clarify whether RAMBlock removing (or even adding) during
> migration is valid operation or it's a bug.
There's a very basic problem though: list of RAMBlock's on source and
destination must match otherwise destination will be confused.
It is probably fixable: keep a fake RAMBlock around until migration is
complete, and send some kind of "RAMBlock removed" message to
destination so it knows to remove it there as well.
--
MST
next prev parent reply other threads:[~2020-01-07 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 7:41 [RFC PATCH 0/1] Removing RAMBlocks during migration Yury Kotov
2019-12-09 7:41 ` [RFC PATCH 1/1] migration: Remove vmstate_unregister_ram Yury Kotov
2019-12-11 11:16 ` [RFC PATCH 0/1] Removing RAMBlocks during migration Dr. David Alan Gilbert
2019-12-23 8:51 ` Yury Kotov
2020-01-03 11:44 ` Dr. David Alan Gilbert
2020-01-07 20:08 ` Michael S. Tsirkin
2020-01-08 10:24 ` Dr. David Alan Gilbert
2020-01-13 14:18 ` Yury Kotov
2020-01-07 20:02 ` Michael S. Tsirkin [this message]
2020-01-08 13:40 ` Juan Quintela
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=20200107145914-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yc-core@yandex-team.ru \
--cc=yury-kotov@yandex-team.ru \
/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.