public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Tilman Schmidt <tilman@imap.cc>, Olaf Hering <olh@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Gabriel C <nix.or.die@googlemail.com>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: 2.6.22-git17 boot failure
Date: Tue, 24 Jul 2007 21:12:31 +0200	[thread overview]
Message-ID: <20070724191231.GA359@one.firstfloor.org> (raw)
In-Reply-To: <46A64CD5.2030800@goop.org>

On Tue, Jul 24, 2007 at 12:02:45PM -0700, Jeremy Fitzhardinge wrote:
> Tilman Schmidt wrote:
> > Alright, I know what's going on now, and it looks like a problem with
> > the Opensuse init script. In fact, the initrd for the Xen enabled
> > kernel got a *different* init script than the one for the non-Xen one.
> > The difference being:
> >   
> 
> Phew, I was getting worried there for a minute.  Does the install script
> check for CONFIG_XEN in the kernel config or something?

Yes 10.2 mkinitrd does. But it still should work because a dom0
kernel would obviously need all the drivers. A paravirt ops
kernel native is like a dom0 variant.

http://firstfloor.org/~andi/mkinitrd

-Andi

  reply	other threads:[~2007-07-24 19:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 23:47 2.6.22-git17 boot failure Tilman Schmidt
2007-07-23  0:31 ` Gabriel C
2007-07-23  0:52 ` Tilman Schmidt
2007-07-23  8:51   ` Jeremy Fitzhardinge
2007-07-23 10:25     ` Tilman Schmidt
2007-07-23 14:51       ` Jeremy Fitzhardinge
2007-07-23 19:42         ` Tilman Schmidt
2007-07-23 20:32           ` Jeremy Fitzhardinge
2007-07-23 23:02             ` Tilman Schmidt
2007-07-24  0:14               ` Jeremy Fitzhardinge
2007-07-24  8:51                 ` Tilman Schmidt
2007-07-24  8:59                   ` Jeremy Fitzhardinge
2007-07-24  9:10                 ` Andi Kleen
2007-07-24  9:56                   ` Olaf Hering
2007-07-24 10:36                     ` Tilman Schmidt
2007-07-24 13:45                       ` Olaf Hering
2007-07-24 15:45                         ` Jeremy Fitzhardinge
2007-07-24 15:47                           ` Andi Kleen
2007-07-24 18:08                     ` Tilman Schmidt
2007-07-24 19:02                       ` Jeremy Fitzhardinge
2007-07-24 19:12                         ` Andi Kleen [this message]
2007-07-24 19:15                           ` Jeremy Fitzhardinge
2007-07-24 20:48                           ` Tilman Schmidt
2007-07-24 21:20                             ` Jeremy Fitzhardinge
2007-07-24  3:46               ` Jeremy Fitzhardinge
2007-07-23  9:25   ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23  0:27 Sid Boyce

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=20070724191231.GA359@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@googlemail.com \
    --cc=olh@suse.de \
    --cc=tilman@imap.cc \
    /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