[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus valu
Re: [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus value.
Tue, 14 Jul 2009 12:16:55 +0200
On 14.07.2009, at 11:32, Gleb Natapov wrote:
On Tue, Jul 14, 2009 at 11:21:53AM +0200, Filip Navara wrote:
On Tue, Jul 14, 2009 at 10:38 AM, Jes Sorensen<address@hidden> wrote:
On 07/09/2009 11:57 PM, Anthony Liguori wrote:
These changes make my Ubuntu server guest very unhappy. I get a
of messages about "Not responding." on startup.
If nothing else, maxcpus ==smp_cpus under QEMU because we don't
hotplug (and I don't think we should).
Sorry haven't gotten back to you earlier as I was on vacation. Are
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
have the larger CPU table in the DSDT.
BTW, many other guests complain when ACPI describes more processors
than actually present in machine. That's why I implemented the
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.
Yeah, last time I tried MacOS X was happy with more CPU descriptions
than actual CPUs too as long as they were in disabled state. Has
anything changed there I should know about?