RE: [Fedora-xen] FW: [IA64]We have successfully booteddom0/domU/domVTI (xen/ia64) on FC5

[Zhang, Xiantao]

> 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:[e-mail]]
>  Sent: 2006年6月1日 4:52
>  To: Aron Griffis
>  Cc: Zhang, Xiantao; fedora-xen(a)redhat.com
>  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

FW: [IA64]We have successfully booteddom0/domU/domVTI (xen/ia64) on FC5

[Aron Griffis]

Zhang, Xiantao wrote:  [Wed May 31 2006, 10:21:12PM EDT]
>  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. 
Could you provide more details how you're configuring it to use the
initrd?

Aron

FW: [IA64]We have successfully booteddom0/domU/domVTI (xen/ia64) on FC5

[Jeremy Katz]

On Thu, 2006-06-01 at 10:21 +0800, Zhang, Xiantao wrote:
>  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. 
Right -- my question was why don't initrds work.  This is really a
requirement given how some of the early boot process works.  There are
ways you can hack around it, but they'll always be just that, a hack.

Jeremy

FW: [IA64]We have successfullybooteddom0/domU/domVTI (xen/ia64) on FC5

[Akio Takebe]

Hi, Jeremy

I made a patch to support initrd of domU.
I think it work good in the case of using xen-ia64-usntable.

I'm checking fedora-xen-ia64 now, please wait.
If necessary, I'll make a patch. :-)

Best Regards,

Akio Takebe

> On Thu, 2006-06-01 at 10:21 +0800, Zhang, Xiantao wrote:
> > 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.
>
> Right -- my question was why don't initrds work.  This is really a
> requirement given how some of the early boot process works.  There are
> ways you can hack around it, but they'll always be just that, a hack.
>
> Jeremy
>
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen