From: Tilman Schmidt <tilman@imap.cc>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, Olaf Hering <olh@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Gabriel C <nix.or.die@googlemail.com>
Subject: Re: 2.6.22-git17 boot failure
Date: Tue, 24 Jul 2007 22:48:43 +0200 [thread overview]
Message-ID: <46A665AB.9010207@imap.cc> (raw)
In-Reply-To: <20070724191231.GA359@one.firstfloor.org>
[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]
Am 24.07.2007 21:12 schrieb Andi Kleen:
> On Tue, Jul 24, 2007 at 12:02:45PM -0700, Jeremy Fitzhardinge wrote:
>> 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.
Apparently not, given that the generated init script is mistaking
a native environment for a domU instead of a dom0.
In fact, when running 2.6.23-rc1 natively, no matter if compiled
with or without Xen support, the directory /proc/xen doesn't even
exist:
ts@xenon:~> uname -a
Linux xenon 2.6.23-rc1-testing #6 SMP PREEMPT Mon Jul 23 22:23:41 CEST 2007 i686 i686 i386 GNU/Linux
ts@xenon:~> ls -l /proc/xen/
ls: cannot access /proc/xen/: No such file or directory
ts@xenon:~>
The same holds for the non-Xen Suse kernel:
ts@xenon:~> uname -a
Linux xenon 2.6.18.8-0.5-default #1 SMP Fri Jun 22 12:17:53 UTC 2007 i686 i686 i386 GNU/Linux
ts@xenon:~> ls -l /proc/xen/
ls: cannot access /proc/xen/: No such file or directory
ts@xenon:~>
But when running Xen with the Opensuse Xen kernel as Dom0:
ts@xenon:~> uname -a
Linux xenon 2.6.18.8-0.5-xen #1 SMP Fri Jun 22 12:17:53 UTC 2007 i686 i686 i386 GNU/Linux
ts@xenon:~> ls -l /proc/xen/
total 0
-rw-r--r-- 1 root root 0 Jul 24 22:08 balloon
-r-------- 1 root root 0 Jul 24 22:08 capabilities
-r-------- 1 root root 0 Jul 24 22:01 privcmd
-r-------- 1 root root 0 Jul 24 22:08 xenbus
-rw------- 1 root root 0 Jul 24 22:01 xsd_kva
-r-------- 1 root root 0 Jul 24 22:08 xsd_port
ts@xenon:~> sudo cat /proc/xen/capabilities
root's password:
control_d
ts@xenon:~>
OTOH, the Opensuse Xen kernel vmlinuz-2.6.18.8-0.5-xen cannot even
be booted natively because GRUB complains immediately:
Error 13: Invalid or unsupported executable format
Conversely, the Xen loader flatly refuses to load a self-compiled,
Xen enabled 2.6.23-rc1 kernel as dom0, complaining:
DOM0 image is not an Xen-compatible Elf image.
So I guess the point is moot, because you cannot use the same image
as dom0 and natively, anyway.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2007-07-24 20:49 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
2007-07-24 19:15 ` Jeremy Fitzhardinge
2007-07-24 20:48 ` Tilman Schmidt [this message]
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=46A665AB.9010207@imap.cc \
--to=tilman@imap.cc \
--cc=andi@firstfloor.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
--cc=olh@suse.de \
/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.