similar to: Virt SIG Xen updates for XSAs 167-169

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

On Wed, Feb 17, 2016 at 12:30 PM, George Dunlap <dunlapg at umich.edu> wrote: > I have the following packages going through the CBS: > * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 > * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 > * A CentOS 6 xen-4.4.3-11, with XSAs 170 > > All these should show up in mirrors hopefully sometime later today. > As usual, please report

I have the following packages going through the CBS: * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 * A CentOS 6 xen-4.4.3-11, with XSAs 170 All these should show up in mirrors hopefully sometime later today. As usual, please report any problems here. Xen 4.4 only has XSA 170 because at the time the embargo was lifted, I didn't have a suitable

My comment was targeted more at naming than support. I appreciate that there are vanishingly few resources to throw at support. I am glad to see any xen support for C7 and am thankful of all those who are putting in time to make things happen. I try to help out when I can but it is all too infrequently. On 01/21/2016 10:29 AM, Johnny Hughes wrote: > This is a community SIG .. and

Just a heads-up -- 4.6.3-2, for both CentOS 7 and CentOS 6, are making their way through the build system now and should be in the mirrors hopefully sometime later this afternoon. These contain patches for XSAs 185-188, one of which is a fairly critical update, so please update as soon as they're available. -George

Just a heads-up: A Xen package with XSAs through 163 is on its way through the build system. I'll send an announcement when I've tagged it as ready to be propagated to the mirrors. As with the last XSA update, it will depend on having manually updated to the new Virt SIG repository layout. If you haven't already please run the following in preparation: yum install

This is a community SIG .. and xenproject.org does NOT release XSAs for 4.2. The goal of Xen4centOS was to use an upstream LTS kernel and update those as required to stay on an LTS. Also to do every second point release of xen (ie, 4.2, 4.4, 4.6). All so we are longer term than upstream, BUT we have supported code from upstream. So, the goal is to use supported code for the longest amount of

On Sat, Feb 20, 2016 at 9:24 PM, Sarah Newman <srn at prgmr.com> wrote: > On 02/17/2016 04:30 AM, George Dunlap wrote: >> I have the following packages going through the CBS: >> * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 >> * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 >> * A CentOS 6 xen-4.4.3-11, with XSAs 170 >> >> All these should show up in

On 02/17/2016 04:30 AM, George Dunlap wrote: > I have the following packages going through the CBS: > * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 > * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 > * A CentOS 6 xen-4.4.3-11, with XSAs 170 > > All these should show up in mirrors hopefully sometime later today. > As usual, please report any problems here. Domains using the

On 23/02/16 15:04, George Dunlap wrote: > On Sat, Feb 20, 2016 at 9:24 PM, Sarah Newman <srn at prgmr.com> wrote: >> On 02/17/2016 04:30 AM, George Dunlap wrote: >>> I have the following packages going through the CBS: >>> * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 >>> * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 >>> * A CentOS 6

On Thu, Jan 21, 2016 at 3:39 PM, Johnny Hughes <johnny at centos.org> wrote: > On 01/21/2016 09:29 AM, Johnny Hughes wrote: >> This is a community SIG .. and xenproject.org does NOT release XSAs for >> 4.2. The goal of Xen4centOS was to use an upstream LTS kernel and >> update those as required to stay on an LTS. Also to do every second >> point release of xen

I've built Xen 4.6.6 with the XSAs released last week, and tagged it so that it shows up in centos-virt-testing. Please test it and let me know if you have any problems. Thanks, -George

xen-4.4.3-9 and kernel-3.18.21-17 (unsigneg) are now on buildlogs.centos.org, and signed packages should be making their way through the mirror system in the near future. Updated package sources can be found in the virt sig area on CentOS: https://github.com/CentOS-virt7/xen https://github.com/CentOS-virt7/xen-kernel The packages contain updates for XSAs 155, 157, 164, 165, and 166 (released

On 01/21/2016 09:29 AM, Johnny Hughes wrote: > This is a community SIG .. and xenproject.org does NOT release XSAs for > 4.2. The goal of Xen4centOS was to use an upstream LTS kernel and > update those as required to stay on an LTS. Also to do every second > point release of xen (ie, 4.2, 4.4, 4.6). All so we are longer term > than upstream, BUT we have supported code from

Well when the last upgrade 4.2 > 4.4 went live and XM was disabled by default it took many hosts down without warning. 4.4 > 4.6 may cause the same issues. It's a dangerous upgrade for sure. Why can't 4.4 be LTS for C6? as it's the last build with XM. Any XSA patches should not be hard to backport. and maybe the optional xen4.6 for C6. On 21 January 2016 at 13:09, President

Its my impression that as a general rule from RH once some software has been released into a major release any further release of that software does not change major version or fundamental features.. For C6 I would argue Xen 4.2 should stay packaged as xen and Xen 4.4 be packaged as xen44 ... I do not believe that Xen has been released for C7 yet so what ever package version is released

?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,

Just to let people know what's going on: The embargo for XSA-135 lifted today at 1400 UTC. The embargoes for XSAs 134 and 136 lift tomorrow at 1200 UTC. XSA-135 only affects guests which have been assigned a PCNET emulated NIC, which is not the default; as such, it doesn't seem terribly urgent to push the fix today. So rather than push one fix today and another tomorrow, our plan is

On Mon, Jun 13, 2016 at 6:39 AM, George Dunlap <dunlapg at umich.edu> wrote: > On Fri, Jun 10, 2016 at 9:11 PM, Lokesh Mandvekar > <lsm5 at fedoraproject.org> wrote: >> Moving this discussion to centos-virt@ as it's upto the SIG to decide on >> how this moves ahead. >> >> I'm hoping to have 2 new koji tag sets: >> >>

Just a reminder to everyone, we've got our bi-weekly Virt SIG meeting today. It's on a phone bridge this time; e-mail me if you want the dial-in information. Lars, will you be hosting the call, or shall I? -George