xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Bamvor Jian Zhang <bjzhang@suse.com>
Subject: Re: [xen-devel] [PATCH] libxl: fix compile error	of libvirt
Date: Thu, 23 Feb 2012 20:05:45 -0700	[thread overview]
Message-ID: <4F46FE89.3050209@suse.com> (raw)
In-Reply-To: <1329987543.8557.24.camel@zakaz.uk.xensource.com>

Ian Campbell wrote:
> On Wed, 2012-02-22 at 21:42 +0000, Jim Fehlig wrote:
>   
>> Ian Jackson wrote:
>>     
>>> Note that the API for libxl has changed in xen-unstable.hg compared to
>>> 4.1, and further changes are forthcoming.  So there will have to be
>>> changes in libvirt.
>>>   
>>>       
>> I suppose libvirt is the only out-of-tree libxl app feeling this pain :-(.
>>     
>
> We're sorry about this, we felt it was necessary to break the API
> between 4.1 and 4.2 in order that we can support a stable API from 4.2
> onwards (I think we discussed this at the time?).

Yes we did, and I need to stop whining about it :-).

>  From 4.2 onwards we
> will make changes in a compatible way or provide compatibility shims etc
> or in extreme circumstances do things in a way which is easily
> detectable e.g. via configure tests.
>   

That would be much appreciated.  Maybe we'll start seeing more libxl apps...

> I was wondering the other day if "libxl v2" support for libvirt might
> make a nice GSoC project, what do you think? Would you be interested in
> mentoring such a project?
>   

I agree that it would make a nice GSoC project, but I had encouraged
Bamvor to take on the task.  It's a good project for becoming familiar
with xen and libvirt.

Regards,
Jim

  reply	other threads:[~2012-02-24  3:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20  9:00 [xen-devel] [PATCH] libxl: fix compile error of libvirt Bamvor Jian Zhang
2012-02-21 18:02 ` Ian Jackson
2012-02-22  7:58   ` Bamvor Jian Zhang
2012-02-22 11:52     ` Ian Jackson
2012-02-22 12:10       ` Ian Campbell
2012-02-22 21:40       ` Jim Fehlig
2012-02-23  8:45         ` Ian Campbell
2012-02-23  8:52           ` Ian Campbell
2012-02-23 11:01             ` Ian Campbell
2012-02-24 12:18         ` Ian Jackson
2012-02-24 12:42           ` Ian Campbell
2012-02-24 15:42             ` Ian Jackson
2012-02-24 16:51               ` Ian Campbell
2012-02-23  2:42       ` Bamvor Jian Zhang
2012-02-22 21:42   ` Jim Fehlig
2012-02-23  8:59     ` Ian Campbell
2012-02-24  3:05       ` Jim Fehlig [this message]
2012-02-24  8:54         ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2012-02-21  2:06 Bamvor Jian Zhang

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=4F46FE89.3050209@suse.com \
    --to=jfehlig@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=bjzhang@suse.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 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).