From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, Bruce Edge <bruce.edge@gmail.com>
Subject: Re: Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
Date: Tue, 9 Nov 2010 10:00:33 -0500 [thread overview]
Message-ID: <20101109150033.GC7208@dumpdata.com> (raw)
In-Reply-To: <677774.36242.qm@web56105.mail.re3.yahoo.com>
On Tue, Nov 09, 2010 at 03:20:13AM -0800, Boris Derzhavets wrote:
> > No. xen/next-2.6.36 doesn't exist any more, and it never really
> > contained anything useful. xen/next-2.6.37, however, is closely
> > tracking upstream and I hope will reach functional parity with the
> > 2.6.32-based branches.
>
> Is 2.6.38 merge window right estimate for time frame to reach functional
> parity with the 2.6.32-based branches ?
Not exactly. We are aiming for the basic functionality for running a PV guest
in that timeframe. Right now, you probably can run an HVM guests, thought we
have been so focused on shaking out bringup bugs that it has not been on our
list of high priorities.
However, something which I did not know until last week, is that there is a
blkback and netback built in QEMU. Which means you could boot up a PV guest
with the blkback/netback utilizing the QEMU back-ends - how well they do, I don't
know. I am not even sure how to utilize it - it might be worth digging in that
and finding out how well it works?
next prev parent reply other threads:[~2010-11-09 15:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 18:19 pvops kernel branches - 2.6.36 options, stable/next/etc? Bruce Edge
2010-11-08 19:14 ` Jeremy Fitzhardinge
2010-11-09 10:26 ` Thomas Goirand
2010-11-10 18:13 ` Jeremy Fitzhardinge
2010-11-12 7:43 ` Boris Derzhavets
2010-11-09 11:20 ` Boris Derzhavets
2010-11-09 15:00 ` Konrad Rzeszutek Wilk [this message]
2010-11-09 16:27 ` Boris Derzhavets
2010-11-10 18:17 ` Bruce Edge
2010-11-10 18:27 ` Jeremy Fitzhardinge
2010-11-10 19:43 ` Konrad Rzeszutek Wilk
2010-11-10 20:04 ` Bruce Edge
2010-11-11 14:58 ` Bruce Edge
2010-11-11 16:25 ` Konrad Rzeszutek Wilk
2010-11-11 16:48 ` Bruce Edge
2010-11-11 16:55 ` Konrad Rzeszutek Wilk
2010-11-11 18:09 ` Boris Derzhavets
2010-11-11 18:32 ` Bruce Edge
2010-11-11 18:50 ` Boris Derzhavets
2010-11-11 20:03 ` Boris Derzhavets
2010-11-11 20:20 ` Bruce Edge
2010-11-11 21:11 ` Konrad Rzeszutek Wilk
2010-11-11 22:06 ` Bruce Edge
2010-11-11 22:25 ` Konrad Rzeszutek Wilk
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=20101109150033.GC7208@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bderzhavets@yahoo.com \
--cc=bruce.edge@gmail.com \
--cc=jeremy@goop.org \
--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.