virt November 2015

virt@lists.centos.org

16 participants
16 discussions

Resigning as lead of the Virt SIG
by Lars Kurth 09 Jan '16

09 Jan '16

Hi all, I wanted to let you know that I feel I need to step down as leader of the Virtualisation SIG. When I originally was approached by KB to do this, it was always clear that this would be a temporary thing until the SIG got going. At the time, only Xen and CentOS folks were involved with the SIG. Since then, we added oVirt and Docker maintainers, have a total of 5 maintainers and built good momentum. There are two reasons why I feel I should step down as leader of the Virt SIG: a) I have been traveling too much and thus did not have the bandwidth to do this job justice in recent months. b) In addition, it would also make more sense for one of the Virt SIG maintainers who is more closely involved with day-to-day activities to pick up this job. I will still be able to help with PR and other items. When I was absent over the last few months, George Dunlap (gwd on irc) did most of the groundwork and led SIG meetings on my behalf, so I wanted to propose that George leads the SIG going forward. That is assuming that none of the other SIG maintainers want to step up. George agreed in principle. In the last Virt SIG meeting, not all maintainers were present, so we couldn't make a formal decision. KB said the following: kbsingh: I think if gwd is ok with it, and people are ok in the SIG, its good for me This means that succession either has to be settled in the next SIG meeting, or by e-mail responding to this thread. I don't think there is any formal process, but I would suggest that the maintainers listed on https://wiki.centos.org/SpecialInterestGroup/Virtualization should have a say either at the next IRC meeting or by replying to this email thread. Best Regards Lars

5 4

kvm-qemu-ev in testing
by Karanbir Singh 19 Dec '15

19 Dec '15

hi, kvm-qemu-ev from virt7-kvm-common-release is now signed and available on buildlogs.centos.org for testing, the corresponding release file is available in the centos/7/extras/ location on buildlogs as well. Once we have some testing, we can push and announce via mirror.centos.org for wider adoption. Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

7 11

new install of Xen 4.6 hangs on Loading initial ramdisk
by Craig Thompson 30 Nov '15

30 Nov '15

First post to this list. I would appreciate some help on this issue. As background, I installed CentOS 7 on a Dell server, and then ran the following commands: yum update http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-1… yum --enablerepo=centos-virt-xen-testing update yum --enablerepo=centos-virt-xen-testing install xen Doing that, I was able to successfully install Xen, create a virtual machine with its own HVM setup, logical volume, etc. and boot it just fine. I then tried to do the same on an IBM x3550 server I’m trying to install with CentOS 7. The CentOS 7 install went just fine. I can boot into the standard kernel and have a working machine. But after running the commands above to install the Xen hypervisor, the machine hangs on boot for a few moments after displaying the lines below and then reboots in a loop over and over and over: Loading Xen 4.6.0-2.el7 … Loading Linux 3.18.21-16.el7.x86_64 … Loading initial ramdisk … It never gets beyond that. If I choose the stock kernel (no Xen) from the Grub menu, it will continue to boot into that just fine. My grub.cfg file has these entries of note: multiboot /xen-4.6.0-2.el7.gz placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all ${xen_rm_opts} echo 'Loading Linux 3.18.21-16.el7.x86_64 ...' module /vmlinuz-3.18.21-16.el7.x86_64 placeholder root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde ro crashkernel=auto debug irqpoll ipv6.disable=1 console=hvc0 earlyprintk=xen nomodeset echo 'Loading initial ramdisk ...' module --nounzip /initramfs-3.18.21-16.el7.x86_64.img What I have tried: 1) adding debug into the vmlinuz line 2) disabling ipv6 in that line 3) adding root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde to the last line AFTER /initramfs …. Nothing so far has made any difference. Obviously the process works, as it works for me just fine on the Dell server. Underlying this machine is a SATA RAID 1 PCI card with two SSD drives attached in a RAID 1 mirror. Not that that should matter, but I’m including it for reference. As noted previously, it boots into the stock kernel just fine. Any help would be appreciated. -- Craig Thompson, President Caldwell Global Communications, Inc. 423-559-5465 ------------------------------------ This message has been scanned by WingNET for spam & virus content. If you get spam regularly, contact us at sales(a)wingnet.net for e-mail filtering.

3 2

No separate XSA-162 package
by George Dunlap 30 Nov '15

30 Nov '15

Hey all, just a heads-up: XSA-162 [1] was released to the public this morning at 0600 UTC. It is, however, a bug in a non-default network card with a simple work-around (don't use that network card). Since there are a large number of updates due next week, and this is a fairly low-priority one, I decided not to do a package release specifically for it, and to include all the updates (through XSA-163) in the release I'll do next week. Peace, -George [1] http://xenbits.xen.org/xsa/advisory-162.html

1 0

Re: [CentOS-virt] CentOS-virt Digest, Vol 99, Issue 17
by bob vargas 29 Nov '15

29 Nov '15

Re: Contents of CentOS-virt digest... Best regards, Bob Vargas On Sat, Nov 28, 2015 at 7:00 AM, <centos-virt-request(a)centos.org> wrote: > Send CentOS-virt mailing list submissions to > centos-virt(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos-virt > or, via email, send a message with subject or body 'help' to > centos-virt-request(a)centos.org > > You can reach the person managing the list at > centos-virt-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS-virt digest..." > > > Today's Topics: > > 1. new install of Xen 4.6 hangs on Loading initial ramdisk > (Craig Thompson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 27 Nov 2015 18:18:05 -0500 > From: Craig Thompson <president(a)caldwellglobal.com> > To: centos-virt(a)centos.org > Subject: [CentOS-virt] new install of Xen 4.6 hangs on Loading initial > ramdisk > Message-ID: <0229360F-F45E-4C83-9CB8-4FE9BB79B306(a)caldwellglobal.com> > Content-Type: text/plain; charset="windows-1252" > > First post to this list. I would appreciate some help on this issue. > > As background, I installed CentOS 7 on a Dell server, and then ran the > following commands: > > yum update > http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-1… > yum --enablerepo=centos-virt-xen-testing update > yum --enablerepo=centos-virt-xen-testing install xen > > Doing that, I was able to successfully install Xen, create a virtual > machine with its own HVM setup, logical volume, etc. and boot it just fine. > > I then tried to do the same on an IBM x3550 server I?m trying to install > with CentOS 7. The CentOS 7 install went just fine. I can boot into the > standard kernel and have a working machine. But after running the commands > above to install the Xen hypervisor, the machine hangs on boot for a few > moments after displaying the lines below and then reboots in a loop over > and over and over: > > Loading Xen 4.6.0-2.el7 ? > Loading Linux 3.18.21-16.el7.x86_64 ? > Loading initial ramdisk ? > > It never gets beyond that. If I choose the stock kernel (no Xen) from the > Grub menu, it will continue to boot into that just fine. > > My grub.cfg file has these entries of note: > > multiboot /xen-4.6.0-2.el7.gz placeholder dom0_mem=1024M,max:1024M > cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all > ${xen_rm_opts} > echo 'Loading Linux 3.18.21-16.el7.x86_64 ...' > module /vmlinuz-3.18.21-16.el7.x86_64 placeholder > root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde ro crashkernel=auto debug > irqpoll ipv6.disable=1 console=hvc0 earlyprintk=xen nomodeset > echo 'Loading initial ramdisk ...' > module --nounzip /initramfs-3.18.21-16.el7.x86_64.img > > > What I have tried: > > 1) adding debug into the vmlinuz line > 2) disabling ipv6 in that line > 3) adding root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde to the last line > AFTER /initramfs ?. > > Nothing so far has made any difference. Obviously the process works, as > it works for me just fine on the Dell server. > > Underlying this machine is a SATA RAID 1 PCI card with two SSD drives > attached in a RAID 1 mirror. Not that that should matter, but I?m > including it for reference. As noted previously, it boots into the stock > kernel just fine. > > Any help would be appreciated. > > -- > Craig Thompson, President > Caldwell Global Communications, Inc. > 423-559-5465 > > > > > ------------------------------------ > This message has been scanned by > WingNET for spam & virus content. > If you get spam regularly, contact us at > sales(a)wingnet.net for e-mail filtering. >

1 0

Install nested ESXi 6.x host under CentOS 7 kvm host
by C. L. Martinez 27 Nov '15

27 Nov '15

Hi all, I am trying to install nested Esxi 6.x under a Centos7 kvm host to use it as test lab for new ESXi versions, but I am doing something wrong because I can't install it. I have configured kvm and kvm_intel modules with the following options: options kvm ignore_msrs=1 options kvm_intel nested=1 ept=1 and I add the following options in <cpu> xml guest file: <cpu mode='custom' match='exact'> <model fallback='allow'>Westmere</model> <feature policy='require' name='vmx'/> </cpu> qemu-kvm package is installed from Virtualization SIG: qemu-kvm-common-ev-2.1.2-23.el7_1.8.1.x86_64 qemu-kvm-ev-2.1.2-23.el7_1.8.1.x86_64 Am I doing something wrong or is it not possible to accomplish this scenario?? Thanks.

3 6

CentOS 6 Xen package update (including XSA-156)
by George Dunlap 25 Nov '15

25 Nov '15

So going forward, we're moving the CentOS 6 Xen packages from the custom "xen4" repos that were introduced several years ago, to repos based on its position as a sub-project of the Virt Sig. That will make things consistent between all the sigs, as well as between CentOS 6 and 7 Xen packages. Unfortunately, XSA-156 came up rather suddenly and is a bit blocked by this transition. So please help us test the new repository structure, so that we can with conscience push the updates to xen4 users in general. To update to the new repository structure, install the centos-release-xen package directly from the new repo: yum update http://mirror.centos.org/centos/6/virt/x86_64/xen/centos-release-xen-7-11.e… This should replace the xen4 repositories with the new virt sig repositories. Now do a 'yum update': yum update This should pull in the Xen 4.4.3-6 package, which contains XSA-156 (and all other packages). If everything works as planned, we'll push the new centos-release-xen to centos-extras, and then everyone else will be moved to the new repos the next time they do an update. -George

4 15

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)
by Russell Gritzo 13 Nov '15

13 Nov '15

Just applied the repo update rpm and the 4.4.3-6 updates - no problems. I only saw one unexpected message in the 4.4.3-6 update - snippet below: <snip> Running Transaction Updating : xen-licenses-4.4.3-6.el6.x86_64 1/10 Updating : xen-libs-4.4.3-6.el6.x86_64 2/10 Updating : xen-hypervisor-4.4.3-6.el6.x86_64 3/10 /var/tmp/rpm-tmp.kxFl1h: line 9: fg: no job control Updating grub config Updating : xen-runtime-4.4.3-6.el6.x86_64 4/10 Stopping xenconsoled Stopping QEMU <snip> I went to look at the script in /var/tmp, but of course it is cleaned up... :} didnt seem to bother anything. r. ---

1 0

CentOS 7 Xen 4.6.0 packages available on buildlogs
by George Dunlap 11 Nov '15

11 Nov '15

At long last, we have the packages and the infrastructure set up in what will be (hopefully) the final form for the CentOS 7 Virt SIG Xen packages. Please help us by testing the packages and the infrastructure. To install the Virt SIG Xen repositories, install the CentOS 7 centos-release-xen package directly from buildlogs: yum update http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-1… Because the CentOS packages aren't released yet, they are only available on buildlogs, which are in the (disable-default) centos-virt-xen-testing repository. So first install the kernel: yum --enablerepo=centos-virt-xen-testing update Then install xen: yum --enablerepo=centos-virt-xen-testing install xen The version we're starting with is Xen 4.6, which has good systemd support as well as aarch64 support. The version on buildlogs has XSAs through 156 applied. Libvirt is also available, for those who are so inclined. Please report any bugs on this list. Thanks, -George

1 0

Updated packages for XSA-156 to be built starting at 12:01am UTC
by George Dunlap 09 Nov '15

09 Nov '15

As you may have noticed, XSA-156 is due to be released publicly at 12:01am tomorrow (10 November). I've prepped packages, and before I leave today will set a script to send them to the CBS at 12:01 exactly. Packages should end up in virt6-xen-44-candidate within probably half an hour after that. If something goes wrong, I'll try to have it sorted out when I come in tomorrow morning (usually around 10am UTC). -George

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt November 2015