From: Anthony Liguori <aliguori@us.ibm.com>
To: Tom Marshall <tommy@home.tig-grr.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-users] Xen 3.0 on Ubuntu Dapper
Date: Thu, 23 Feb 2006 09:39:12 -0600 [thread overview]
Message-ID: <43FDD720.9090701@us.ibm.com> (raw)
In-Reply-To: <20060221233838.GC11453@home.tig-grr.com>
(Moving to xen-devel)
Tom Marshall wrote:
>> In case anyone is interested, I'm trying to port the the Ubuntu Dapper
>> kernel to Xen. I can see two options: (1) revert the kernel back to 3.0.1
>> compatibility, or (2) update the tools to tip. Both seem to be nontrivial.
>> I'm currently attempting the former because Dapper uses 2.6.15 as a base,
>> but I have a feeling that the latter may prove a better course.
>>
>
> Just a quick update (sorry for the spam, I'm hoping at least a couple folks
> are interested in Xen 3.x on Dapper...)
>
> I got kernel 2.6.15 up and running on Dapper using version 16045
> (16045:7b8ab50c2b04) with the Xen 3.0.1 tools. I'm not really familiar with
> driving Mercurial, nor the Xen history. So I would like to ask if this is a
> good version to start with, or whether a later version (compatible with
> 3.0.1 and based on 2.6.15 if possible) would be a better starting point.
>
Which tree did you base this on? 16045 is a local version number (only
has meaning in your repository). 7b8ab50c2b04 doesn't appear to be in
-unstable.
In general, if you're building a domU kernel, it should be safe to use
older changesets. If you're building a dom0 kernel, you really want to
use a set of tools that is matched with the dom0 kernel. I don't think
there have been any huge changes in the tools so I think it would be
fine to pull the tools from the same snapshot that you took 2.6.15 from
(which I assume is around 8740:3d7ea7972b39).
> I'll be trying to merge this with the Dapper changes. If there is any
> interest in this project, I can send out another message with a link to my
> merged code when I'm done. If not, please accept my apologies for the
> interruption.
>
I tried running -unstable on Dapper a couple of weeks ago and Xend
wouldn't start. I only run Dapper on my laptop so I haven't
investigated much further. Have you had any problems with Xend?
Regards,
Anthony Liguori
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
next parent reply other threads:[~2006-02-23 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43FB83EE.3020002@cira.colostate.edu>
[not found] ` <20060221214223.GC9533@home.tig-grr.com>
[not found] ` <20060221233838.GC11453@home.tig-grr.com>
2006-02-23 15:39 ` Anthony Liguori [this message]
2006-02-23 17:55 ` Re: [Xen-users] Xen 3.0 on Ubuntu Dapper Tom Marshall
2006-02-23 19:10 ` Anthony Liguori
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=43FDD720.9090701@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=tommy@home.tig-grr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.