From: Gleb Natapov <gleb@redhat.com>
To: Filip Navara <filip.navara@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Jes Sorensen <jes@sgi.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus value.
Date: Tue, 14 Jul 2009 12:32:29 +0300 [thread overview]
Message-ID: <20090714093229.GX28046@redhat.com> (raw)
In-Reply-To: <5b31733c0907140221l3c2b6b3an1e5ebf79eaeef703@mail.gmail.com>
On Tue, Jul 14, 2009 at 11:21:53AM +0200, Filip Navara wrote:
> On Tue, Jul 14, 2009 at 10:38 AM, Jes Sorensen<jes@sgi.com> wrote:
> > On 07/09/2009 11:57 PM, Anthony Liguori wrote:
> >>
> >> These changes make my Ubuntu server guest very unhappy. I get a bunch
> >> of messages about "Not responding." on startup.
> >>
> >> If nothing else, maxcpus ==smp_cpus under QEMU because we don't do CPU
> >> hotplug (and I don't think we should).
> >
> > Anthony,
> >
> > Sorry haven't gotten back to you earlier as I was on vacation. Are you
> > saying the Ubuntu kernel doesn't like having more CPU entries in the
> > ACPI table than it actually boots on?
> >
> > Does the same guest boot using an older KVM setup? Curious since it does
> > have the larger CPU table in the DSDT.
> >
> > Cheers,
> > Jes
> >
>
> BTW, many other guests complain when ACPI describes more processors
> than actually present in machine. That's why I implemented the dynamic
> DSDT generation in Bochs BIOS in the first place. One that comes to
> mind is MacOS X, or the Darwin kernel respectively.
>
There is nothing wrong in describing more processors than actually
present. The disable flag is defined by ACPI for a reason. My real HW
IBM server does this.
--
Gleb.
next prev parent reply other threads:[~2009-07-14 9:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 8:35 [Qemu-devel] [patch 0/2] QEMU maxcpus support v2 Jes Sorensen
2009-06-24 8:35 ` [Qemu-devel] [patch 1/2] Introduce -smp , maxcpus= flag to specify maximum number of CPUS Jes Sorensen
2009-06-24 9:02 ` [Qemu-devel] " Avi Kivity
2009-06-24 9:02 ` Jes Sorensen
2009-06-24 9:15 ` Avi Kivity
2009-06-24 12:04 ` Jes Sorensen
2009-06-24 8:35 ` [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
2009-07-09 21:57 ` Anthony Liguori
2009-07-12 9:39 ` Avi Kivity
2009-07-12 13:23 ` Anthony Liguori
2009-07-12 13:36 ` Avi Kivity
2009-07-14 8:38 ` Jes Sorensen
2009-07-14 9:21 ` Filip Navara
2009-07-14 9:32 ` Gleb Natapov [this message]
2009-07-14 10:16 ` Alexander Graf
2009-07-14 11:15 ` Filip Navara
2009-07-14 11:21 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2009-07-23 15:03 [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v4 Jes Sorensen
2009-07-23 15:03 ` [Qemu-devel] [PATCH 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
2009-07-20 14:43 [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v3 Jes Sorensen
2009-07-20 14:43 ` [Qemu-devel] [PATCH 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
2009-07-14 12:53 [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v2 Jes Sorensen
2009-07-14 12:53 ` [Qemu-devel] [PATCH 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
2009-06-23 10:00 [Qemu-devel] [patch 0/2] QEMU maxcpus support Jes Sorensen
2009-06-23 10:00 ` [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
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=20090714093229.GX28046@redhat.com \
--to=gleb@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=filip.navara@gmail.com \
--cc=jes@sgi.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).