xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Srujan Kotikela <ksrujandas@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.0.1 on Ubuntu 10.04 LTS Desktop
Date: Wed, 16 Mar 2011 19:38:41 +0000	[thread overview]
Message-ID: <1300304321.26078.5.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTinRsBvqFdwm52xdL4aycr-ynOmzF9=Be_ydjbSY@mail.gmail.com>

Please don't top post.

On Wed, Mar 16, 2011 at 1:19 PM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote: 
>         
>         No. It is b/c you don't have the hypervisor (xen.gz) in your
>         grub2 file.
>         Did you install the xen toolstack?

On Wed, 2011-03-16 at 19:26 +0000, Srujan Kotikela wrote:
> 
> Yes, I did.

You didn't actually boot Xen though, your log contains:

Mar 16 04:36:15 xen kernel: [    0.000000] Booting paravirtualized kernel on bare hardware

I wonder if this is because your grub stanza contains
	multiboot ....xen....
	linux ....vmlinuz....
	initrd ....initrd....
and the "linux" statement (which means boot a native Linux kernel) takes
precedence over the "multiboot" statement (which means boot a multiboot
kernel, possibly with a series of extra modules).

I think you probably need to use something of this form instead:
	multiboot ....xen....
	module ....vmlinuz....
	module ...initrd....

IOW your mistake is that the "linux" statement does not add extra
modules to a "multiboot" kernel -- it is a top level kernel loader
command thing in its own right. "module" is the correct syntax for
adding additional multiboot modules.

Ian.

> 
> --
> Srujan D. Kotikela
> 
> 
> 
> 
> On Wed, Mar 16, 2011 at 1:19 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
>         On Wed, Mar 16, 2011 at 12:50:27PM -0500, Srujan Kotikela
>         wrote:
>         > Hi,
>         >
>         > I tried installing Xen 4.0.1 on Ubuntu 10.04 using the
>         xen/stable a.k.a
>         > 2.6.32.32 PVOPS kernel. The installation went fine, but xend
>         is not running.
>         > I had similar issue when I tried in Ubuntu 10.10 also. Is it
>         because of the
>         > PVOPS kernel?
>         
>         
>         No. It is b/c you don't have the hypervisor (xen.gz) in your
>         grub2 file.
>         Did you install the xen toolstack?
>         >
>         > The log is attached.
>         >
>         >
>         > --
>         > Srujan D. Kotikela
>         
>         
>         
>         > _______________________________________________
>         > Xen-devel mailing list
>         > Xen-devel@lists.xensource.com
>         > http://lists.xensource.com/xen-devel
>         
> 
> 
> 

  reply	other threads:[~2011-03-16 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 17:50 Xen 4.0.1 on Ubuntu 10.04 LTS Desktop Srujan Kotikela
2011-03-16 17:53 ` Srujan Kotikela
2011-03-16 18:19 ` Konrad Rzeszutek Wilk
     [not found]   ` <AANLkTikZ4ieWCjwre36+Zo7jPha0-HyLaV4h+gXo2+5t@mail.gmail.com>
2011-03-16 19:26     ` Srujan Kotikela
2011-03-16 19:38       ` Ian Campbell [this message]
2011-03-16 20:13         ` Srujan Kotikela
2011-03-16 19:32 ` Pasi Kärkkäinen

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=1300304321.26078.5.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=ksrujandas@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).