xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jim Fehlig <jfehlig@suse.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Chun Yan Liu <cyliu@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ondrej Holecek <oholecek@suse.com>,
	Bamvor Jian Zhang <bjzhang@suse.com>
Subject: Re: libxl drivers for libvirt?
Date: Fri, 26 Oct 2012 14:03:33 +0100	[thread overview]
Message-ID: <508A8A25.3010505@eu.citrix.com> (raw)
In-Reply-To: <50882F59.6070203@suse.com>

On 24/10/12 19:11, Jim Fehlig wrote:
>> * What kind of Xen support for libxl is in the libvirt development
>> branch, and do you have an idea when full support for 4.2 (at least,
>> including migration, suspend/resume, &c) might be available?
> Nothing has changed in git master over what is available in 0.10.2, but
> we are now starting to pick up this work.  Our priorities are to first
> get the libxl driver compiling against 4.2 and all of the existing
> functionality that works with 4.1 working with 4.2, followed by closing
> the feature gap with the legacy xen driver, and finally closing the
> feature gap with the qemu driver where it makes sense.  This is
> obviously quite a bit of work and any help would be appreciated :).
>
> BTW, we don't have any motivation to add features to the 4.1 version of
> the libvirt libxl driver.

That sounds like a good plan.  For 4.1, xend is still the default 
toolstack, and libxl is a "tech preview"; for 4.2, xl is the default 
toolstack, and (if I understand correctly) we're officially going to be 
supporting the libxl interface in a backwards-compatible way from here 
forward.

It seems to me that if you have trouble supporting both libxl 4.2 and 
libxl 4.1, that it might be better just to drop 4.1 support and focus on 
4.2.  Ian Campbell / Jackson: Thoughts?

  -George

  parent reply	other threads:[~2012-10-26 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 15:33 libxl drivers for libvirt? George Dunlap
2012-10-24 18:11 ` Jim Fehlig
2012-10-26 12:54   ` Ondřej Holeček
2012-10-26 13:12     ` Ian Campbell
2012-10-26 13:03   ` George Dunlap [this message]
2012-10-26 13:18     ` Ian Campbell
2012-10-29 15:55       ` Jim Fehlig
2012-10-29 16:05         ` [libvirt] " Daniel P. Berrange
2012-10-26 14:00     ` Ian Jackson

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=508A8A25.3010505@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=bjzhang@suse.com \
    --cc=cyliu@suse.com \
    --cc=dario.faggioli@citrix.com \
    --cc=jfehlig@suse.com \
    --cc=oholecek@suse.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 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).