From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>,
marcandre.lureau@redhat.com, maxime.coquelin@redhat.com
Cc: Peng Hao <peng.hao2@zte.com.cn>,
Wang Yechao <wang.yechao255@zte.com.cn>,
qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vhost: fix a migration failed because of vhost region merge
Date: Wed, 19 Jul 2017 12:46:13 +0100 [thread overview]
Message-ID: <20170719114612.GC3500@work-vm> (raw)
In-Reply-To: <20170719095058.4d46359d@Igors-MacBook-Pro.local>
* Igor Mammedov (imammedo@redhat.com) wrote:
> On Wed, 19 Jul 2017 23:17:32 +0800
> Peng Hao <peng.hao2@zte.com.cn> wrote:
>
> > When a guest that has several hotplugged dimms is migrated, in
> > destination host it will fail to resume. Because vhost regions of
> > several dimms in source host are merged and in the restore stage
> > in destination host it computes whether more than vhost slot limit
> > before merging vhost regions of several dimms.
> could you provide a bit more detailed description of the problem
> including command line+used device_add commands on source and
> command line on destination?
(ccing in Marc Andre and Maxime)
Hmm, I'd like to understade the situation where you get merging between
RAMBlocks; that complicates some stuff for postcopy.
> >
> > 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 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/hw/mem/pc-dimm.c b/hw/mem/pc-dimm.c
> > index ea67b46..bb0fa08 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() && runstate_is_running()) {
> > error_setg(&local_err, "a used vhost backend has no free"
> > " memory slots left");
> > goto out;
Even this produces the wrong error message in this case,
it also makes me think if the existing code should undo a lot of
the object_property_set's that happen.
Dave
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-07-19 11:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 15:17 [Qemu-devel] [PATCH] vhost: fix a migration failed because of vhost region merge Peng Hao
2017-07-19 7:50 ` Igor Mammedov
2017-07-19 11:46 ` Dr. David Alan Gilbert [this message]
2017-07-19 13:24 ` Igor Mammedov
2017-07-19 15:52 ` Michael S. Tsirkin
2017-07-20 17:22 ` Dr. David Alan Gilbert
2017-07-21 19:49 ` Michael S. Tsirkin
2017-07-24 8:06 ` Dr. David Alan Gilbert
2017-07-24 10:46 ` Igor Mammedov
2017-07-21 14:41 ` Igor Mammedov
2017-07-21 21:30 ` Michael S. Tsirkin
2017-07-24 10:05 ` Igor Mammedov
2017-07-24 13:01 ` Igor Mammedov
2017-07-19 8:36 ` no-reply
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=20170719114612.GC3500@work-vm \
--to=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@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.