Xen 4.4 heading for Rawhide

[M A Young]

I am planning to update the xen package in Rawhide to version 4.4.0 in the 
next few days. The xend functionality including the xm command is now an 
optional extra which I was intending to leave out. Is that likely to cause 
problems with libvirt? Also, this version makes it easier to use upstream 
qemu, but Fedora qemu currently builds without xen support. How easy would 
it be to change this (after xen has been updated)?

 	Michael Young

[Cole Robinson]

On 03/20/2014 05:40 PM, M A Young wrote:
>  I am planning to update the xen package in Rawhide to version 4.4.0
> in the
>  next few days. The xend functionality including the xm command is now an
>  optional extra which I was intending to leave out. Is that likely to cause
>  problems with libvirt? 
I don't think it should matter much. libvirt ships two driver subpackages, one
for xend and one for libxl, but they both map to the xen:/// URI which will
only use xend if xend is running.

People might be doing 'yum install libvirt-daemon-driver-xen' which won't
give
them what they want anymore, but I think that's fine given that xend isn't
shipped anymore. Maybe we should stop distributing the libvirt package as
well, but then again we already ship libvirt drivers for stuff not in fedora
like virtualbox, esx, etc. so not sure what the policy is there.

Also, this version makes it easier to use upstream
>  qemu, but Fedora qemu currently builds without xen support. How easy
> would it
>  be to change this (after xen has been updated)? 
Pretty easy I think. I'm happy to do it ahead of time too, just let me know
when you want the build.

- Cole

[M A Young]

On Fri, 21 Mar 2014, Cole Robinson wrote:

> > Also, this version makes it easier to use upstream
> > qemu, but Fedora qemu currently builds without xen support. How easy would it
> > be to change this (after xen has been updated)?
>
>  Pretty easy I think. I'm happy to do it ahead of time too, just let me know
>  when you want the build. 
Thanks. I have now built xen-4.4.0 on Rawhide. It wouldn't have been worth 
building qemu beforehand as the xen library versions change with this 
update, and the xen setting is just where to find qemu.

Libvirt will presumably also need to be rebuilt for the same reason.

 	Michael Young

[Cole Robinson]

On 03/23/2014 04:14 PM, M A Young wrote:
>  On Fri, 21 Mar 2014, Cole Robinson wrote:
>  
> >> Also, this version makes it easier to use upstream
> >> qemu, but Fedora qemu currently builds without xen support. How easy would it
> >> be to change this (after xen has been updated)?
> >
> > Pretty easy I think. I'm happy to do it ahead of time too, just let me know
> > when you want the build.
>  
>  Thanks. I have now built xen-4.4.0 on Rawhide. It wouldn't have been worth
>  building qemu beforehand as the xen library versions change with this update,
>  and the xen setting is just where to find qemu.
>  
>  Libvirt will presumably also need to be rebuilt for the same reason.
>   
Thanks, builds in progress for libvirt and qemu with xen enabled.

- Cole

[Major Hayden]

I'm a libxl user but I know quite a few people still using xm/xend for the
functionality it provides or because it's what they're used to.  Can we do
something documentation-wise to alert users that xm/xend isn't available any longer
and how they could migrate to using libxl?

There's some documentation here that might be good to reference:

  http://wiki.xen.org/wiki/MigrationGuideToXen4.1%2B#Toolstack_upgrade_notes

--
Major Hayden

On Mar 20, 2014, at 16:40, M A Young <m.a.young(a)durham.ac.uk&gt; wrote:

>  I am planning to update the xen package in Rawhide to version 4.4.0
> in the next few days. The xend functionality including the xm command is now an optional
> extra which I was intending to leave out.