From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, veillard@redhat.com
Subject: Re: 3.0.3 freeze
Date: Mon, 28 Aug 2006 18:03:00 +0100 [thread overview]
Message-ID: <20060828170300.GF862@redhat.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D57257A@liverpoolst.ad.cl.cam.ac.uk>
On Mon, Aug 28, 2006 at 05:48:56PM +0100, Ian Pratt wrote:
> > > All bug fixing is going on in the unstable tree: there has been no
> > > fork. I'm now done with major refactorings (domctl/sysctl
> > on Friday;
> > > shadow2->shadow today). I wanted those in before 3.0.3 because,
> > > although large, they are unlikely to break anything,
> >
> > Huh ? libvirt uses dom0 syscalls. And libvirt uses its own
> > code to do it since the existing libraries for dom0 calls are
> > GPL'ed which would not be compatible with libvirt own
> > licencing (LGPL). The headers used by libvirt are simply
> > removed, the ioctl entry points are changed, etc ... You
> > really expected that to 'not break anything' ?
>
> We were only thinking in terms of the internal consistency of the tree
> and the public APIs and libraries -- I didn't realise libvirt was going
> directly at the dom0_op ABI rather than using the libxenguest or
> libxenctrl libraries.
>
> If your reason for doing this was just the GPL'ness of the libraries
> then I assume you'd support the email I posted a few weeks ago
> suggesting we try to change the library license to LGPL? Would you then
> start using the libraries?
I don't think the libraries match our use case since they only ever
support the current version of the HV api. libvirt meanwhile supports
*all* historic versions of the HV that it needs. So if someone upgrades
libvirt to a newer release, but doesn't upgrade their HV, their management
layer keeps working reliably - libvirt checks the HV version at runtime and
decides the calls to use. So if we switched to the libraries we'd loose
this compatability with different HV versions
Regards,
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:[~2006-08-28 17:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 16:48 3.0.3 freeze Ian Pratt
2006-08-28 17:03 ` Daniel P. Berrange [this message]
2006-08-28 20:16 ` Daniel Veillard
-- strict thread matches above, loose matches on Subject: below --
2006-08-28 15:22 Ian Pratt
2006-08-22 16:03 Ian Pratt
2006-08-22 16:34 ` Sean Dague
2006-08-22 21:00 ` Ryan Harper
2006-08-22 21:12 ` Subrahmanian, Raj
2006-08-25 0:53 ` Tuan Van
2006-08-28 14:58 ` Daniel P. Berrange
2006-08-28 15:08 ` Keir Fraser
2006-08-28 15:21 ` Daniel P. Berrange
2006-08-28 15:49 ` Daniel Veillard
2006-08-28 16:32 ` Keir Fraser
2006-08-28 16:47 ` Rik van Riel
2006-08-28 16:48 ` Keir Fraser
2006-08-28 17:12 ` Rik van Riel
2006-08-28 17:19 ` Keir Fraser
2006-08-28 17:56 ` Daniel Veillard
2006-09-12 11:06 ` Anthony Wright
2006-09-12 11:40 ` Ian Pratt
2006-09-12 12:55 ` Anthony Wright
2006-09-12 13:45 ` Matt Ayres
2006-09-12 22:00 ` John Lenz
2006-09-13 9:33 ` Nicholas Lee
2006-09-19 11:21 ` Anthony Wright
2006-09-19 12:56 ` Keir Fraser
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=20060828170300.GF862@redhat.com \
--to=berrange@redhat.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=veillard@redhat.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 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.