virt

virt@lists.centos.org

1608 discussions

Using network-script with Xen 4.4.1 (aka what will I do without xend?)
by Gene 01 Feb '15

01 Feb '15

I normally use the network-script parameter in the '/etc/xen/xend-config.sxp' configuration file to configure network bridges. However, the latest release of Xen4CentOS (which comes with Xen 4.4.1) has xend disabled by default. Can I continue to use network-script without xend? If not what is the recommended method for automatically configuring network bridges with the latest release of Xen4CentOS? I know I can just enable xend to continue using this script, but since Xen 4.5 is apparently dropping xend altogether I figure I should change my standard configuration starting now. Thanks in advance for your time. -Gene

5 5

libvirt errors after applying RPMS from 2015:X002
by rgritzo 30 Jan '15

30 Jan '15

folks: after applying the updated rpms from advisory 2015:X002 i am having problems with libvirtd, and with virt-manager. if i run libvirtd in the foreground and look at the error messages, the error i see is 2015-01-29 04:45:27.342+0000: 6477: error : virDBusGetSystemBus:1742 : internal error: DBus support not compiled into this binary and virt-manager is unable to connect to the hypervisor. this started after i applied the subject patches. is this an issue with the recent versions of libvirt? anybody else seeing this behavior? btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64 thanks in advance. -- rgritzo(a)gmail.com

2 1

Making the bi-weekly VIRT SIG call's IRC only
by Lars Kurth 27 Jan '15

27 Jan '15

Hi all, at today's call we decided to make the meetings going forward IRC only. If I don't get any objections by next Tue, I will update invites and wiki Regards Lars

2 1

oVirt - Virt / Storage cross SIG dependencies
by Sandro Bonazzola 27 Jan '15

27 Jan '15

Hi, I've seen that gluster is now available in CentOS Storage SIG[1]. Upstream we're currently requiring to enable the gluster 3.6 repository in order to use suche storage for oVirt managed VMs. But while we're planning how to package for CentOS VIrt SIG we're interested in how to depend on inter-SIG dependencies and use gluster from within the CentOS Storage SIG instead of requiring upstream gluster repository. Do we need to require something like " Should we require centos-release-gluster[2] from something like centos-release-ovirt and then just require gluster? When is centos-release-gluster planned to land in extra? Any hint or suggestion? [1] http://lists.centos.org/pipermail/centos-devel/2015-January/012686.html [2] http://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

Minutes of Jan 27 2015 VIRT SIG Meeting
by Lars Kurth 27 Jan '15

27 Jan '15

Hi all, seems we are making good progress. Thank you everyone! * First Xen release via the SIG is imminent (see Xen section) * We are also close to a Docker release (see Docker section) * We also need to look at cross-SIG dependencies to be able to make use of Gluster support in the Storage SIG (see oVirt section) Regards Lars = Attendees = * Lars Kurth * George Dunlap * Sandro Bonazzola * Lokesh Mandevar = Agenda = == Replace audio meetings in favor of IRC meetings, which seem to work better == <All agree with IRC meetings> ACTION :Send mail to list: If anyone objects, let us know. ACTION: Lars to changeg invite and wiki to reflect IRC meetings always. == Xen Update (George) == 4.4.1 Virt-Sif testing for several weeks now. Everything appears to be working Have a wiki now: covering xend to libxl migration - see http://wiki.centos.org/HowTos/Xen/Xen4QuickStart Jonny has pushed the signed packages Thus, this is the 1st Xen release from the VIRT SIG ACTION: George to send quick mail to the list and write up a blog post. CC publicity@xenproject and KB such that he can cross post to the CentOS blog if he wants to Note: 4.4.1 is still using the new old 3.10 kernel. DISCUSSION: George: do we have a conflict on kernel versions for CentOS 7. For xen we would need to override the CentOS 7 kernel to make Xen work with CentOS 7 Lokesh: there is no kernel requirement for Docker except that the kernel needs to be >= 3.10 – this should be a match George: potential issue is that Docker is officially supported in RHEL/ CentOS 7 Lokesh: 3.14 should work for Docker, but needs to be verified. George: before we push to public repo we need to test it. Lokesh: CentOS and Docker are tested with 3.10. For Fedora we test with 3.18. Docker has its own test suite. So covering 3.14 should be straightforward George: would you mind if I uploaded 3.10 and see whether it works? But there may be an issue that we would be missing RedHat backports in CentOS 7 Lokesh: Since yesterday have been doing a daily test for rawhide in addition to the stable branch. I don't think there should be an issue George: Checking understanding that a new kernel is totally OK. Lokesh: As long as we are not disabling standard kernel functionality we are fine ACTION: George upload the latest kernel and coordinate with Lokesh re testing to ensure that nothing breaks = Docker update (Lokesh) = Still on 1.4.1 Yesterday I was talking to Jim and KB re a daily rebuild for CentOS and that should be fine Maybe we will have an additional package Docker-upstream or Docker-unsupported (TBD) I have also been talking to people from Kubernetes and Cockpit re new versions. ACTION: Lokesh to make an announcements on the list(s) and then we can try and make a public release. ACTION: Lokesh to create a getting started wiki page ACTION: Lars to link to any announcements in FOSDEM VIRT SIG presentation = oVirt update (Sandro) = 3.5.1 is upstreamed and released Now we have a bit more time to investigate CBS, etc. We also have credentials for wiki and CBS Sandro: I had asked for some HowTo for CBS / Coogee by mail, which is still unresolved George: has some runes for basic stuff which he can share ACTION: George to create brief howto and share on list/wiki. One of the other issues Sandro brought up is that the Storage SIG now has Gluster support and that he would like to build oVirt with support from Gluster packages in the storage SIG. There may a requirement for QEMU and KVM packages (details needed) from that SIG. George: this will require some cross-SIG coordination that we need to resolve. At the moment we don’t have a way to cover inter-SIG dependencies ACTION: Sandro email storage SIG (via centos-devel) and virt SIG and lay out problem to kick off a discussion. Lars can try and follow up with KB and others at FOSDEM. = Any other business = None

1 0

New Xen 4.4 and Libvirt 1.2 rpms are Live in the CentOS 6.6 Xen4 repo
by Johnny Hughes 27 Jan '15

27 Jan '15

The new Xen 4.4.1-5 and LibVirt 1.2.10-3 RPMs that were being tested via this list are now live in the main Xen4CentOS repo for CentOS-6.6: http://lists.centos.org/pipermail/centos-announce/2015-January/020904.html Thanks, Johnny Hughes

1 0

Reminder: CentOS Virt SIG teleconf tomorrow (27 Jan), 2pm GMT
by Lars Kurth 26 Jan '15

26 Jan '15

Hey all, Just a reminder that we'll be resuming our bi-weekly Virt SIG meeting The meeting is by teleconf tomorrow. If you don't have the details let me know and I will add you. Also, I can send you the details on IRC a few minutes before the call, if you ping me. Basic agenda: * Xen update * Docker update * oVirt update * Replace audio meetings in favour of IRC meetings, which seem to work better * Any other business Please let me know if you have any other topics you'd like to bring up. -Lars

1 0

kvm guest from zfs dataset
by aurfalien 22 Jan '15

22 Jan '15

Hi all, I thought I’d post this in case any one has issues similar to mine. First, my initial email to the list which I didn’t send; I’m trying to run a KVM based guest OS off of a mirrored ZFS dataset. It won’t run with errors "invalid argument..", but will run when on the root volume, or when that ZFS dataset has been removed in favor of an EXT4 volumes. Thanks in advance, PS I do see this thread which is not promising; http://www.redhat.com/archives/redhat-list/2014-July/msg00017.html Lastly, the solution; Set your cache policy on the KVM guest as write back. This allows it to run on a ZFS volume. My apology if this has been covered. I did spend some time on this so hopefully you can save time by setting the cache policy. - aurf "Janitorial Services"

3 2

Xen 4.4 + libvirt 1.2 rpms test report with xl/libxl on CentOS 6
by Pasi Kärkkäinen 20 Jan '15

20 Jan '15

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

3 3

SIG repo layout and conflicts between projects within a SIG
by George Dunlap 20 Jan '15

20 Jan '15

At the moment, we're essentially using yum repos as the "patch" mechanism to CentOS Base: SIGs populate a repo with packages they want to add / override, and all other packages default to Base. The current setup is that every sig has exactly one production repo per CentOS version. Also, we seem to be wanting to see SIGs not as individual projects, but to make the 'G' an actual "group": so, for instance, the Virt SIG has both Xen and Docker, and we've recently approved oVirt. But there's a bit of a conflict here: what if one project in the SIG wants to use the package from Base, and another project in the SIG wants to use a custom-built package? Or what if both projects want to customize their packages in different ways? In particular: the Docker project in the Virt SIG wants to supply updated versions of Docker; but at the moment uses the kernel package from Base. The Xen project, on the other hand, needs to supply a different kernel package that has dom0 support enabled. Up until this point, this hasn't been an issue because I've been doing Xen development in virt6-testing, and Lokesh has been doing Docker development in virt7-testing. But I'm hoping to get Xen for CentOS 7 out soon, and I was just about to upload the Xen kernel to the CBS, when it occurred to me that if I did so, then everyone using the virt7-testing repo for Docker would suddenly get my updated kernel as well. So it seems we have a couple of ways to approach it. 1. Keep it one repo per SIG, and make all projects in a SIG sort out shared dependencies. 2. Allow one repo per *project* within a SIG (e.g., virt6-xen, virt7-docker) 3. Have some alternate way of doing a "patch", instead of repos. In the case of xen / docker, I haven't talked with Lokesh about this at all; it may be that he's fine with sharing a kernel with Xen. But it does increase the workload: now Lokesh needs to maintain the Docker side of the kernel, whereas before they could just rely on our upstream to do a lot of that testing. Furthermore, it increases the complexity of development and testing: before when doing kernel work, I could just test Xen; now the kernel needs to be tested by both Xen and Docker. And finally, now users of both projects get a kernel update whenever either one does. Which, of course, is pretty much the same as any other distro; but as a whole, at the moment at least, we have a lot less resources than any other distro our size and popularity. On the whole I'm inclined to prefer #2. Thoughts? -George

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt