Hi,
On Sat, Apr 26, 2008 at 12:41 PM, Rob Greene <robgreene@xxxxxxxxx> wrote:
> On Fri, Apr 25, 2008 at 1:06 AM, Michael Jinks <mjinks@xxxxxxxxxxxx> wrote:
>
> > Hi, Rob.
> >
> > I'm a confused newbie too but I think I can help with this one...
>
> Glad to have some company! :-)
>
> > This all looks fine to me, but there's no 'ramdisk' line, and I bet the
> > el5 kernel stores its block drivers in its ramdisk (or not; see below).
> > Alongside wherever you got your kernel, there should be a file named
> > something like "initrd-[same exact version string].img". Copy it into
> > the same area where you're storing your Xen kernel, and add
> >
> >
>
> That's what I find funny. The VM images I create do not require an external
> kernal/initrd (except for installation). Why would these images (from
> jailtime.org) that are built to be used by Xen require them? I should just
> be able to use pygrub and go from there...
>
I agree the the jailtime.org images would be nice as ready to be used
with pygrub, but that would required putting a working, compatible
kernel within the image. This is possible, but sometimes tricky. You
should contact the jailtime.org admin, he is usually pretty good about
trying to add images and features.
There is at least one alternative that I am familiar with, rpath.com
has quite a few prebuilt images, some of which are designed to work
with pygrub out of the box. We covered how to do this in our book, but
(if you can't or don't want to buy the book) we have also provided a
fair number of resources on our website for the book as well.
For some ideas and other places to get prebuilt images See:
http://runningxen.com/chapters/chapter5/
Cheers,
Todd
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users