From: "Radim Krčmář" <rkrcmar@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 0/3] Improve error message on invalid CPU topologies
Date: Wed, 5 Nov 2014 22:53:30 +0100 [thread overview]
Message-ID: <1415224413-13972-1-git-send-email-rkrcmar@redhat.com> (raw)
A not-a-bug reported that QEMU fails when cores=6,maxcpus=240,
https://bugzilla.redhat.com/show_bug.cgi?id=1159264
The error message is
qemu-kvm: max_cpus is too large. APIC ID of last CPU is 317
Misconfiguration, but how large can maxcpus be?
There probably aren't many QEMU users with knowledge about initial APIC ID
assignment, so it would be better to prevent confusion by making the error
message more accessible. Especially since big VMs are spreading.
Output after this patch is
qemu-kvm: invalid CPU topology: maxcpus can't exceed 192 if cores=6 and threads=1
Looking for better wording ...
(The main problem of this series is benefit/code ratio.)
Radim Krčmář (3):
target-i386: add apicid_pkg_width to topology.h
target-i386: introduce x86_cpu_nr_apic_ids
pc: improve error message with impossible max_cpus
hw/i386/pc.c | 12 +++++++-----
target-i386/cpu.c | 16 ++++++++++++++++
target-i386/cpu.h | 1 +
target-i386/topology.h | 13 +++++++++++++
tests/test-x86-cpuid.c | 9 +++++++++
5 files changed, 46 insertions(+), 5 deletions(-)
--
2.1.0
next reply other threads:[~2014-11-05 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 21:53 Radim Krčmář [this message]
2014-11-05 21:53 ` [Qemu-devel] [PATCH 1/3] target-i386: add apicid_pkg_width to topology.h Radim Krčmář
2014-11-05 21:53 ` [Qemu-devel] [PATCH 2/3] target-i386: introduce x86_cpu_nr_apic_ids Radim Krčmář
2014-11-05 21:53 ` [Qemu-devel] [PATCH 3/3] pc: improve error message on invalid topologies Radim Krčmář
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=1415224413-13972-1-git-send-email-rkrcmar@redhat.com \
--to=rkrcmar@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).