From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Tue, 30 Mar 2010 18:07:44 -0700 Message-ID: References: <20100322085832.GZ1878@reaktio.net> <29b32d341003231321n502ab6acjc036d6726a749c17@mail.gmail.com> <29b32d341003261211k7140d298lffd9d0dae5d1b9e3@mail.gmail.com> <29b32d341003271128g2638e2cqd76adcf75fcfff8b@mail.gmail.com> <20100327184311.GK1878@reaktio.net> <29b32d341003271832p5337a2e4q70e443face36030b@mail.gmail.com> <29b32d341003272021x70d8d757s28d88f0134809c45@mail.gmail.com> <20100328113439.GO1878@reaktio.net> <20100328115550.GQ1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0533852603==" Return-path: In-Reply-To: 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 --===============0533852603== Content-Type: multipart/alternative; boundary=000e0cd1066aab09a904830e5f3f --000e0cd1066aab09a904830e5f3f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Just to add, I have tried both com1 and com2 from baud rate 38400 to 115200 no luck. Inputs much appreciated. Thanks On Tue, Mar 30, 2010 at 5:28 PM, Ritu kaur wrote: > Hi Pasi, > > Serial console just doesn't seem to work. In extlinux.conf file I have > > # location mbr > serial 0 115200 > default xe-serial > prompt 1 > timeout 50 > ... > > label xe-serial > # XenCloudPlatform (Serial) > kernel mboot.c32 > append /boot/xen.3.4.3.gz com1=3D115200,8n1 console=3Dcom1,vga dom0_mem= =3D752M > lowmem_emergency_pool=3D1M crashkernel=3D64M@32M --- /boot/vmlinuz-2.6.32 > root=3DLABEL=3Droot-mhycetek ro console=3Dtty0 earlyprintk=3Dxen nomodese= t > xencons=3Dhvc console=3Dhvc0 --- /boot/initrd-2.6.32.img > > From another linux m/c, I run minicom -s /dev/ttyS0, configure serial por= t > to match above config. minicom always reports serial port as offline. > Googled and tried another option "minicom -c on /dev/ttyS0" still no luck= . I > have made sure from BIOS on both m/c's serial com ports are enabled. Not > quite sure what is wrong here. Does extlinux.conf entry looks fine? > > Thanks > > > On Sun, Mar 28, 2010 at 4:55 AM, Pasi K=E4rkk=E4inen wrote= : > >> On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi K=E4rkk=E4inen wrote: >> > On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote: >> > > 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 >> > > >> > >> > mkinitrd reads /etc/modprobe.conf to figure out what modules should be >> included into the initrd image. >> > >> >> also I'm not sure if ide-disk is a required module for 2.6.32? >> >> -- Pasi >> >> > > My boot disk is ide and looking into .config didn't give me any >> ideas as >> > > to what has to be enabled. >> > > >> > >> > If you need some other module then fix it in /etc/modprobe.conf >> > You need to figure out what's the correct driver for your root/boot >> disk. >> > >> > -- Pasi >> > >> > > Thanks >> > > >> > > On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur <[1]ritu.kaur.us@[2] >> gmail.com> >> > > wrote: >> > > >> > > Thanks Pasi. I had used following command to regenerate initrd >> image in >> > > xcp 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 seri= al >> cable >> > > will reveal anything more. Inputs appreciated. >> > > >> > > Thanks >> > > >> > > On Sat, Mar 27, 2010 at 11:43 AM, Pasi K=E4rkk=E4inen <[3] >> pasik@iki.fi> >> > > wrote: >> > > >> > > 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 whic= h >> 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 >> > > it: >> > > [4]http://wiki.xensource.com/xenwiki/XenSerialConsole >> > > >> > > -- Pasi >> > > >> > > > Thanks >> > > > >> > > > On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur >> > > <[1][5]ritu.kaur.us@[2][6]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-mhycet= ek ro >> > > Xencons=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 return= s >> 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-mhyce= tek 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_STAR= T >> to >> > > 0x00100000 >> > > > and CONFIG_PHYSICAL_ALIGN=3D0x100000, didn't help. >> > > > >> > > > Inputs appreciated. >> > > > >> > > > Thanks >> > > > >> > > > References >> > > > >> > > > Visible links >> > > > 1. [7]http://ritu.kaur.us/ >> > > > 2. [8]http://gmail.com/ >> > > >> > > > _______________________________________________ >> > > > Xen-devel mailing list >> > > > [9]Xen-devel@lists.xensource.com >> > > > [10]http://lists.xensource.com/xen-devel >> > > >> > > References >> > > >> > > Visible links >> > > 1. http://ritu.kaur.us/ >> > > 2. http://gmail.com/ >> > > 3. mailto:pasik@iki.fi >> > > 4. http://wiki.xensource.com/xenwiki/XenSerialConsole >> > > 5. http://ritu.kaur.us/ >> > > 6. http://gmail.com/ >> > > 7. http://ritu.kaur.us/ >> > > 8. http://gmail.com/ >> > > 9. mailto:Xen-devel@lists.xensource.com >> > > 10. http://lists.xensource.com/xen-devel >> > >> > _______________________________________________ >> > Xen-devel mailing list >> > Xen-devel@lists.xensource.com >> > http://lists.xensource.com/xen-devel >> > > --000e0cd1066aab09a904830e5f3f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Just to add, I have tried both com1 and com2 from baud rate 38400 to 115200= no luck. Inputs much appreciated.

Thanks

On Tue, Mar 30, 2010 at 5:28 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
Hi Pasi,

Serial console just doesn't seem to work. In extlinux.= conf file I have

# location mbr
serial 0 115200
default xe-serial
prompt 1
t= imeout 50
...

label xe-serial
=A0 # XenCloudPlatform (Serial)<= br> =A0 kernel mboot.c32
=A0 append /boot/xen.3.4.3.gz com1=3D115200,8= n1 console=3Dcom1,vga dom0_mem=3D752M lowmem_emergency_pool=3D1M crashkerne= l=3D64M@32M --- /boot/vmlinuz-2.6.32 root=3DLABEL=3Droot-mhycetek ro consol= e=3Dtty0 earlyprintk=3Dxen nomodeset xencons=3Dhvc console=3Dhvc0 --- /boot= /initrd-2.6.32.img

From another linux m/c, I run minicom -s /dev/ttyS0, configure serial p= ort to match above config. minicom always reports serial port as offline. G= oogled and tried another option "minicom -c on /dev/ttyS0" still = no luck. I have made sure from BIOS on both m/c's serial com ports are = enabled. Not quite sure what is wrong here. Does extlinux.conf entry looks = fine?

Thanks


On Sun, Mar 28, 2010 at 4:55 AM, Pasi K=E4rkk=E4inen = <pasik@iki.fi><= /span> wrote:
On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi K=E4rkk=E4inen wrote: > On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote:
> > =A0 =A0I tried another thing. After compilation, =A0I did "m= ake modules_install" in
> > =A0 =A0xcp ddk in order to use following command
> >
> > =A0 =A0mkinitrd -f ./initrd-2.6.32.img 2.6.32
> >
> > =A0 =A0I get following errors...
> >
> > =A0 =A0modinfo: could not find module ide-disk
> > =A0 =A0No module ide-disk found for kernel 2.6.32, aborting
> >
>
> mkinitrd reads /etc/modprobe.conf to figure out what modules should be= included into the initrd image.
>

also I'm not sure if ide-disk is a required module for 2.6.32?
-- Pasi

> > =A0 =A0My boot disk is ide and looking into .config didn't gi= ve me any ideas as
> > =A0 =A0to what has to be enabled.
> >
>
> If you need some other module then fix it in /etc/modprobe.conf
> You need to figure out what's the correct driver for your root/boo= t disk.
>
> -- Pasi
>
> > =A0 =A0Thanks
> >
> > =A0 =A0On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
> > =A0 =A0wrote:
> >
> > =A0 =A0 =A0Thanks Pasi. I had used following command to regenerat= e initrd image in
> > =A0 =A0 =A0xcp ddk
> >
> > =A0 =A0 =A0mkinitrd -f ./initrd-2.6.32.img =A02.6.27.42-0.1.1.xs0= .1.1.737.1065xen
> >
> > =A0 =A0 =A0it doesn't work either. While booting screen goes = blank immediately
> > =A0 =A0 =A0after I see
> > =A0 =A0 =A0...
> > =A0 =A0 =A0 Booting:MBI=3D0x00010120, entry=3D0x00100000
> >
> > =A0 =A0 =A0and next thing I see is BIOS setup, so not sure connec= ting serial cable
> > =A0 =A0 =A0will reveal anything more. Inputs appreciated.
> >
> > =A0 =A0 =A0Thanks
> >
> > =A0 =A0 =A0On Sat, Mar 27, 2010 at 11:43 AM, Pasi K=E4rkk=E4inen = <[3]pasik@iki.fi&g= t;
> > =A0 =A0 =A0wrote:
> >
> > =A0 =A0 =A0 =A0On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kau= r wrote:
> > =A0 =A0 =A0 =A0> =A0 =A0Any inputs on this? I compiled xen/nex= t kernel in Debian Lenny
> > =A0 =A0 =A0 =A0and booted
> > =A0 =A0 =A0 =A0> =A0 =A0successfully as a domU(I am using same= .config file which I used
> > =A0 =A0 =A0 =A0to build
> > =A0 =A0 =A0 =A0> =A0 =A0under xcp-ddk). Looks to me xen/next d= oesn't work with xcp0.1.1.
> > =A0 =A0 =A0 =A0>
> >
> > =A0 =A0 =A0 =A0You need to re-generate the dom0 kernel initrd to = match your kernel.
> > =A0 =A0 =A0 =A0You cannot use the default xcp initrd image.
> >
> > =A0 =A0 =A0 =A0Please provide the full serial console boot log so= we can troubleshoot
> > =A0 =A0 =A0 =A0it:
> > =A0 =A0 =A0 =A0[4]http://wiki.xensource.com/xenwiki/XenSeri= alConsole
> >
> > =A0 =A0 =A0 =A0-- Pasi
> >
> > =A0 =A0 =A0 =A0> =A0 =A0Thanks
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0On Fri, Mar 26, 2010 at 12:11 PM, Ritu= kaur
> > =A0 =A0 =A0 =A0<[1][5]ritu.kaur.us@[2][6]gmail.com>
> > =A0 =A0 =A0 =A0> =A0 =A0wrote:
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Hi Pasi,
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Messages seen with not-working cas= e
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0 /************************************************= ***********************************
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0kernel:/boot/xen.3.4.3.gz dom0-mem= =3D752M
> > =A0 =A0 =A0 =A0lowmem-emergency-pool=3D1M
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0crashkernel=3D64M@32M console=3Dco= mX vga=3Dmode-0x0311
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0loading /boot/xen.3.4.3.gz........= ..
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Module:/boot/vmlinuz-2.6.32 root= =3DLABEL=3Droot-mhycetek ro
> > =A0 =A0 =A0 =A0Xencons=3Dhvc
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0console=3Dhvc0 console=3Dtty0 quie= t vga=3D785 splash
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Loading /boot/vmlinuz-2.6.32......= ...
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Module:/boot/initrd-2.6-xen.img > > =A0 =A0 =A0 =A0> =A0 =A0 =A0Loading
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0 /boot/initrd-2.6-xen.img.........................= ......................................................................
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Booting:MBI=3D0x00010120, entry=3D= 0x00100000
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0 *************************************************= **************************************/
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Screen is blank after these messag= es and system returns to BIOS
> > =A0 =A0 =A0 =A0setup.
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Messages seen with working case > > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0 /************************************************= ***********************************
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0kernel:/boot/xen.gz dom0-mem=3D752= M lowmem-emergency-pool=3D1M
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0crashkernel=3D64M@32M comsole=3Dco= mX vga=3Dmode-0x0311
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0loading /boot/xen.gz..........
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Module:/boot/vmlinuz-2.6.xen root= =3DLABEL=3Droot-mhycetek ro
> > =A0 =A0 =A0 =A0Xencons=3Dhvc
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0console=3Dhvc0 console=3Dtty0 quie= t vga=3D785 splash
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Loading /boot/vmlinuz-2.6.xen.....= ....
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Module:/boot/initrd-2.6-xen.img > > =A0 =A0 =A0 =A0> =A0 =A0 =A0Loading
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0 /boot/initrd-2.6-xen.img.........................= ......................................................................
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Booting:MBI=3D0x00010120, entry=3D= 0x00100000
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0 *************************************************= **************************************/
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Versions used in Non-working case<= br> > > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0xen - 3.4.3/4.0.0
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0kernel - xen/next
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0initrd - default one which came wi= th xcp0.1.1 download.(Ps
> > =A0 =A0 =A0 =A0note, in xcp
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0ddk cannot build initrd image)
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0in Working case
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0xen - 3.4.2
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0kernel - xcp 0.1.1
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0initrd - one that came with xcp 0.= 1.1
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Checked in my .config and changed = CONFIG_PHYSICAL_START to
> > =A0 =A0 =A0 =A00x00100000
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0and CONFIG_PHYSICAL_ALIGN=3D0x1000= 00, didn't help.
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Inputs appreciated.
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0 =A0Thanks
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> References
> > =A0 =A0 =A0 =A0>
> > =A0 =A0 =A0 =A0> =A0 =A0Visible links
> > =A0 =A0 =A0 =A0> =A0 =A01. [7]http://ritu.kaur.us/
> > =A0 =A0 =A0 =A0> =A0 =A02. [8]http://gmail.com/
> >
> > =A0 =A0 =A0 =A0> _____________________________________________= __
> > =A0 =A0 =A0 =A0> Xen-devel mailing list
> > =A0 =A0 =A0 =A0> [9]Xen-devel@lists.xensource.com
> > =A0 =A0 =A0 =A0> [10]http://lists.xensource.com/xen-devel
> >
> > References
> >
> > =A0 =A0Visible links
> > =A0 =A01. http= ://ritu.kaur.us/
> > =A0 =A02. http://= gmail.com/
> > =A0 =A03. mailto:pasik@iki.fi
> > =A0 =A04. http://wiki.xensource.com/xenwiki/XenSerialConsol= e
> > =A0 =A05. http= ://ritu.kaur.us/
> > =A0 =A06. http://= gmail.com/
> > =A0 =A07. http= ://ritu.kaur.us/
> > =A0 =A08. http://= gmail.com/
> > =A0 =A09. mailto:Xen-devel@lists.xensource.com
> > =A0 10. http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list


--000e0cd1066aab09a904830e5f3f-- --===============0533852603== 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 --===============0533852603==--