similar to: Xen 4.6.6-7 packages in virt-testing

Xen 4.6.6-8 has been tagged in virt-testing. It contains XSAs 248-251, as well as an additional fix to XSA 240. Please test it if you get a chance and report any bugs; I'll probably push it to mirrors tomorrow if I don't hear anything. Peace, -George

Thanks George. As there are now quite many options to choose from, what would be the best option performance wise for running 32bit domUs under xen-4.6? Best, Peter On Wed, Jan 17, 2018 at 7:14 PM, George Dunlap <dunlapg at umich.edu> wrote: > I've built & tagged packages for CentOS 6 and 7 4.6.6-9, with XPTI > "stage 1" Meltdown mitigation. > > This will

George, This version of xen updates and allows both a CentOS 6 and CentOS 7 DomU to start and run in both HVM and PVHVM modes. So it 'works for me'. Thanks, Johnny Hughes On 12/12/2017 08:34 AM, George Dunlap wrote: > Xen 4.6.6-8 has been tagged in virt-testing. It contains XSAs > 248-251, as well as an additional fix to XSA 240. Please test it if > you get a chance and

I've built & tagged packages for CentOS 6 and 7 4.6.6-9, with XPTI "stage 1" Meltdown mitigation. This will allow 64-bit PV guests to run safely (with a few caveats), but incurs a fairly significant slowdown for 64-bit PV guests on Intel boxes (including domain 0). If you prefer using Vixen / Comet, you can turn it off by adding 'xpti=0' to your Xen command-line.

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

Just a heads up that I'm seeing major stability problems on these builds. Didn't have console capture setup unfortunately, but have seen my test hypervisor hard lock twice over the weekend. This is with xpti being used, rather than the shim. Cheers, Nathan > -----Original Message----- > From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of > George Dunlap

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

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

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

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

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

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

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

On 11/28/2017 10:11 AM, Johnny Hughes wrote: > Kevin has been rolling back the security updates to the 4.4 branch. He > has been working with some of the other distros (debian for sure, and > some others on the xen security list). > > I think it is his intention to continue this for as long as he is able > to. (Kevin, chime in if you have a schedule lifetime or EOL in mind)

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: >> >>

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

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

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

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

Xen 4.6.3-15 packages for CentOS 6 and CentOS 7 are on their way through the build system. They should show up in centos-virt-testing in a few hours, and in the main mirrors tomorrow morning (God willing). These contain several critical updates; users are encouraged to update as soon as possible. XSA 220 unfortunately had several dependencies on changes included in 4.6.4 and 4.6.5. This