WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

[XenPPC] Re: [Libvir] libvirt not compatible with Xen-unstable hypercall

To: veillard@xxxxxxxxxx
Subject: [XenPPC] Re: [Libvir] libvirt not compatible with Xen-unstable hypercall API ?
From: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Date: Tue, 27 Mar 2007 18:30:11 +0900
Cc: libvir-list@xxxxxxxxxx, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 27 Mar 2007 04:23:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070327085429.GA20910@xxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070327085429.GA20910@xxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi, Daniel

Thank you for your description.
Now I understand libvirt policy and why code is complex.
Anyway I will track on this.

Thanks
Atsushi SAKAI


Daniel Veillard <veillard@xxxxxxxxxx> wrote:

> On Tue, Mar 27, 2007 at 10:27:23AM +0900, Atsushi SAKAI wrote:
> > Hi, Jerone.
> > 
> > Thank you for your info.
> > It needs to fix, I will fix this issue.
> > (I check up to xen-3.0.4 but for xen-3.0.5 is not yet.
> > The structure changes from xen-3.0.4 to xen-3.0.5.) 
> 
> Yes as Dan Berrange pointed out that's something in our TODO list.
> It's a good idea to start working on a patch if you have time for
> this, but note that I won't apply it until 3.0.5 is officially 
> released, in the past we have seen hypervisor call changes just
> before releases, so...
> 
> > But I hope xen_internal.c should switch libxc.
> > Any reason of libvirt stay on original code? 
> 
>   First libxc is GPL'ed and libvirt is LGPL'ed, if we relied on 
> libxc that would affect any program using libvirt from a licencing
> point of view, making it far less attractive in my opinion.
>   Second we aim at providing compatibility with any released version
> of the xen hypervisor, so when 3.0.5 is out we will need to adapt the
> code again and check the hypervisor_version (and subversion) and possibly
> add more switch cases to handle the new version.



_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel