From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Peng Hao <peng.hao2@zte.com.cn>,
Wang Yechao <wang.yechao255@zte.com.cn>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2] vhost: fix a migration failed because of vhost region merge
Date: Mon, 24 Jul 2017 23:50:00 +0300 [thread overview]
Message-ID: <20170724234849-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170724111419.720aa168@nial.brq.redhat.com>
On Mon, Jul 24, 2017 at 11:14:19AM +0200, Igor Mammedov wrote:
> On Sun, 23 Jul 2017 20:46:11 +0800
> Peng Hao <peng.hao2@zte.com.cn> wrote:
>
> > When a guest that has several hotplugged dimms is migrated, on
> > destination it will fail to resume. Because regions on source
> > are merged and on destination the order of realizing devices
> > is different from on source with dimms, so when part of devices
> > are realizd some region can not be merged.That may be more than
> > vhost slot limit.
> >
> > Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> > Signed-off-by: Wang Yechao <wang.yechao255@zte.com.cn>
> > ---
> > hw/mem/pc-dimm.c | 2 +-
> > include/sysemu/sysemu.h | 1 +
> > vl.c | 5 +++++
> > 3 files changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/mem/pc-dimm.c b/hw/mem/pc-dimm.c
> > index ea67b46..13f3db5 100644
> > --- a/hw/mem/pc-dimm.c
> > +++ b/hw/mem/pc-dimm.c
> > @@ -101,7 +101,7 @@ void pc_dimm_memory_plug(DeviceState *dev, MemoryHotplugState *hpms,
> > goto out;
> > }
> >
> > - if (!vhost_has_free_slot()) {
> > + if (!vhost_has_free_slot() && qemu_is_machine_init_done()) {
> > error_setg(&local_err, "a used vhost backend has no free"
> > " memory slots left");
> that doesn't fix issue,
> 1st: number of used entries is changing after machine_init_done() is called
> as regions continue to mapped/unmapped during runtime
But that's fine, we want hotplug to fail if we can not guarantee vhost
will work.
> 2nd: it brings regression and allows to start QEMU with number memory
> regions more than supported by backend, which combined with missing
> error handling in vhost will lead to qemu crashes or obscure bugs in
> guest breaking vhost enabled drivers.
> i.e. patch undoes what were fixed by
> https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg00789.html
Why does it? The issue you fixed there is hotplug, and that means
pc_dimm_memory_plug called after machine done.
>
> > goto out;
> > diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
> > index b213696..48228ad 100644
> > --- a/include/sysemu/sysemu.h
> > +++ b/include/sysemu/sysemu.h
> > @@ -88,6 +88,7 @@ void qemu_system_guest_panicked(GuestPanicInformation *info);
> > void qemu_add_exit_notifier(Notifier *notify);
> > void qemu_remove_exit_notifier(Notifier *notify);
> >
> > +bool qemu_is_machine_init_done(void);
> > void qemu_add_machine_init_done_notifier(Notifier *notify);
> > void qemu_remove_machine_init_done_notifier(Notifier *notify);
> >
> > diff --git a/vl.c b/vl.c
> > index fb6b2ef..43aee22 100644
> > --- a/vl.c
> > +++ b/vl.c
> > @@ -2681,6 +2681,11 @@ static void qemu_run_exit_notifiers(void)
> >
> > static bool machine_init_done;
> >
> > +bool qemu_is_machine_init_done(void)
> > +{
> > + return machine_init_done;
> > +}
> > +
> > void qemu_add_machine_init_done_notifier(Notifier *notify)
> > {
> > notifier_list_add(&machine_init_done_notifiers, notify);
next prev parent reply other threads:[~2017-07-24 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 12:46 [Qemu-devel] [PATCH V2] vhost: fix a migration failed because of vhost region merge Peng Hao
2017-07-24 9:14 ` Igor Mammedov
2017-07-24 20:50 ` Michael S. Tsirkin [this message]
2017-07-25 8:44 ` Igor Mammedov
2017-07-25 19:47 ` Michael S. Tsirkin
2017-07-26 14:05 ` Igor Mammedov
2017-07-26 16:01 ` Michael S. Tsirkin
2017-07-28 9:19 ` Igor Mammedov
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=20170724234849-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=peng.hao2@zte.com.cn \
--cc=qemu-devel@nongnu.org \
--cc=wang.yechao255@zte.com.cn \
/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.