From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Ritu kaur <ritu.kaur.us@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU guest for xcp 0.1.1
Date: Sun, 28 Mar 2010 14:33:07 +0300 [thread overview]
Message-ID: <20100328113307.GN1878@reaktio.net> (raw)
In-Reply-To: <29b32d341003271832p5337a2e4q70e443face36030b@mail.gmail.com>
On Sat, Mar 27, 2010 at 06:32:00PM -0700, Ritu kaur 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
>
Uhm.. this is wrong.
If you want to generate initrd image for 2.6.32 kernel, then you need to do it like this:
mkinitrd initrd-2.6.32.img 2.6.32
> it doesn't work either. While booting screen goes blank immediately after
> I see
>
Do you have "console=hvc0 earlyprintk=xen nomodeset" parameters for the pvops dom0 kernel?
-- Pasi
> ...
> 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 <[1]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 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:
> [2]http://wiki.xensource.com/xenwiki/XenSerialConsole
>
> -- Pasi
>
> > Thanks
> >
> > On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
> <[1][3]ritu.kaur.us@[2][4]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. [5]http://ritu.kaur.us/
> > 2. [6]http://gmail.com/
>
> > _______________________________________________
> > Xen-devel mailing list
> > [7]Xen-devel@lists.xensource.com
> > [8]http://lists.xensource.com/xen-devel
>
> References
>
> Visible links
> 1. mailto:pasik@iki.fi
> 2. http://wiki.xensource.com/xenwiki/XenSerialConsole
> 3. http://ritu.kaur.us/
> 4. http://gmail.com/
> 5. http://ritu.kaur.us/
> 6. http://gmail.com/
> 7. mailto:Xen-devel@lists.xensource.com
> 8. http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-28 11:33 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 17:10 domU guest for xcp 0.1.1 Ritu kaur
2010-03-12 17:51 ` Pasi Kärkkäinen
2010-03-13 1:51 ` Ritu kaur
2010-03-13 11:18 ` Pasi Kärkkäinen
2010-03-13 16:09 ` Ritu kaur
2010-03-13 16:41 ` Pasi Kärkkäinen
2010-03-14 1:43 ` Ritu kaur
2010-03-14 9:04 ` pvops xen/master and xen/stable domU kernel compilation errors Pasi Kärkkäinen
2010-03-14 11:15 ` domU guest for xcp 0.1.1 Sander Eikelenboom
2010-03-14 20:29 ` Ritu kaur
2010-03-14 20:52 ` Sander Eikelenboom
2010-03-15 1:40 ` Ritu kaur
2010-03-15 3:30 ` Ritu kaur
2010-03-15 8:44 ` Ian Campbell
2010-03-15 13:42 ` Ritu kaur
2010-03-15 13:44 ` Ian Campbell
2010-03-15 13:46 ` Ritu kaur
2010-03-16 2:04 ` Ritu kaur
2010-03-16 7:37 ` Ian Campbell
2010-03-16 15:23 ` Pasi Kärkkäinen
2010-03-16 23:25 ` Ritu kaur
2010-03-17 18:44 ` Ritu kaur
2010-03-18 9:17 ` Ian Campbell
2010-03-18 13:43 ` Ritu kaur
2010-03-18 14:11 ` Ian Campbell
2010-03-18 14:23 ` Ritu kaur
2010-03-18 14:27 ` Ian Campbell
2010-03-18 14:32 ` Ian Campbell
2010-03-18 14:39 ` Konrad Rzeszutek Wilk
2010-03-18 15:28 ` Ritu kaur
2010-03-18 16:26 ` Konrad Rzeszutek Wilk
2010-03-19 15:27 ` Ritu kaur
2010-03-21 1:50 ` Ritu kaur
2010-03-21 17:22 ` Ritu kaur
2010-03-21 18:41 ` Pasi Kärkkäinen
2010-03-21 21:21 ` Ritu kaur
2010-03-22 8:58 ` Pasi Kärkkäinen
2010-03-22 21:02 ` Ritu kaur
2010-03-22 21:09 ` Pasi Kärkkäinen
2010-03-23 20:21 ` Ritu kaur
2010-03-26 19:11 ` Ritu kaur
2010-03-27 18:28 ` Ritu kaur
2010-03-27 18:43 ` Pasi Kärkkäinen
2010-03-28 1:32 ` Ritu kaur
2010-03-28 3:21 ` Ritu kaur
2010-03-28 11:34 ` Pasi Kärkkäinen
2010-03-28 11:55 ` Pasi Kärkkäinen
2010-03-31 0:28 ` Ritu kaur
2010-03-31 1:07 ` Ritu kaur
2010-03-31 6:30 ` Pasi Kärkkäinen
2010-03-31 13:15 ` Ritu kaur
2010-03-31 13:42 ` Konrad Rzeszutek Wilk
2010-03-31 13:55 ` Ritu kaur
2010-03-31 14:39 ` Pasi Kärkkäinen
2010-03-31 21:10 ` Ritu kaur
2010-04-01 12:48 ` Ritu kaur
2010-04-05 14:10 ` Ritu kaur
2010-04-05 17:00 ` Konrad Rzeszutek Wilk
2010-04-06 4:00 ` Ritu kaur
2010-04-06 6:03 ` Pasi Kärkkäinen
2010-04-06 13:31 ` Ritu kaur
2010-04-09 15:53 ` Ritu kaur
2010-04-11 17:11 ` Ritu kaur
2010-04-12 14:04 ` Konrad Rzeszutek Wilk
2010-04-12 22:14 ` Ritu kaur
2010-04-13 8:34 ` Ian Campbell
2010-04-13 22:06 ` Ritu kaur
2010-04-14 8:48 ` Ian Campbell
2010-03-28 11:33 ` Pasi Kärkkäinen [this message]
2010-03-31 23:23 ` Ritu kaur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100328113307.GN1878@reaktio.net \
--to=pasik@iki.fi \
--cc=ritu.kaur.us@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).