From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Knorr <kraxel@suse.de>
Subject: Re: [DOC] Update item on FAQ
Date: Fri, 18 Nov 2005 09:01:44 +0100
Message-ID: <437D8A68.2090306@suse.de>
References: <437CAB59.8060808@us.ibm.com>
	<Prayer.1.0.16.0511172030470.1562@hermes-1.csi.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <Prayer.1.0.16.0511172030470.1562@hermes-1.csi.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: mark.williamson@cl.cam.ac.uk
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

>> "Some distros (notably SLES9) have a mkinitrd that adds garbage to the 
>> end of the initrd.  These initrds will not work with Xen.  To correct 
>> this problem, you should gunzip the initrd, and then gzip it again."
> 
> !?!?!
> 
> What's in the garbage?  Presumably it's there for some reason?

Sure it is, it is the image for the fancy console screen.  Doesn't hurt 
when it isn't present.  And as vesafb doesn't work with xenified linux 
kernels it isn't used anyway.  Easiest way to permanently get rid of it 
is "rpm -e bootsplash" (i.e. mkinitrd will stop appending the image to 
the initrd then).  Nevertheless I don't see why it causes trouble, the 
domain builder should simply take the ramdisk blob and pass it as-is to 
the kernel, no?

   Gerd