WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [XenPPC] DOM0 can not be set up

To: Christian Ehrhardt <ehrhardt@xxxxxxxxxxxxxxxxxx>
Subject: Re: [XenPPC] DOM0 can not be set up
From: Jun Hui Bu <bujunhui@xxxxxxxxxx>
Date: Sun, 12 Aug 2007 00:32:44 +0800
Cc: Hollis Blanchard <hollisb@xxxxxxxxxx>, xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 11 Aug 2007 09:26:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46BDD365.80200@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx

Thank you!

>
> > I am attempting to boot Xen/Dom0 instead of the installed Linux kernel.
> > Since the boot loaded is yaboot, I added a new entry in
> > /etc/yaboot.conf that boots Xen instead.
> >
> >
> > > I've never used yaboot to boot Xen, but please paste your "xen" yaboot
> > > config. I find this interesting in particular:
> > > > boot_of_module: Dom0 was loaded and found using r3/r4:
> > > 0xf00000[size 0x35d000]
> > > > mod0: 63 L 3 Ì
> > > > boot_of_module: dom0 mod @ 0x0000000000f00000[0x125d000]
> > >
> > > That "mod0" output looks suspicious if it's supposed to be an ELF
> > > file...
> > >
> >
> > The "xen" yaboot is:
> >
> > image = /boot/xen
> > label = xen
> > root = /dev/disk/by-id/ata-TOSHIBA_MK4019GAXB_93SK3653T-part3
> > initrd = /boot/zImage.initrd
> >
> > And also, the original yaboot is:
> >
> > image = /boot/vmlinux-2.6.16.46-0.12-ppc64
> > label = linux
> > root = /dev/disk/by-id/ata-TOSHIBA_MK4019GAXB_93SK3653T-part3
> > initrd = /boot/initrd-2.6.16.46-0.12-ppc64
> >
> Hi,
> I always used yaboot to boot xenppc, the default configuration you used
> with xen_maple_defconfig does not need an initrd so my yaboot looked
> like this:
>
>   boot=/dev/sda1
>   label = xen
>   image = /boot/xen
>
> To build without initrd I always used this commands:
>   make ARCH=powerpc O=../xen mrproper
>   make ARCH=powerpc O=../xen xen_maple_defconfig
>   make ARCH=powerpc O=../xen menuconfig
>   make -j5 ARCH=powerpc O=../xen all
>   make O=../xen modules_install
>
> And afterwards to build xen:
>   make debug=y optimize=0 crash_debug=y CMDLINE="noreboot debug loglvl=7
> debug=7 -- root=/dev/sda6 debug loglevel=7"
> DOM0_IMAGE=~/xen_2.6.18/xen-unstable.hg/linux-2.6.18-xen.
> hg/arch/powerpc/boot/zImage
>
> You may remove all the loglevel&debug stuff, but give it a try without
> initrd and my build commands.
> If it still does not work add all the debug&loglevel stuff and attach
> the complete output of the boot process, maybe we see more in that one.
>
> --
>
> Grüsse / regards,
> Christian Ehrhardt
>
> IBM Linux Technology Center, Open Virtualization
> +49 7031/16-3385
> Ehrhardt@xxxxxxxxxxxxxxxxxx
> Ehrhardt@xxxxxxxxxx
>
> IBM Deutschland Entwicklung GmbH
> Vorsitzender des Aufsichtsrats: Johann Weihen
> Geschäftsführung: Herbert Kircher
> Sitz der Gesellschaft: Böblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>

Hi,

It works now. Thank you very much!!!

The problem was caused by the ramdisk.image...


_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel
<Prev in Thread] Current Thread [Next in Thread>