From: Ritu kaur <ritu.kaur.us@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: domU guest for xcp 0.1.1
Date: Sat, 27 Mar 2010 11:28:12 -0700 [thread overview]
Message-ID: <29b32d341003271128g2638e2cqd76adcf75fcfff8b@mail.gmail.com> (raw)
In-Reply-To: <29b32d341003261211k7140d298lffd9d0dae5d1b9e3@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2317 bytes --]
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.
Thanks
On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur <ritu.kaur.us@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
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2697 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-27 18:28 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 [this message]
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
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=29b32d341003271128g2638e2cqd76adcf75fcfff8b@mail.gmail.com \
--to=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).