RE: [Xen-ia64-devel] RE: OK, now domU can boot on tip. ;-)

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

I just ran into a problem and I think it happens when I
run xenlinux built from defconfig instead of zx1_config.
I get:

  vcpu_translate: bad physical address: a000000100009820

when I am doing a full xen+xenlinux build (and it happens
in the same place -- when doing the second mkbuildtree with
a newly created sparse/arch/xen/configs/xenU_defconfig_ia64).

The machine then reboots.

I need to rebuild xenlinux to confirm but this may make
it problematic for me to check in the new config file.

Dan


> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Wednesday, November 16, 2005 1:48 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; Zhang, Xiantao
> Subject: RE: [Xen-ia64-devel] RE: OK, now domU can boot on tip. ;-)
> 
> That works on Tiger box as dom0, by your steps:
>       * Add CONFIG_XEN
>       * Remove CONFIG_IA32_SUPPORT
>       * Change all =m to =y
> 
> However because the defconfig doesn't fit the latest Kconfig 
> content, there're many prompt when make oldconfig and I just 
> hit "Enter" to use default option for all of them.
> 
> Attached the final .config file and you may compare how much 
> difference from your one.
> 
> BTW, to make xenlinux compiled, we also need to change 
> arch/ia64/Makefile a bit. Or else duplicated inclusion to 
> arch/ia64/hp/sim/ made link failed since CONFIG_IA64_GENERIC 
> already does that:
> 
> diff -r 2f98977d9f85 linux-2.6-xen-sparse/arch/ia64/Makefile
> --- a/linux-2.6-xen-sparse/arch/ia64/Makefile Thu Nov 10 21:24:29 2005
> +++ b/linux-2.6-xen-sparse/arch/ia64/Makefile Wed Nov 16 16:24:15 2005
> @@ -60,7 +60,7 @@
>  core-$(CONFIG_IA64_HP_ZX1)   += arch/ia64/dig/
>  core-$(CONFIG_IA64_HP_ZX1_SWIOTLB) += arch/ia64/dig/
>  core-$(CONFIG_IA64_SGI_SN2)  += arch/ia64/sn/
> -core-$(CONFIG_XEN)           += arch/ia64/xen/ arch/ia64/hp/sim/
> +core-$(CONFIG_XEN)           += arch/ia64/xen/
>  
>  drivers-$(CONFIG_PCI)                += arch/ia64/pci/
>  drivers-$(CONFIG_IA64_HP_SIM)        += arch/ia64/hp/sim/
> 
> Thanks,
> Kevin
> 
> >-----Original Message-----
> >From: Magenheimer, Dan (HP Labs Fort Collins) 
> [mailto:dan.magenheimer@xxxxxx]
> >Sent: 2005å11æ16æ 4:56
> >To: Tian, Kevin
> >Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: RE: [Xen-ia64-devel] RE: OK, now domU can boot on tip. ;-)
> >
> >> -----Original Message-----
> >> From: Magenheimer, Dan (HP Labs Fort Collins)
> >> Sent: Thursday, November 10, 2005 8:31 AM
> >> To: 'Tian, Kevin'
> >> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> 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
> 

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel