virt November 2015

virt@lists.centos.org

16 participants
16 discussions

Libvirt enhancement requests
by Nux! 08 Nov '15

08 Nov '15

Hi folks, I know you're rebuilding livbirt for the SIG. Would it be possible to enable RBD support in it? I know quite a few cases (in the Cloudstack community) that switched to Ubuntu particularly because CEPH support was missing. The recommendation is to rebuild the rpms, but this is not a viable thing for everyone. E.g. http://blog.widodh.nl/2015/04/rebuilding-libvirt-under-centos-7-1-with-rbd-… Another thing that I noticed on the CentOS ml recently is an alleged lack of hooks, https://www.libvirt.org/hooks.html And last but not least, where could I find the libvirt (s)rpms that the SIG produces? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

4 12

CVE-2015-7835
by Jens Larsson 05 Nov '15

05 Nov '15

Hi, There was new packages (4.4.3-3) released on Oct 29, but they don't address the CVE-2015-7835 problems. Does anyone have news about a rebuild with this fix applied? Or should we make our own build? /jens

2 3

Plan to update to Xen 4.6
by George Dunlap 03 Nov '15

03 Nov '15

When we started the Virt SIG, our stated goal was to support one recent version of Xen with a recent kernel. We updated at that time to Xen 4.4, as the most recent stable release. We skipped 4.5; but now with 4.6 out, I think it's about time to upgrade. Moving to 4.6 has several distinct advantages for CentOS 7. Xen 4.4 has no systemd integration, while Xen 4.6 does. Additionally, Xen 4.4 has an insufficient level of ARM support, while Xen 4.6 does. The Xen releases are heavily tested upstream, not only by the open-source team, but by the vendors who build their products on Xen. I'm fairly confident that moving forward to Xen 4.6 should be a relatively safe maneuver for most people. So I shall be moving towards releasing Xen 4.6 for CentOS 6 in the not too distant future. That said, the Virt SIG is a community effort -- if anyone in the community wants to step up and maintain the Xen 4.4 packages within the SIG, they would be welcome to do so. The burden of doing the maintenance should not be too high. Security updates will continue for 4.4 until the 4.6 packages are fully ready (and may continue for a month or two afterwards, depending on severity, to provide a transition period). -George

2 1

Kernel 3.18.21-16 and Xen 4.4.3-3 released into Xen4CentOS repo for CentOS 6
by Johnny Hughes 02 Nov '15

02 Nov '15

I have released to the master mirror the following packages for Xen4CentOS: b518e3b0fd4f735b34d7784815793cb787283d9029776bd9794cedeb274b9204 kernel-3.18.21-16.el6.x86_64.rpm 4b17373a0ef6806b26d02eb87fc299020beb60b6e31ed08a9c57d30a1410fbe7 kernel-devel-3.18.21-16.el6.x86_64.rpm cacedf6771849f7525145ad4ed7d36a2cad5b49b546173bb7c132b236cb7ac49 kernel-doc-3.18.21-16.el6.noarch.rpm 22479ee9c2d3748edb08b410514d12c17ad966bcc2c067c48deedf732ae62aae kernel-firmware-3.18.21-16.el6.noarch.rpm 5d7cd57276f8755c8c312149888956f230ed356bc753117365b4ad7df7b1bf69 kernel-headers-3.18.21-16.el6.x86_64.rpm 99f65bb828a4d1f9ee25c77d0c71b3d88eba93fcf3fb0babf6c10379d426e5b3 perf-3.18.21-16.el6.x86_64.rpm 616a1fd6689f214f10dce7b70eb1984e60371edb8341140ddd0b4850fa9705de xen-4.4.3-3.el6.x86_64.rpm 2a9584266af525126e7b6a2fa2eeac3757aa63bc6636a8393e0b65e6f4694a42 xen-devel-4.4.3-3.el6.x86_64.rpm 4ac658cd679ba54496ea82e018ec89156620b2e4c93ef93c3afcfd0956b22f9e xen-doc-4.4.3-3.el6.x86_64.rpm ebfd368aa03a16a1c943afbda8795b631a88a800edcb0650903620928264ab48 xen-hypervisor-4.4.3-3.el6.x86_64.rpm c2fa54596923d000e32cd5e96982a06b95ac9a9d1c20655ea3371d44620a2f0e xen-libs-4.4.3-3.el6.x86_64.rpm a2481c5a3e55d20028f90c1b44195cfb64f22a34f9956ee67ce3a7d1bd9a24ea xen-licenses-4.4.3-3.el6.x86_64.rpm 283a3052c17735103aef249b3c183b5d9781f76f110dff3d585425af276d0e50 xen-ocaml-4.4.3-3.el6.x86_64.rpm f2058a63167d3f0781ab71267b7c10132b18c836d7d4d8bd78214d88d930f5e3 xen-ocaml-devel-4.4.3-3.el6.x86_64.rpm 43ed7df8e5fb1e836e84f3c517726a6f0512ac6afbbc2eec4af76a39a8cb9eae xen-runtime-4.4.3-3.el6.x86_64.rpm These changelog entries are applicable for the new kernel compared to the previously released version: https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.21 https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.20 https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.19 https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.18 The xen updates roll in: * Thu Oct 29 2015 George Dunlap <george.dunlap(a)citrix.com> - 4.4.3-3.el6.centos - Update fix for XSA-150 * Thu Oct 22 2015 George Dunlap <george.dunlap(a)citrix.com> - 4.4.3-2.el6.centos - Import XSAs 149-153 Thanks, Johnny Hughes

4 4

Differences between qemu-kvm and qemu-kvm-ev
by C. L. Martinez 02 Nov '15

02 Nov '15

Hi all, What are the real technical difference between qemu-kvm and qemu-kvm-ev packages? What are the advantages to use qemu-kvm-ev (if exists someone)? Or qemu-kvm-ev makes sense when is used with ovirt only?? Thanks.

4 5

Errors with virt-manager
by C.L. Martinez 02 Nov '15

02 Nov '15

Hi all, When I try to connect to a remote KVM host from my CentOS workstation (both are CentOS 7.1 fully patched) using virt-manager (ssh+qemu), the following error is displayed: Error launching connect dialogue: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 714, in _do_show_connect self._get_connect_dialog().show(src.topwin, reset_state) File "/usr/share/virt-manager/virtManager/connect.py", line 143, in show self.start_browse() File "/usr/share/virt-manager/virtManager/connect.py", line 273, in start_browse service, domain, flags) File "/usr/lib64/python2.7/site-packages/gi/overrides/Gio.py", line 171, in __call__ None) GError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files Searching about this error, I have found this patch: https://www.redhat.com/archives/virt-tools-list/2014-December/msg00165.html But applying this solution doesn't resolves the problem. Any idea why?

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt November 2015