From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, ehabkost@redhat.com, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vl.c: make sure maxcpus matches topology to prevent migration failure
Date: Fri, 24 Aug 2018 11:13:50 +0200 [thread overview]
Message-ID: <20180824111350.04d10250@redhat.com> (raw)
In-Reply-To: <fb74bf2d-6973-9c2d-d799-8d16561c0265@redhat.com>
On Thu, 23 Aug 2018 18:32:41 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 23/08/2018 16:51, Igor Mammedov wrote:
> > Topology (threads*cores*sockets) must match maxcpus to be valid,
> > otherwise we could start QEMU with invalid topology that throws
> > a error on migration destination side, that should not be reachable:
> > Source:
> > -smp 8,maxcpus=64,cores=1,threads=8,sockets=1
> > // hotplug cpus upto maxcpus
> > Destination:
> > -smp 64,maxcpus=64,cores=1,threads=8,sockets=1
> > qemu: cpu topology: sockets (1) * cores (1) * threads (8) < smp_cpus (64)
This destination CLI aren't exactly correct as well since
it should've been exactly the same -smp as on source + a bunch of -device cpufoo...
so we can always say go fix your CLI so it won't trigger error.
> The destination should have sockets=8, shouldn't it?
either that or cores=8 or cores=4,sockets=2 ...
> It seems to me that, at startup, you should have cpus = s*t*c and cpus
> <= maxcpus. Currently we check cpus <= s*t*c <= maxcpus, which doesn't
> make much sense.
I think that s*t*c should describe topology of whole machine
including not yet plugged vcpus. "cpus = s*t*c" probably won't work
for partially filled package case:
-smp 1,cores=1,threads=8,sockets=1
cores/threads should reflect full package configuration
for guest to see an expected topology.
> Paolo
>
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > ---
> > vl.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/vl.c b/vl.c
> > index 16b913f..2b35e0c 100644
> > --- a/vl.c
> > +++ b/vl.c
> > @@ -1238,10 +1238,10 @@ static void smp_parse(QemuOpts *opts)
> > exit(1);
> > }
> >
> > - if (sockets * cores * threads > max_cpus) {
> > + if (sockets * cores * threads != max_cpus) {
> > error_report("cpu topology: "
> > - "sockets (%u) * cores (%u) * threads (%u) > "
> > - "maxcpus (%u)",
> > + "sockets (%u) * cores (%u) * threads (%u) not equal to"
> > + " maxcpus (%u)",
> > sockets, cores, threads, max_cpus);
> > exit(1);
> > }
> >
>
next prev parent reply other threads:[~2018-08-24 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 14:51 [Qemu-devel] [PATCH] vl.c: make sure maxcpus matches topology to prevent migration failure Igor Mammedov
2018-08-23 16:32 ` Paolo Bonzini
2018-08-23 18:03 ` Eduardo Habkost
2018-08-24 9:15 ` Igor Mammedov
2018-08-27 11:21 ` Andrew Jones
2018-08-24 9:13 ` Igor Mammedov [this message]
2018-08-24 11:11 ` Eduardo Habkost
2018-08-24 11:26 ` Igor Mammedov
2018-08-24 13:53 ` Eduardo Habkost
2018-08-24 14:03 ` [Qemu-devel] [libvirt] " Daniel P. Berrangé
2018-08-24 15:24 ` [Qemu-devel] " 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=20180824111350.04d10250@redhat.com \
--to=imammedo@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).