From: Jim Fehlig <jfehlig@suse.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: libvir-list@redhat.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Convert libxl driver to Xen 4.2
Date: Tue, 27 Nov 2012 08:14:19 -0700 [thread overview]
Message-ID: <50B4D8CB.1070303@suse.com> (raw)
In-Reply-To: <CAFLBxZYjcij+20baWQZwh+7RSXw1SJjk7PkZ7g-1DoX6EsOa8w@mail.gmail.com>
George Dunlap wrote:
> On Mon, Nov 26, 2012 at 10:28 PM, Jim Fehlig <jfehlig@suse.com
> <mailto:jfehlig@suse.com>> wrote:
>
> Based on a patch originally authored by Daniel De Graaf
>
> http://lists.xen.org/archives/html/xen-devel/2012-05/msg00565.html
>
> This patch converts the Xen libxl driver to support only Xen >= 4.2.
> Support for Xen 4.1 libxl is dropped since that version of libxl is
> designated 'technology preview' only and is incompatible with Xen 4.2
> libxl. Additionally, the default toolstack in Xen 4.1 is still xend,
> for which libvirt has a stable, functional driver.
>
>
> Great! Just one question -- does this patch add any new functionality
> (e.g., migration for libxl), or just switch the existing functionality
> over to the new interface?
This patch just switches all existing functionality to the new libxl
interface. There are other patches in the oven which add new functionality.
Regards,
Jim
next prev parent reply other threads:[~2012-11-27 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353968895-16014-1-git-send-email-jfehlig@suse.com>
2012-11-27 10:35 ` [PATCH] Convert libxl driver to Xen 4.2 George Dunlap
2012-11-27 11:57 ` Stefano Stabellini
2012-11-27 15:14 ` Jim Fehlig [this message]
2012-11-27 10:51 ` Ian Campbell
2012-11-27 11:56 ` Stefano Stabellini
[not found] ` <1354013490.5830.181.camel@zakaz.uk.xensource.com>
2012-11-27 11:00 ` [libvirt] " Daniel P. Berrange
2012-11-30 22:17 ` Jim Fehlig
2012-11-30 22:13 Jim Fehlig
-- strict thread matches above, loose matches on Subject: below --
2012-11-26 22:28 Jim Fehlig
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=50B4D8CB.1070303@suse.com \
--to=jfehlig@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=libvir-list@redhat.com \
--cc=xen-devel@lists.xen.org \
/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.