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

[Zhang, Xiantao]

Due to picture size exceeding limitation of mailing list, it's waiting for approval now. So, send out notification first for your reference. :-)

Thanks
-Xiantao

-----Original Message-----
From: Zhang, Xiantao 
Sent: 2006年5月26日 16:24
To: fedora-xen at redhat.com
Subject: [IA64]We have successfully booted dom0/domU/domVTI (xen/ia64) on FC5 

Hi, all,
	After some hard debug and work around, now we've got xen/ia64 dom0/domU/domVTI both up on FC5-IA64. Attached is the snapshot.

	We still use python2.4.2 contained in FC5 for test. 

	We need following changes to make things happen:

	- xen-tools is not built and integrated into the RPM package. Typically we know there're 3 major directories on xen-ia64-unstable.hg: xen,linux-sparse and tools. All three need to be kept consistence with each other. However current fedora-kernel-ia64 only incorporates former two and tools is totally missed. We tried to build the tools individually from xen-ia64-unstable under same Rev (10150), and then install to target box manually. 

	- 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.
		* 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.

	After above 2 changes, both domU and domVTI can be boot successfully.

	Following are other tricky issues we've observed:
	- brctl package is not integrated into FC5 and so vnif is not available now. People need to install brctl manually and we'll try network later. Is it possible to add dependency check upon brctl in spec file?

	- When installing xen0 rpm package, it depends on xen rpm package. However we didn't find the xen rpm package, and had to install with "nodeps". Actually xen image has been included in xen0 rpm package.

	- Is it possible to use same configuration file for xen0/xenU just like current xen-ia64-unstable.hg? Or at least give a configuration option to user in spec.

	- Even everything works now, we kept seeing some boring call trace from BUG in mm/slab.c:2818, especially when vncserver is started. Actually even dom0 itself will encounter such warning infrequently before xend start.

Cheers!
-Xiantao and Kevin