Re: [CentOS-virt] Xen 4.4 + libvirt 1.2 rpms test report with xl/libxl on CentOS 6

2015-01-20 Thread Lars Kurth
Hi all,

this is great news. So according to 
http://www.centos.org/minutes/2015/january/centos-devel.2015-01-13-14.06.html 
this means

 * Xen 4.4.1 rpms + libvirt 1.2.x (10?) have been in the repo since 
mid-december, and mostly there are positive things to say about it (sbonazzo, 
14:09:3
 * ACTION: pasik and any other volunteer to verify Xen 4.4.1 rpms + libvirt 
1.2.x + libvirt-libxl (sbonazzo, 14:16:18)
 * AGREED: people should start move off xend in 4.4 since it's been removed in 
4.5 (sbonazzo, 14:20:15)
 * ACTION: pasik to test xen 4.4 + libxl + libvirt + virt-manager amd report to 
virt-list (kbsingh, 14:25:39)

== We are here ==
 * ACTION: gwd to test the upgrade path from 4.2 to 4.4 ( xen ) and report to 
virt-list (kbsingh, 14:27:58)

 * AGREED: on releasing xen 4.4 rpms if able to close off the libivrt / 
virt-manager issues on email to the list (sbonazzo, 14:32:37)

Looks like we are close to release and may be set to do this for FOSDEM.

Regards
Lars


On 19 Jan 2015, at 15:43, Johnny Hughes joh...@centos.org wrote:

 On 01/17/2015 08:46 AM, Pasi Kärkkäinen wrote:
 On Fri, Jan 16, 2015 at 09:16:05PM +0200, Pasi Kärkkäinen wrote:
 Hello,
 
 As discussed on the last Virt SIG meeting I promised to do some libvirt + 
 libxl testing using the latest Xen 4.4 rpms.
 
 Versions used:
 
 xen-libs-4.4.1-5.el6.x86_64
 xen-licenses-4.4.1-5.el6.x86_64
 xen-hypervisor-4.4.1-5.el6.x86_64
 xen-4.4.1-5.el6.x86_64
 xen-runtime-4.4.1-5.el6.x86_64
 
 kernel-3.10.63-11.el6.centos.alt.x86_64
 
 libvirt-daemon-driver-nwfilter-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-xen-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-lxc-1.2.10-3.el6.x86_64
 libvirt-daemon-1.2.10-3.el6.x86_64
 libvirt-daemon-config-nwfilter-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-libxl-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-secret-1.2.10-3.el6.x86_64
 libvirt-python-1.2.10-2.el6.x86_64
 libvirt-daemon-driver-network-1.2.10-3.el6.x86_64
 libvirt-daemon-config-network-1.2.10-3.el6.x86_64
 libvirt-1.2.10-3.el6.x86_64
 libvirt-client-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-interface-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-nodedev-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-qemu-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-storage-1.2.10-3.el6.x86_64
 
 python-virtinst-0.600.0-25.el6.centos.alt.noarch
 
 
 And I forgot to add this:
 
 virt-manager-0.9.0-28.el6.x86_64
 
 I concur that this does work.  I created new machines in XL via
 virt-install, virt-manager, even via a CentOS-7 virt-manager connected
 to the xen machine.
 
 
 
 
 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org
 http://lists.centos.org/mailman/listinfo/centos-virt

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


Re: [CentOS-virt] Xen 4.4 + libvirt 1.2 rpms test report with xl/libxl on CentOS 6

2015-01-19 Thread Johnny Hughes
On 01/17/2015 08:46 AM, Pasi Kärkkäinen wrote:
 On Fri, Jan 16, 2015 at 09:16:05PM +0200, Pasi Kärkkäinen wrote:
 Hello,

 As discussed on the last Virt SIG meeting I promised to do some libvirt + 
 libxl testing using the latest Xen 4.4 rpms.

 Versions used:

 xen-libs-4.4.1-5.el6.x86_64
 xen-licenses-4.4.1-5.el6.x86_64
 xen-hypervisor-4.4.1-5.el6.x86_64
 xen-4.4.1-5.el6.x86_64
 xen-runtime-4.4.1-5.el6.x86_64

 kernel-3.10.63-11.el6.centos.alt.x86_64

 libvirt-daemon-driver-nwfilter-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-xen-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-lxc-1.2.10-3.el6.x86_64
 libvirt-daemon-1.2.10-3.el6.x86_64
 libvirt-daemon-config-nwfilter-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-libxl-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-secret-1.2.10-3.el6.x86_64
 libvirt-python-1.2.10-2.el6.x86_64
 libvirt-daemon-driver-network-1.2.10-3.el6.x86_64
 libvirt-daemon-config-network-1.2.10-3.el6.x86_64
 libvirt-1.2.10-3.el6.x86_64
 libvirt-client-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-interface-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-nodedev-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-qemu-1.2.10-3.el6.x86_64
 libvirt-daemon-driver-storage-1.2.10-3.el6.x86_64

 python-virtinst-0.600.0-25.el6.centos.alt.noarch

 
 And I forgot to add this:
 
 virt-manager-0.9.0-28.el6.x86_64

I concur that this does work.  I created new machines in XL via
virt-install, virt-manager, even via a CentOS-7 virt-manager connected
to the xen machine.






signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


[CentOS-virt] Xen 4.4 + libvirt 1.2 rpms test report with xl/libxl on CentOS 6

2015-01-16 Thread Pasi Kärkkäinen
Hello,

As discussed on the last Virt SIG meeting I promised to do some libvirt + libxl 
testing using the latest Xen 4.4 rpms.

Versions used:

xen-libs-4.4.1-5.el6.x86_64
xen-licenses-4.4.1-5.el6.x86_64
xen-hypervisor-4.4.1-5.el6.x86_64
xen-4.4.1-5.el6.x86_64
xen-runtime-4.4.1-5.el6.x86_64

kernel-3.10.63-11.el6.centos.alt.x86_64

libvirt-daemon-driver-nwfilter-1.2.10-3.el6.x86_64
libvirt-daemon-driver-xen-1.2.10-3.el6.x86_64
libvirt-daemon-driver-lxc-1.2.10-3.el6.x86_64
libvirt-daemon-1.2.10-3.el6.x86_64
libvirt-daemon-config-nwfilter-1.2.10-3.el6.x86_64
libvirt-daemon-driver-libxl-1.2.10-3.el6.x86_64
libvirt-daemon-driver-secret-1.2.10-3.el6.x86_64
libvirt-python-1.2.10-2.el6.x86_64
libvirt-daemon-driver-network-1.2.10-3.el6.x86_64
libvirt-daemon-config-network-1.2.10-3.el6.x86_64
libvirt-1.2.10-3.el6.x86_64
libvirt-client-1.2.10-3.el6.x86_64
libvirt-daemon-driver-interface-1.2.10-3.el6.x86_64
libvirt-daemon-driver-nodedev-1.2.10-3.el6.x86_64
libvirt-daemon-driver-qemu-1.2.10-3.el6.x86_64
libvirt-daemon-driver-storage-1.2.10-3.el6.x86_64

python-virtinst-0.600.0-25.el6.centos.alt.noarch


First I verified the baseline setup using xm/xend and libvirt:

- Install new PV domUs using virt-install, using LVM volumes.
- Install new PV domUs using virt-install, using file images (tap2).
- Install new PV domUs using virt-manager, using LVM volumes.
- Install new PV domUs using virt-manager, using file images (tap2).

And all that worked OK with xend, as we already know. tap2 backend was now 
automatically chosen for file images etc, all good.


Next I tried the same with xl/libxl. So I disabled xend with chkconfig xend 
off,
rebooted the server, and after the reboot verified xend is not running anymore.

And then I did the same PV domU installation tests as above.. and to my 
surprise it all worked out-of-the-box ! 
libvirt 1.2.10 seems to be happy with libxl aswell! Both virt-install and 
virt-manager worked OK for me for installing new guests,
and also for the basic lifecycle operations.


One difference compared to our earlier libvirt 0.x rpms is this:

# virsh version
Compiled against library: libvirt 1.2.10
Using library: libvirt 1.2.10
Using API: Xen 1.2.10
Running hypervisor: Xen 4.4.0

Now I get the same output from virsh version for both xm/xend and xl/libxl..
Earlier it would say Xen or xenlight on the Using API line depending 
which backend it was using.
I guess that has changed upstream, and both backends seem to work now anyway :)


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt