[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [DOC] Update item on FAQ


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Molle Bestefich <molle.bestefich@xxxxxxxxx>
  • Date: Fri, 18 Nov 2005 18:13:00 +0100
  • Delivery-date: Fri, 18 Nov 2005 17:12:59 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dpdGQ060pO7mwdBZcMSC6F7mFG88819vdFxb0DR9UcXuBRyAAN8EAn+A4wCy391pNyWIW1d6l8X9CErTABxg60/tpvBjxMrvKj3VH2l/YVGSXafTuycEhkUg8926/24dcTZQ1A+mwO9VJYxwg3W6rMZwYmQfp68ZYKHkzeXTF1E=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.

Anthony Liguori wrote:
> It actually decompresses the initrd before passing it to the kernel.

Presumably that's also why initramfs images doesn't work.
Extremely unhelpful of Xen to not at least bark out an error message
if un-gzipping fails.

(I've spent 4-5 hours today just looking at the darn thing, trying to
figure out why there's no RAM disk image at 0.  I live, I learn,
although that is a couple of hours spent in frustration that I'd like
to have back ;-).  Perhaps you guys could help some other poor lusers
out by changing this behaviour.)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.