From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Sat, 27 Mar 2010 20:21:49 -0700 Message-ID: <29b32d341003272021x70d8d757s28d88f0134809c45@mail.gmail.com> References: <29b32d341003201850v6328f6afp1183c16ae6771cb1@mail.gmail.com> <29b32d341003211421g2a49a807obfcfd7c8b3260b74@mail.gmail.com> <20100322085832.GZ1878@reaktio.net> <29b32d341003221402u745c15adhedb491b4518797c@mail.gmail.com> <20100322210944.GS1878@reaktio.net> <29b32d341003231321n502ab6acjc036d6726a749c17@mail.gmail.com> <29b32d341003261211k7140d298lffd9d0dae5d1b9e3@mail.gmail.com> <29b32d341003271128g2638e2cqd76adcf75fcfff8b@mail.gmail.com> <20100327184311.GK1878@reaktio.net> <29b32d341003271832p5337a2e4q70e443face36030b@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1247985505==" Return-path: In-Reply-To: <29b32d341003271832p5337a2e4q70e443face36030b@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1247985505== Content-Type: multipart/alternative; boundary=000e0cd17e22a11e550482d3e5f0 --000e0cd17e22a11e550482d3e5f0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I tried another thing. After compilation, I did "make modules_install" in xcp ddk in order to use following command mkinitrd -f ./initrd-2.6.32.img 2.6.32 I get following errors... modinfo: could not find module ide-disk No module ide-disk found for kernel 2.6.32, aborting My boot disk is ide and looking into .config didn't give me any ideas as to what has to be enabled. Thanks On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur wrote: > Thanks Pasi. I had used following command to regenerate initrd image in x= cp > ddk > > mkinitrd -f ./initrd-2.6.32.img 2.6.27.42-0.1.1.xs0.1.1.737.1065xen > > it doesn't work either. While booting screen goes blank immediately after= I > see > > ... > Booting:MBI=3D0x00010120, entry=3D0x00100000 > > and next thing I see is BIOS setup, so not sure connecting serial cable > will reveal anything more. Inputs appreciated. > > Thanks > > > On Sat, Mar 27, 2010 at 11:43 AM, Pasi K=E4rkk=E4inen wrot= e: > >> On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote: >> > Any inputs on this? I compiled xen/next kernel in Debian Lenny and >> booted >> > successfully as a domU(I am using same .config file which I used to >> build >> > under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1. >> > >> >> You need to re-generate the dom0 kernel initrd to match your kernel. >> You cannot use the default xcp initrd image. >> >> Please provide the full serial console boot log so we can troubleshoot i= t: >> http://wiki.xensource.com/xenwiki/XenSerialConsole >> >> -- Pasi >> >> > Thanks >> > >> > On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur <[1]ritu.kaur.us@[2] >> gmail.com> >> > wrote: >> > >> > Hi Pasi, >> > >> > Messages seen with not-working case >> > >> > >> /**********************************************************************= ************* >> > kernel:/boot/xen.3.4.3.gz dom0-mem=3D752M lowmem-emergency-pool= =3D1M >> > crashkernel=3D64M@32M console=3DcomX vga=3Dmode-0x0311 >> > loading /boot/xen.3.4.3.gz.......... >> > Module:/boot/vmlinuz-2.6.32 root=3DLABEL=3Droot-mhycetek ro Xenco= ns=3Dhvc >> > console=3Dhvc0 console=3Dtty0 quiet vga=3D785 splash >> > Loading /boot/vmlinuz-2.6.32......... >> > Module:/boot/initrd-2.6-xen.img >> > Loading >> > >> /boot/initrd-2.6-xen.img...............................................= ................................................ >> > Booting:MBI=3D0x00010120, entry=3D0x00100000 >> > >> ***********************************************************************= ****************/ >> > >> > Screen is blank after these messages and system returns to BIOS >> setup. >> > >> > Messages seen with working case >> > >> /**********************************************************************= ************* >> > kernel:/boot/xen.gz dom0-mem=3D752M lowmem-emergency-pool=3D1M >> > crashkernel=3D64M@32M comsole=3DcomX vga=3Dmode-0x0311 >> > loading /boot/xen.gz.......... >> > Module:/boot/vmlinuz-2.6.xen root=3DLABEL=3Droot-mhycetek ro >> Xencons=3Dhvc >> > console=3Dhvc0 console=3Dtty0 quiet vga=3D785 splash >> > Loading /boot/vmlinuz-2.6.xen......... >> > Module:/boot/initrd-2.6-xen.img >> > Loading >> > >> /boot/initrd-2.6-xen.img...............................................= ................................................ >> > Booting:MBI=3D0x00010120, entry=3D0x00100000 >> > >> ***********************************************************************= ****************/ >> > >> > Versions used in Non-working case >> > >> > xen - 3.4.3/4.0.0 >> > kernel - xen/next >> > initrd - default one which came with xcp0.1.1 download.(Ps note, = in >> xcp >> > ddk cannot build initrd image) >> > >> > in Working case >> > >> > xen - 3.4.2 >> > kernel - xcp 0.1.1 >> > initrd - one that came with xcp 0.1.1 >> > >> > Checked in my .config and changed CONFIG_PHYSICAL_START to >> 0x00100000 >> > and CONFIG_PHYSICAL_ALIGN=3D0x100000, didn't help. >> > >> > Inputs appreciated. >> > >> > Thanks >> > >> > References >> > >> > Visible links >> > 1. http://ritu.kaur.us/ >> > 2. http://gmail.com/ >> >> > _______________________________________________ >> > Xen-devel mailing list >> > Xen-devel@lists.xensource.com >> > http://lists.xensource.com/xen-devel >> >> > --000e0cd17e22a11e550482d3e5f0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I tried another thing. After compilation,=A0 I did "make modules_insta= ll" in xcp ddk in order to use following command

mkinitrd -f ./= initrd-2.6.32.img 2.6.32

I get following errors...

modinfo: c= ould not find module ide-disk
No module ide-disk found for kernel 2.6.32, aborting

My boot disk is= ide and looking into .config didn't give me any ideas as to what has t= o be enabled.

Thanks

On Sat, Mar = 27, 2010 at 6:32 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
Thanks Pasi. I ha= d used following command to regenerate initrd image in xcp ddk

mkini= trd -f ./initrd-2.6.32.img=A0 2.6.27.42-0.1.1.xs0.1.1.737.1065xen

it doesn't work either. While booting screen goes blank immediately= after I see

...
=A0Booting:MBI=3D0x00010120, entry=3D0x00100000
=A0
= and next thing I see is BIOS setup, so not sure connecting serial cable wil= l reveal anything more. Inputs appreciated.

Thanks


On Sat, Mar 27, 2010 at 11:43 AM, Pasi K=E4rkk=E4inen <= ;pasik@iki.fi> wrote:
On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
> =A0 =A0Any inputs on this? I compiled xen/next kernel in Debian Lenny = and booted
> =A0 =A0successfully as a domU(I am using same .config file which I use= d to build
> =A0 =A0under xcp-ddk). Looks to me xen/next doesn't work with xcp0= .1.1.
>

You need to re-generate the dom0 kernel initrd to match your kernel.<= br> You cannot use the default xcp initrd image.

Please provide the full serial console boot log so we can troubleshoot it:<= br> http://wiki.xensource.com/xenwiki/XenSerialConsole

-- Pasi

> =A0 =A0Thanks
>
> =A0 =A0On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
> =A0 =A0wrote:
>
> =A0 =A0 =A0Hi Pasi,
>
> =A0 =A0 =A0Messages seen with not-working case
>
> =A0 =A0 =A0/**********************************************************= *************************
> =A0 =A0 =A0kernel:/boot/xen.3.4.3.gz dom0-mem=3D752M lowmem-emergency-= pool=3D1M
> =A0 =A0 =A0crashkernel=3D64M@32M console=3DcomX vga=3Dmode-0x0311
> =A0 =A0 =A0loading /boot/xen.3.4.3.gz..........
> =A0 =A0 =A0Module:/boot/vmlinuz-2.6.32 root=3DLABEL=3Droot-mhycetek ro= Xencons=3Dhvc
> =A0 =A0 =A0console=3Dhvc0 console=3Dtty0 quiet vga=3D785 splash
> =A0 =A0 =A0Loading /boot/vmlinuz-2.6.32.........
> =A0 =A0 =A0Module:/boot/initrd-2.6-xen.img
> =A0 =A0 =A0Loading
> =A0 =A0 =A0/boot/initrd-2.6-xen.img...................................= ............................................................
> =A0 =A0 =A0Booting:MBI=3D0x00010120, entry=3D0x00100000
> =A0 =A0 =A0***********************************************************= ****************************/
>
> =A0 =A0 =A0Screen is blank after these messages and system returns to = BIOS setup.
>
> =A0 =A0 =A0Messages seen with working case
> =A0 =A0 =A0/**********************************************************= *************************
> =A0 =A0 =A0kernel:/boot/xen.gz dom0-mem=3D752M lowmem-emergency-pool= =3D1M
> =A0 =A0 =A0crashkernel=3D64M@32M comsole=3DcomX vga=3Dmode-0x0311
> =A0 =A0 =A0loading /boot/xen.gz..........
> =A0 =A0 =A0Module:/boot/vmlinuz-2.6.xen root=3DLABEL=3Droot-mhycetek r= o Xencons=3Dhvc
> =A0 =A0 =A0console=3Dhvc0 console=3Dtty0 quiet vga=3D785 splash
> =A0 =A0 =A0Loading /boot/vmlinuz-2.6.xen.........
> =A0 =A0 =A0Module:/boot/initrd-2.6-xen.img
> =A0 =A0 =A0Loading
> =A0 =A0 =A0/boot/initrd-2.6-xen.img...................................= ............................................................
> =A0 =A0 =A0Booting:MBI=3D0x00010120, entry=3D0x00100000
> =A0 =A0 =A0***********************************************************= ****************************/
>
> =A0 =A0 =A0Versions used in Non-working case
>
> =A0 =A0 =A0xen - 3.4.3/4.0.0
> =A0 =A0 =A0kernel - xen/next
> =A0 =A0 =A0initrd - default one which came with xcp0.1.1 download.(Ps = note, in xcp
> =A0 =A0 =A0ddk cannot build initrd image)
>
> =A0 =A0 =A0in Working case
>
> =A0 =A0 =A0xen - 3.4.2
> =A0 =A0 =A0kernel - xcp 0.1.1
> =A0 =A0 =A0initrd - one that came with xcp 0.1.1
>
> =A0 =A0 =A0Checked in my .config and changed CONFIG_PHYSICAL_START to = 0x00100000
> =A0 =A0 =A0and CONFIG_PHYSICAL_ALIGN=3D0x100000, didn't help.
>
> =A0 =A0 =A0Inputs appreciated.
>
> =A0 =A0 =A0Thanks
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. http://ri= tu.kaur.us/
> =A0 =A02. http://gmail= .com/

> ___________________________________________= ____
> Xen-devel mailing list
> Xen= -devel@lists.xensource.com
> htt= p://lists.xensource.com/xen-devel



--000e0cd17e22a11e550482d3e5f0-- --===============1247985505== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1247985505==--