similar to: Xen4CentOS kernel-debuginfo

By default, /var/lib/xenstored is mounted tmpfs in centos 5 but this doesn't appear to be true for Xen4CentOS. This can cause performance issues as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=446089 I'm not sure if this should be part of xencommons, but if not, adding a tmpfs mount should probably be documented on the quick start wiki page. Thanks, Sarah

On 03/10/2016 12:05 AM, Sarah Newman wrote: > On 03/09/2016 08:15 PM, Sarah Newman wrote: >> I've been running 3.18.25-18.el6.x86_64 + our build of xen 4.4.3-9 on one host for the last couple of weeks and have gotten several soft lockups >> within the last 24 hours. I am posting here first in case anyone else has experienced the same issue. >> > > Here is mpstat

It looks like no XSA-142 patch, which is "libxl fails to honour readonly flag on disks with qemu-xen" has been applied to Xen4CentOS. I assume this was on purpose? If not, I can have someone try adding the original patch from http://xenbits.xen.org/xsa/advisory-142.html and some variant of the commit from ef6cb76026628e26e3d1ae53c50ccde1c3c78b1b

Is there any problem moving to 4.9.31? This contains upstream commits f2e767bb5d6ee0d9 for mpt3sas and 69861e0a52f87333 for dom0 memory mappings. I am also trying to build a debuginfo package but it's not correct. Specifically I'm able to get vmlinux but the .debug files for modules are stripped, which isn't right. Does anyone know how to fix this? I'm also not sure how

The mystery gets more interesting... I now have a CentOS 7.3 Dell R710 server doing the exact same thing of rebooting immediately after the Xen kernel load. Just to note this is a second system and not just the first system with an update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following

Hi, We were hoping to attend an IRC meeting this morning but it looks like that didn't happen. Has this been moved to once a month or was this a special week? Thanks, Sarah

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 06/12/2017 05:17 PM, Sarah Newman wrote: > Is there any problem moving to 4.9.31? This contains upstream commits f2e767bb5d6ee0d9 for mpt3sas and > 69861e0a52f87333 for dom0 memory mappings. 4.9.31-27 is tagged for testing presently along with updated firmware. I have it running on one hypervisor on Xen-44 and it has been stable for 3 days so far. We could probably use some more testing

On Mon, Oct 23, 2017 at 12:57 PM, Karl Johnson <karljohnson.it at gmail.com> wrote: > On Sat, May 20, 2017 at 8:30 PM, Sarah Newman <srn at prgmr.com> wrote: > >> I experienced a bug that is likely the same as >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373 . Commit >> b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it,

On 3/7/19 10:30 AM, Akemi Yagi wrote: > On Thu, Mar 7, 2019 at 9:42 AM George Dunlap <dunlapg at umich.edu> wrote: >> >> Hey all, >> >> We've been on 4.9 for some time now, and while it's still supported, I >> think it's time to start thinking about upgrading, and I'd like input >> from the community about which version to move up to.

On 01/04/2018 10:49 AM, Akemi Yagi wrote: > On Thu, Jan 4, 2018 at 9:51 AM, <rikske at deds.nl> wrote: > >> Please patch the CentOS-virt Kernel to fix the >> Kernel Side-Channel Attacks vulnerabilities. >> >> The latest CentOS-virt kernel was released in November, as seen below. >> >> kernel-4.9.63-29.el7.x86_64.rpm 2017-11-21 13:30 >>

I've been running 3.18.25-18.el6.x86_64 + our build of xen 4.4.3-9 on one host for the last couple of weeks and have gotten several soft lockups within the last 24 hours. I am posting here first in case anyone else has experienced the same issue. Here is the first instance: sched: RT throttling activated NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] Modules linked in:

On Sun, Apr 2, 2017 at 9:22 PM, Sarah Newman <srn at prgmr.com> wrote: > On 04/02/2017 02:49 AM, Chris Elliott wrote: >> Hi all >> >> I?ve got a few Intel Z87 chipset machines with Adaptec 5405 raid cards (latest firmware), they work fine on 3.18 but during Dom0 boot using kernel >> 4.9.13 it hangs at ?Using clocksource tsc? and the aacraid driver keeps trying to

On Tue, Apr 4, 2017 at 11:13 AM, Johnny Hughes <johnny at centos.org> wrote: > On 03/28/2017 04:55 PM, PJ Welsh wrote: > > The mystery gets more interesting... I now have a CentOS 7.3 Dell R710 > > server doing the exact same thing of rebooting immediately after the Xen > > kernel load. Just to note this is a second system and not just the first > > system with an

On Thu, Jan 21, 2016 at 12:01 PM, Peter <peter at 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

On 08/23/2016 01:10 PM, Sarah Newman wrote: > On 08/23/2016 12:59 PM, Craig Thompson wrote: > >> I was thinking that in iterations past, it was possible just to run the hypervisor, put a symlink in /etc/xen/auto, and VMs would be auto-started upon reboot. Maybe I'm wrong, and maybe those older boxes had libvirt installed on them, too. >> > > We haven't had issues

On Sun, Mar 15, 2015 at 8:26 PM, Sarah Newman <srn at prgmr.com> wrote: > On 03/15/2015 03:25 PM, Nico Kadel-Garcia wrote: >> So I'm right back to my effectively unanswered original questions. So >> please: I asked a very specific pair of questions, and they remain >> unanswered. CentOS 5 Xen server (hypervisor, or Dom0, whatever we want >> to call it this

Not sure about CentOS 6, but this was covered previously (at least for 7...not sure how much they differ)...not that I can find the message now, but here's what I recall/pieced together from bash history that works on CentOS 7: If the microcode you want is in the microcode_ctl package: mkdir -p /etc/microcode_ctl/ucode_with_caveats/ touch /etc/microcode_ctl/ucode_with_caveats/force yum

I experienced a bug that is likely the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373 . Commit b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, doesn't appear in this kernel and doesn't apply cleanly either. Is there any point in trying to backport the patch? The backtrace is as follows: [ 32.304666] ------------[ cut here ]------------ [