From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Duffy Subject: Re: [DOC] Update item on FAQ Date: Fri, 18 Nov 2005 18:26:59 -0600 Message-ID: <437E7153.1070001@spamcop.net> References: <437CAB59.8060808@us.ibm.com> <437D8A68.2090306@suse.de> <437E0506.6000108@us.ibm.com> <62b0912f0511180913j37500ff5sa1457dd4d46a323d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <62b0912f0511180913j37500ff5sa1457dd4d46a323d@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: molle.bestefich@gmail.com List-Id: xen-devel@lists.xenproject.org Molle Bestefich wrote: > Gerd Knorr wrote: > >>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? > > > Another thing that's broken is initramfs (cpio) images. > Results in "RAMDISK: Couldn't find valid RAM disk image starting at > 0", every time. No -- I've been using those with xen.unstable for quite some time, and they work fine. Linux copes nicely with these whether or not they're gzipped. Well, sort of fine; they're very twitchy about the cpio format, but that's the case upstream as well. For instance, the cpio image *absolutely must* include . (as opposed to just containing the files under its root directory), and there are only two cpio format variants that are supported (I use newc).