From: "Daniel P. Berrange" <berrange@redhat.com>
To: Nate Carlson <natecars@natecarlson.com>
Cc: tim.post@netkinetics.net, Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>,
Ian Campbell <Ian.Campbell@xensource.com>
Subject: Re: 2.6.20.3 to be the next kernel?
Date: Mon, 4 Jun 2007 19:17:52 +0100 [thread overview]
Message-ID: <20070604181752.GG17323@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0706041312470.2167@tungsten.msp.technicality.org>
On Mon, Jun 04, 2007 at 01:13:01PM -0500, Nate Carlson wrote:
> On Mon, 4 Jun 2007, Mark Williamson wrote:
> >Not sure. A few interesting things are currently in progress with
> >respect to kernel versions; the Xen paravirt-ops patches may be going
> >into the next release mainline Linux (maybe? I think?) at which point
> >you'll be able to build domU kernels directly from kernel.org sources.
>
> Just curious - can you also build dom0? :)
No. AFAIK, at this point in time, Xen paravirt_ops is DomU only.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-06-04 18:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 12:44 2.6.20.3 to be the next kernel? Tim Post
2007-06-04 18:01 ` Mark Williamson
2007-06-04 18:10 ` Daniel P. Berrange
2007-06-04 18:31 ` Mark Williamson
2007-06-04 18:13 ` Nate Carlson
2007-06-04 18:17 ` Daniel P. Berrange [this message]
2007-06-04 18:33 ` Mark Williamson
2007-06-04 19:04 ` Jeremy Fitzhardinge
2007-06-04 19:58 ` Mark Williamson
2007-06-04 20:00 ` Daniel P. Berrange
2007-06-04 20:16 ` Jeremy Fitzhardinge
2007-06-04 20:15 ` Jeremy Fitzhardinge
2007-06-05 2:24 ` Mark Williamson
2007-06-05 4:50 ` Jeremy Fitzhardinge
2007-06-05 4:57 ` Jeremy Fitzhardinge
2007-06-05 15:57 ` Mark Williamson
2007-06-05 3:49 ` Tim Post
2007-06-05 4:53 ` Jeremy Fitzhardinge
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=20070604181752.GG17323@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Campbell@xensource.com \
--cc=jeremy@goop.org \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=natecars@natecarlson.com \
--cc=tim.post@netkinetics.net \
--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.