This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Continuing problems booting

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: Continuing problems booting
From: M A Young <m.a.young@xxxxxxxxxxxx>
Date: Fri, 6 Mar 2009 01:07:48 +0000 (GMT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxx>
Delivery-date: Thu, 05 Mar 2009 17:08:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49B03772.8090602@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.GSO.2.00.0902201239010.757@xxxxxxxxxxxxxxxx> <alpine.GSO.2.00.0902201554500.757@xxxxxxxxxxxxxxxx> <alpine.LFD.2.00.0902211225540.14632@xxxxxxxxxxxxxxx> <49A0F68D.9070306@xxxxxxxx> <alpine.LFD.2.00.0902220922040.4149@xxxxxxxxxxxxxxx> <alpine.LFD.2.00.0902221449410.17196@xxxxxxxxxxxxxxx> <49A187B8.7000902@xxxxxxxx> <alpine.LFD.2.00.0902222257230.4472@xxxxxxxxxxxxxxx> <49A1DD80.1080903@xxxxxxxx> <alpine.LFD.2.00.0902222359090.4472@xxxxxxxxxxxxxxx> <49A241EC.3050300@xxxxxxxx> <alpine.LFD.2.00.0902242228550.12607@xxxxxxxxxxxxxxx> <alpine.LFD.2.00.0902272317030.17305@xxxxxxxxxxxxxxx> <49AF3059.2010403@xxxxxxxx> <alpine.LFD.2.00.0903052012410.10012@xxxxxxxxxxxxxxx> <49B03772.8090602@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (LFD 1167 2008-08-23)
On Thu, 5 Mar 2009, Jeremy Fitzhardinge wrote:

Yes, a recent update allows my qemu test environment to see its disk. It crashes later, but in what looks to be a non-xen related way. However booting the kernel non-xen crashes much faster with the traceback

RAMDISK: gzip decompressor not configured!
It looks like you need to configure gzip compression for your initrd. Also, make sure you don't use any of the other compression algorithms for the kernel itself, or Xen won't be able to parse them.

BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<(null)>] (null)

This looks like a bug. HPA, will it fall down a NULL function pointer if you leave compression out?

It now boots (xen and non-xen) if I build with CONFIG_RD_GZIP=y (and work around the problems of my current livecd generating situation). I get the impression that the boot is expected to fail if this or an equivalent CONFIG_RD_BZIP2 or CONFIG_RD_LZMA setting, but it should do so more gracefully so I agree this is a bug.

        Michael Young

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>