lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A665AB.9010207@imap.cc>
Date:	Tue, 24 Jul 2007 22:48:43 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>, Olaf Hering <olh@...e.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Gabriel C <nix.or.die@...glemail.com>
Subject: Re: 2.6.22-git17 boot failure

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@...on:~> 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@...on:~> ls -l /proc/xen/
ls: cannot access /proc/xen/: No such file or directory
ts@...on:~>

The same holds for the non-Xen Suse kernel:

ts@...on:~> 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@...on:~> ls -l /proc/xen/
ls: cannot access /proc/xen/: No such file or directory
ts@...on:~>

But when running Xen with the Opensuse Xen kernel as Dom0:

ts@...on:~> 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@...on:~> 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@...on:~> sudo cat /proc/xen/capabilities
root's password:
control_d
ts@...on:~>

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@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ