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

Hi Aron, 
> -----Original Message-----
> From: Aron Griffis [mailto:aron@hp.com]
> Sent: 2006年6月1日 3:13
> To: Zhang, Xiantao
> Cc: fedora-xen@redhat.com
> Subject: Re: [Fedora-xen] FW: [IA64]We have successfully booted
> dom0/domU/domVTI (xen/ia64) on FC5
> 
> 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.
> 
> > >> 	- Xen-ia64-unstable.hg doesn''t have IDE devices
configured for
> > >> 	domU, however fedora-kernel-ia64 does, which wastes much
time
> > >> 	for probe. If the configuration file can be kept consistence
> > >> 	with xen-ia64-unstable.hg, above issues are gone.
> > > That''s my mistake too.  I''ll fix it.
> > OK too:)
> 
> On investigation, I don''t see IDE configured for the xenU kernel.
> Could you point out the specific problem, or send a patch to the
> config?
I saw the issue was fixed by CSet 33. Did you encounter it after Cset 33? :)
> Thanks,
> Aron

Zhang, Xiantao wrote:  [Wed May 31 2006, 10:17:41PM EDT]
> I saw the issue was fixed by CSet 33. Did you encounter it after
> Cset 33? :)
Cset 33 was a huge screwup of mine.  Somehow I saved a kernel with
CONFIG_XEN *unset* as the xenU config.  I reverted it in cset 34 but
disabled some other hardware that obviously won''t be available in an
unprivileged environment.

Please look at the config in cset 34 and let me know if I missed
something.

Aron