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-devel

Re: [Xen-devel] domU guest for xcp 0.1.1

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Tue, 30 Mar 2010 18:07:44 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 30 Mar 2010 18:08:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=2mW8D1F4RFvQSt1v3T98p0n6NATyrsPTkjMX24WPa8A=; b=JuniFF3XVKdGrteeie080yjVkq0RabnVqMRGhWMRoh+wYAItaM68qqXhM50eQDURzI Y7e9yF5zzD/w0mI1kxA9b0z8o6MVkSrMWXWn90BBP6D0Bbv4iVXJcSosN/Zrd5PqNJca Ek8Rsi4zZ0G1I3/JN//W22i+YdiIZXbQlcK40=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WJI+xGFpedPXNVkAwk8uGoQozBivExgUhU53yQvve3/P7e9LEuRy+ux5Pfprzz5YPw dkRymguXre/eZscCllbFD0cw5WM+AmdozYfoS+PFuYznCzI+xrQbJOnJvKs8V/fa7pPh Ew0MN6NJqpiJYn0gJYmlj9RZ11t1vtkxAvono=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <h2q29b32d341003301728q8b505cebx1c0326d9451121f5@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100322085832.GZ1878@xxxxxxxxxxx> <29b32d341003231321n502ab6acjc036d6726a749c17@xxxxxxxxxxxxxx> <29b32d341003261211k7140d298lffd9d0dae5d1b9e3@xxxxxxxxxxxxxx> <29b32d341003271128g2638e2cqd76adcf75fcfff8b@xxxxxxxxxxxxxx> <20100327184311.GK1878@xxxxxxxxxxx> <29b32d341003271832p5337a2e4q70e443face36030b@xxxxxxxxxxxxxx> <29b32d341003272021x70d8d757s28d88f0134809c45@xxxxxxxxxxxxxx> <20100328113439.GO1878@xxxxxxxxxxx> <20100328115550.GQ1878@xxxxxxxxxxx> <h2q29b32d341003301728q8b505cebx1c0326d9451121f5@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
timeout 50
...

label xe-serial
  # XenCloudPlatform (Serial)
  kernel mboot.c32
  append /boot/xen.3.4.3.gz com1=115200,8n1 console=com1,vga dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M --- /boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro console=tty0 earlyprintk=xen nomodeset xencons=hvc console=hvc0 --- /boot/initrd-2.6.32.img

From another linux m/c, I run minicom -s /dev/ttyS0, configure serial port 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ärkkäinen <pasik@xxxxxx> wrote:
On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi Kärkkäinen 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=0x00010120, entry=0x00100000
> >
> >      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ärkkäinen <[3]pasik@xxxxxx>
> >      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 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
> >        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=752M
> >        lowmem-emergency-pool=1M
> >        >      crashkernel=64M@32M console=comX vga=mode-0x0311
> >        >      loading /boot/xen.3.4.3.gz..........
> >        >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro
> >        Xencons=hvc
> >        >      console=hvc0 console=tty0 quiet vga=785 splash
> >        >      Loading /boot/vmlinuz-2.6.32.........
> >        >      Module:/boot/initrd-2.6-xen.img
> >        >      Loading
> >        >
> >         /boot/initrd-2.6-xen.img...............................................................................................
> >        >      Booting:MBI=0x00010120, entry=0x00100000
> >        >
> >         ***************************************************************************************/
> >        >
> >        >      Screen is blank after these messages and system returns to BIOS
> >        setup.
> >        >
> >        >      Messages seen with working case
> >        >
> >         /***********************************************************************************
> >        >      kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
> >        >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
> >        >      loading /boot/xen.gz..........
> >        >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro
> >        Xencons=hvc
> >        >      console=hvc0 console=tty0 quiet vga=785 splash
> >        >      Loading /boot/vmlinuz-2.6.xen.........
> >        >      Module:/boot/initrd-2.6-xen.img
> >        >      Loading
> >        >
> >         /boot/initrd-2.6-xen.img...............................................................................................
> >        >      Booting:MBI=0x00010120, entry=0x00100000
> >        >
> >         ***************************************************************************************/
> >        >
> >        >      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=0x100000, 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@xxxxxxxxxxxxxxxxxxx
> >        > [10]http://lists.xensource.com/xen-devel
> >
> > References
> >
> >    Visible links
> >    1. http://ritu.kaur.us/
> >    2. http://gmail.com/
> >    3. mailto:pasik@xxxxxx
> >    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@xxxxxxxxxxxxxxxxxxx
> >   10. http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list


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