From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: can't boot dom0
Date: Thu, 6 Oct 2005 08:58:16 +0100 [thread overview]
Message-ID: <623652d50510060058p30ecd783i@mail.gmail.com> (raw)
In-Reply-To: <364032b989f0c3bc7a785c4b0594d1f1@cl.cam.ac.uk>
On 05/10/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 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.
next prev parent reply other threads:[~2005-10-06 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 15:15 AW: can't boot dom0 Stephan Böni
2005-10-05 18:32 ` Chris Bainbridge
2005-10-05 21:56 ` Keir Fraser
2005-10-06 7:58 ` Chris Bainbridge [this message]
2005-10-06 9:15 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 14:55 Chris Bainbridge
2005-10-05 15:13 ` Chris Bainbridge
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=623652d50510060058p30ecd783i@mail.gmail.com \
--to=chris.bainbridge@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.