-----Original Message-----
From: Magenheimer, Dan (HP Labs Fort Collins)
Sent: Thursday, November 10, 2005 8:31 AM
To: 'Tian, Kevin'
Cc: xen-...@lists.xensource.com
Subject: RE: [Xen-ia64-devel] RE: OK, now domU can boot on tip. ;-)
Actually what confusing me is how to support different
configuration file copied to xen0_defconfig_ia64
automatically when build. Current xen0_defconfig_ia64 is
based on zx box configuration, and I have to copy one for
tiger manually to override that file before build. However I
didn't find easy way to pass into such machvec information
and let it automate. Can anyone help with an idea?
I've been thinking that linux/arch/ia64/defconfig might
work for both HP and tiger4, but since it uses many modules,
I have been waiting to try it until the boot-dom0-with-initrd
works (RHEL4).
Perhaps just changing all the =m to =y in linux/arch/ia64/defconfig
will work for a xen0_defconfig_ia64 for both HP and tiger4?
I tried using linux-2.6.12/arch/ia64/defconfig with edits to
add CONFIG_XEN=y and change CONFIG_IA32_SUPPORT=n and changing
all =m to =y. The resultant xenlinux runs successfully as
dom0 though it is much bigger and boots slower. However,
it crashes when booting as domU. Since we can probably
reduce the config file for domU significantly, this is
unlikely to be a problem once we have a default domU config.
Could you confirm that defconfig with the above changes works
for tiger4? If so, we can replace the zx1-specific config in
sparse/arch/xen/configs/.
Dan
10 messages in com.xensource.lists.xen-ia64-develRE: [Xen-ia64-devel] RE: OK, now domU...
.file