While trying to verify any potential problem between with libvirt & Xen PPC port. I've found that libvirt currently in CVS attempts to determine what hypercall version to follow, by looking at the hypervisior version. It determines that this is some arbitrary versioning "v2" of the hypercall api. This starts on line 1250 of xen_internal.c. This does not appear to be compatible with current Xen-Unstable from testing and trying to hack it up. Has any work been done toward making libvirt compatible with Xen-unstable that has not been included? Or is it waiting till the offical 3.0.5 release? We are attempting to ensure that Xen PPC works with libvirt. Though we have to use the latest hypercall api. Thanks, Jerone -- Libvir-list mailing list Libvir-list(a)redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

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.