From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vl.c: make sure maxcpus matches topology to prevent migration failure
Date: Thu, 23 Aug 2018 15:03:07 -0300 [thread overview]
Message-ID: <20180823180307.GQ3778@localhost.localdomain> (raw)
In-Reply-To: <fb74bf2d-6973-9c2d-d799-8d16561c0265@redhat.com>
On Thu, Aug 23, 2018 at 06:32:41PM +0200, Paolo Bonzini 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)
>
> The destination should have sockets=8, shouldn't it?
>
> 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.
Most of the incompleteness of input validation at smp_parse() can
be explained by our fear of breaking existing configurations and
making existing running VMs not runnable.
But now we have a deprecation policy. If we're still afraid of
breaking peoples' existing configurations, we should at least
deprecate those configurations as soon as possible (and make QEMU
at least emit a warning).
--
Eduardo
next prev parent reply other threads:[~2018-08-23 18:03 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 [this message]
2018-08-24 9:15 ` Igor Mammedov
2018-08-27 11:21 ` Andrew Jones
2018-08-24 9:13 ` Igor Mammedov
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=20180823180307.GQ3778@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@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 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.