Hi,

Thanks very much for your response! Really appreciate your helps!!

Hollis Blanchard <[EMAIL PROTECTED]> wrote on 2007-08-11 01:14:23:

> On Fri, 2007-08-10 at 09:56 +0800, Jun Hui Bu wrote:
> >
> > According to the instructions in Xen wiki, Xen could not set up DOM0
> > guest OS(SLES10 SP1) when try it on JS20. Would you please help take a
> > look it? Thanks a lot!
>
> How old is your source? The boot log contains this line:
> > OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc
> version 4.1.2 20070115 (prerelease) (SUSE Linux)) Sun Sep 9 09:34:58 EDT
2007
> ... which is clearly inaccurate.
>

I am not sure the exact version of my source. it comes from XenPPC project
who
maintains a separate Linux tree from the "sparse tree" that comes with Xen.

-----------------------------------------------
$ mkdir ~/xen
$ cd ~/xen
$ hg clone http://xenbits.xensource.com/xen-unstable.hg
$ mkdir ~/xen/linux
$ cd ~/xen/linux
$ hg clone http://xenbits.xensource.com/ext/linux-ppc-2.6.hg
$ mkdir ~/xen/linux/xen
-----------------------------------------------

The gcc version 4.1.2_20070115 was used to build the boot image, which
shipped with SLES 10 SP1.


> What exact command line are you using to build Xen? How are you
> attaching your dom0?
>

Here below is the command line used:
make -C ~/xen/linux/linux-ppc-2.6.hg ARCH=powerpc O=../xen
xen_maple_defconfig
make -C ~/xen/linux/linux-ppc-2.6.hg ARCH=powerpc O=../xen zImage
<cp ramdisk.image.gz ~/xen/linux/xen/arch/powerpc/boot/ramdisk.image.gz>
make -C ~/xen/linux/linux-ppc-2.6.hg ARCH=powerpc O=../xen zImage.initrd
make -C /root/xen/xen-unstable.hg/xen/
DOM0_IMAGE=/root/xen/linux/xen/arch/powerpc/boot/zImage  CMDLINE=" --
root=/dev/disk/by-id/ata-TOSHIBA_MK4019GAXB_93SK3653T-part3"

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



> --
> Hollis Blanchard
> IBM Linux Technology Center
>

Thanks once again!
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel

Reply via email to