virt January 2016

virt@lists.centos.org

24 participants
21 discussions

Start a nNew thread

Fw: new important message
by meows＠techie.com 20 Jan '16

20 Jan '16

Hello! New message, please read <http://ks.mpt.ru/up.php?axr> meows(a)techie.com

1 0

Fw: new important message
by meows＠techie.com 20 Jan '16

20 Jan '16

Hello! New message, please read <http://esportskart.com/however.php?lxlue> meows(a)techie.com

1 0

Xen kernel-3.18.25-17 EL6 and EL7 needs testing
by Johnny Hughes 20 Jan '16

20 Jan '16

There is a new xen kernel for centos-6 and centos-7 the needs testing in: http://cbs.centos.org/repos/virt6-xen-common-testing/x86_64/os/Packages/ and http://cbs.centos.org/repos/virt7-xen-common-testing/x86_64/os/Packages/ Thanks, Johnny Hughes

3 7

Virt SIG Xen updates for XSAs 167-169
by George Dunlap 20 Jan '16

20 Jan '16

xen-4.4.3-10.el6 and xen-4.6.0-9.el7, which contain patches for XSAs 167-169, are on their way to CentOS 6 and CentOS 7 Virt Sig Xen mirrors, respectively. As a reminder, this is the last security update for xen-4.4. Xen 4.6 for CentOS 6 is already available in centos-virt-xen-testing, and we will be pushing it to the main (mirrors) repository sometime this week. Peace, -George

1 0

Xen kernel-3.18.25-18 for EL6 and EL7 (CVE-2016-0728)
by Johnny Hughes 20 Jan '16

20 Jan '16

There is now a kernel-3.18.25-18 that fixes CVE-2016-0728 (and upgrades to the lastest 3.18 LTS kernel) for Xen4CentOS users. This kernel can be tested from here: http://cbs.centos.org/repos/virt6-xen-common-testing/x86_64/os/Packages/ (CentOS-6) and here: http://cbs.centos.org/repos/virt7-xen-common-testing/x86_64/os/Packages/ (CentOS-7) Once we get several tested installs we can move this to released. For more info on CVE-2016-0728: http://bit.ly/1nifPm4 There is info in the above link on testing the vulnerability is fixed .. see the code under 'Triggering the bug from userspace is fairly straightforward, as we can see in the following code snippet'. Reports that the kernel works, and that the CVE-2016-0728 issue is tested (before and after installing the new kernel) would be greatly appreciated on this thread. The following changelogs are also applicable in a upgrade from the current 3.18.21-17 release and this 3.18.25-18 release: https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.25 https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.24 https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.23 https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.22 Thanks. Johnny Hughes

1 2

How to debug kernel with kernel-3.10.68-11.el6
by Xiaoding (B) 19 Jan '16

19 Jan '16

Hi all I used kernel-3.10.68-11.el6 as dom0 and config kdump I have got vmcore file when compute crash, but not found debuginfo package from http://debuginfo.centos.org/ I found kernel-3.10.68-11.el6 set CONFIG_DEBUG_INFO=n Why not set this key? Is there any other method to debug when compute crash Best Wishes Ding

2 1

Networking Problem
by Günther J. Niederwimmer 14 Jan '16

14 Jan '16

Hello, I have two problems one big and the other small with my KVM System I have four NICs configured on my system, and I lost the most time on reboot one NIC ? I have all clients configured in the same way and I lost on all clients the same NIC ? The NICs are configured in virt-manager 2 x Hostdev ens10 ens9 1 x Bridge (virtio) eth1 // this is the Problem NIC 1x Isolated Network (virtio) eth0 I have configure two even Computers and have on all the same problem? have any a idea what is wrong with the Network? On a other System with three NICs near the same configuration all is working? The second Problem is, I can't disable the IPv6_PRIVACY on "ens9" I have all disabled in the Kernel I set it in the ifconf-ens9, but I have the most time a privacy IPv6 Address ? after a "systemctl restart network" the IPv6_PRIVACY is gone ? What is different on a boot initial and a systemctl restart network ? -- mit freundlichen Grüßen / best regards, Günther J. Niederwimmer

1 0

CentOS 6 Xen: XSAs 167-169, update to Xen 4.6
by George Dunlap 14 Jan '16

14 Jan '16

XSA 169 is out, but is low-priority and has a work-around, so I'm going to batch it together with XSAs 167-168 and release a new 4.4.3 package when the embargo is lifted next Wednesday. This will be the last XSA update for the 4.4.3 packages. Today or tomorrow I will push the Xen 4.6.0 packages to buildlogs for testing; and sometime after the final 4.4.3 packages are released, I will push the Xen 4.6 packages as the main Xen packages. The Virt SIG is a community project, so anyone wishing to maintain the Xen 4.4. packages going forward is welcome to step up to do so. -George

2 1

Welcoming a new SIG member :)
by Lokesh Mandvekar 13 Jan '16

13 Jan '16

Virt SIG folks, please join me in welcoming our latest SIG member, Marianne Lombard (username: jehane). She's been a Fedora contributor for quite sometime already, and will now be helping to ensure I'm not being a bottleneck RE: docker on CentOS virt :) Welcome aboard, Marianne. -- Lokesh Freenode: lsm5 GPG: 0xC7C3A0DD

3 2

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt January 2016