>From the last mail:
Currently the ext3 is compiled as module, however initrd doesn't work for domU even when we add "ramdisk=" in config file. So we change ext3 to be kernel built-in, and then domU can boot up immediately.
Thanks
-Xiantao
> -----Original Message-----
> From: Jeremy Katz [mailto:katzj@xxxxxxxxxx]
> Sent: 2006年6月1日 4:52
> To: Aron Griffis
> Cc: Zhang, Xiantao; fedora-xen@xxxxxxxxxx
> Subject: Re: [Fedora-xen] FW: [IA64]We have successfully
> booteddom0/domU/domVTI (xen/ia64) on FC5
>
> On Wed, 2006-05-31 at 15:13 -0400, Aron Griffis wrote:
> > Zhang, Xiantao wrote: [Fri May 26 2006, 09:38:51AM EDT]
> > > >> - The configuration files for dom0/domU seems a big difference
> > > >> compared to xen-ia64-unstable.hg. (Why?) Currently the ext3 is
> > > >> compiled as module, however initrd doesn't work for domU even
> > > >> when we add "ramdisk=" in config file. So we change ext3 to be
> > > >> kernel built-in, and then domU can boot up immediately.
> > > >
> > > > Ok, I'll fix that in the rpm.
> > >
> > > OK.
> >
> > I added ext3 as 'y' instead of module, this is now in the
> > fedora-kernel-ia64 repo.
>
> Things are configured as they are so that we don't have configuration
> skew between Xen and non-Xen kernels as that just leads to confusion and
> tool problems down the road. What's the problem with initrds and ia64
> xen?
>
> Jeremy
