virt

virt@lists.centos.org

2 participants
1613 discussions

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing
by President 21 Jan '16

21 Jan '16

My .02 is to stay the course. As a server admin, I want to be able to type things like: yum upgrade php not yum upgrade php55-epel-rpmforge-fancy-package Having to remember all the idiosyncrasies of a system is what causes some type of major failure in the future whenever (1) you forget something or (2) someone else has to pick up the box to adminster. -- Craig Thompson, President Caldwell Global Communications, Inc. +1 (423) 559-5465 caldwellglobal.com -----Original message----- From: George Dunlap <dunlapg(a)umich.edu> Sent: Thursday 21st January 2016 7:32 To: Discussion about the virtualization on CentOS <centos-virt(a)centos.org> Subject: Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing On Thu, Jan 21, 2016 at 12:01 PM, Peter <peter(a)pajamian.dhs.org> wrote: > On 15/01/16 05:57, George Dunlap wrote: >> As mentioned yesterday, Xen 4.6 packages are now available for >> testing. These also include an update to libvirt 1.3.0, in line with >> what's available for CentOS 7. Please test, particularly the upgrade >> if you can, and report any problems here. > > Per conversation in IRC, Xen 4.6 no longer includes xend and therefore > no longer has the "xm" command. This is problematic for people who may > be using xm in various scripts on their host (such as home-brewed backup > scripts). > > I think it's a bad idea to break this functionality without warning by > allowing a simple "yum update" to remove it. You will take a lot of > people by surprise and cause such scripts to stop working, if people are > running yum cron the situation becomes even worse. Thanks, PJ, for your input. Just to be clear: 1. In the Xen 4.4 packages (first released October 2014), xend was disabled by default; so anyone using xend at the moment has already manually intervened to enable deprecated functionality 2. In 4.4, the first time xm was executed, it printed this warning: --- xend is deprecated and scheduled for removal. Please migrate to another toolstack ASAP. See http://wiki.xen.org/wiki/Choice_of_Toolstacks for information on other alternatives, including xl which is designed to be a drop in replacement for xm (http://wiki.xen.org/wiki/XL) --- 3. ...and on every subsequent invocation, it printed this warning: "WARNING: xend/xm is deprecated" I think this constitutes "warning" that the functionality was going to break at some point. :-) Also, in most cases "s/xm/xl/g;" Just Works; most people have reported that changing from xm -> xl was pretty painless. So this isn't like upgrading from Python 2 to Python 3 (or QT 4 to 5, or...). > I think that due to this lack of backwards compatibility with Xen 4.4 > and earlier versions it would be a good idea to not force the upgrade on > people who are not wary of it. I propose that the new packages carry > the name "xen46" and they purposefully conflict with the old "xen" > packages. That will require people to take positive action to do the > upgrade and hence avoid breaking systems unintentionally. This would avoid breaking things for people still using xm, which certainly has some value. However it has some costs: * The packages between C6 and C7 will now be slightly different, increasing the maintenance burden. This is not only in the spec file, but also in all the associated scripting machinery for managing packages in the CBS and smoke-testing packages before pushing them publicly. * Instructions for installing Xen are now differend between C6 and C7, and slightly more complicated, as they have to explain about Xen 4.6 vs alternatives. * Users who have heeded the warning and switched to xl will have to make an extra effort to switch to Xen 4.6. If they don't follow centos-virt, they may not notice that there's a new package to upgrade to. I'm a developer, not a server admin, so I can't gauge how important this issue is. Before making such a change, I'd like to hear opinions from other people in the community about how important (or not) it is to avoid breaking xm, given the ample warning (>1 year) users have had. On the other hand, explicitly moving to a "xen${VER}" (both for C6 and C7) would make it simpler for people to step up and maintain older versions in parallel if anybody wanted to do so. Thanks again, Peter, for bringing this up. Peace, -George _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org https://lists.centos.org/mailman/listinfo/centos-virt

5 11

Re: [CentOS-virt] DomU Guests not shutting down nicely when Dom0 Hypervisor shuts down
by Keith Roberts 21 Jan '16

21 Jan '16

Hi Francis. Personally I would gracefully shutdown all the VM’s first, before attempting to shutdown the xen hypervisor. Are you getting any fsck errors when restarting those VM’s? Kind Regards, Keith On 21 Jan 2016, at 08:48, Francis Greaves <francis(a)choughs.net> wrote: > I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.? on CentOS 6.5 on my previous system. I installed using yum install centos-release-xen. > On shutting down the Hypervisor it used to wait for the DomUs to shut down gracefully (one can take a minute or more), then on starting up again it would restart the DomUs, all nice and controlled. > For some reason the DomUs (CentOS or Ubuntu servers) are not shutting down nicely when the Hypervisor is shutdown, and not restarting. I have the cfg files in /etc/xen/auto so they should start up. > If I forget to shut down the DomU guests then the shutdown hangs. > I am running this on a Dell Poweredge T430 by the way. > Any ideas why, and how to cure this? > _______________________________________________ > CentOS-virt mailing list > CentOS-virt(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-virt

1 0

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt