[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] can't boot dom0

  • To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
  • Date: Thu, 6 Oct 2005 08:58:16 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 06 Oct 2005 07:56:51 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=f1zdomQ+RGgYvB8BuDeUB8nR4yTsA+/3h0Bwyv935eyPsH9b/NH3ogQdHr1OA+N9gG0xx2cSh4VA+1OXElPz9Ag6GwWvD8CzzLIu2T+/kjXbSWqCQS4syaSVju1oEATKgiJVNAPekPg4BVqiTTsfVOFfYnWLplCXZRaO9PyVaKM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 05/10/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> On 5 Oct 2005, at 19:32, Chris Bainbridge wrote:
> > Ah-ha! So it looks like you need CONFIG_X86_UP_IOAPIC or SMP to get it
> > working.
> >
> > Bug 1) xen with non apic kernel is broken
> > Bug 2) compile error with CONFIG_PCI_MSI
> Trying to boot an SMP system with a non-APIC domain0 is a recipe for
> disaster. We depend an awful lot on domain0 to get interrupt routing
> correct. If Xen has booted an SMP system, probed IO-APICs and so on,
> domain0 needs to have the same world view.
> The 'bug' is really that we don't make it harder for people to shoot
> themselves in the foot in their configuration. Possibly forcing the
> APIC options is the way to go, or at least indicate that setting them
> to N is DANGEROUS.

In my case "SMP" was just uniprocessor hyperthreading, not really SMP,
so I expected it to work. It's a non-obvious error that will trip up a
lot of people, I'd recommend forcing it, or detecting the
hypervisor/kernel SMP mismatch at boottime and printing a big warning.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.