similar to: Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

Sad to say that I already tested 4.9.20-26 from your repo yesterday...it does look a little cleaner before it dies, but still dies. I have not tested it with the vcpu=4 wokaround, but I can tonight if you would like. Relevant bits below: Loading Xen 4.6.3-12.el7 ... Loading Linux 4.9.20-26.el7.x86_64 ... Loading initial ramdisk ... [ 0.000000] Linux version 4.9.20-26.el7.x86_64 (mockbuild@)

There was a note that the non-Xen kernel at the same kernel version did indeed boot: "CentOS-6 4.9.20-26 kernel exhibits the same constant kernel-start-then-reboot issue when booting under the "CentOS Linux, with Xen hypervisor" grub2 menu option. However, it *does* properly boot under the "CentOS Linux (4.9.20-25.el7.x86_64) 7 (Core)" grub2 menu option!" Trying to

Apologies: I installed the newer -26 kernel and had not rebooted into it. The grub2 menu item should have been "CentOS Linux (4.9.20-25.el7.x86_64) 7 (Core)". I am currently restarting that remote affected system (unmodified grub2 entry first). Thanks PJ On Tue, Apr 18, 2017 at 8:39 AM, PJ Welsh <pjwelsh at gmail.com> wrote: > Just to note, the same pattern happens on C7: >

Dave, Take a look at this kernel as it is the one I think we are going to release (or a slightly newer 4.9.2x from kernel.org LTS). This version has some newer settings that are more redhat/fedora/centos base kernel like WRT what is a module and what is built into the kernel, etc. https://people.centos.org/hughesjr/4.9.x/ Thanks, Johnny Hughes On 04/14/2017 05:16 AM, Anderson, Dave wrote: >

So, strangely, I have two _identical_ dualproc xeon mobos (same bios/ipmi versions, they even share an enclosure, one is right side, other is left), each with different cpu/memory: Using 4.9.13 with vcpu limited to 4, early in the boot process, the one that _was_ booting before setting the xen vcpu args says: "[ 7.060720] smpboot: Max logical packages: 2", and the other one says

On 04/14/2017 03:26 PM, Anderson, Dave wrote: > Sad to say that I already tested 4.9.20-26 from your repo yesterday...it does look a little cleaner before it dies, but still dies. I have not tested it with the vcpu=4 wokaround, but I can tonight if you would like. Relevant bits below: > > Loading Xen 4.6.3-12.el7 ... > Loading Linux 4.9.20-26.el7.x86_64 ... > Loading initial

Just to note, the same pattern happens on C7: "CentOS Linux, with Xen hypervisor" = reboot "CentOS Linux (4.9.20-26.el7.x86_64) 7 (Core)" = boot [root at XXX ~]# uname -a Linux XXX 4.9.20-25.el7.x86_64 #1 SMP Fri Mar 31 08:53:28 CDT 2017 x86_64 x86_64 x86_64 On Tue, Apr 18, 2017 at 8:36 AM, PJ Welsh <pjwelsh at gmail.com> wrote: > There was a note that the non-Xen

Here is something interesting... I went through the BIOS options and found that one R710 that *is* functioning only differed in that "Logical Processor"/Hyperthreading was *enabled* while the one that is *not* functioning had HT *disabled*. Enabled Logical Processor and the system starts without issue! I've rebooted 3 times now without issue. Dell R710 BIOS version 6.4.0 2x Intel(R)

On 04/19/2017 12:18 PM, PJ Welsh wrote: > > On Wed, Apr 19, 2017 at 5:40 AM, Johnny Hughes <johnny at centos.org > <mailto:johnny at centos.org>> wrote: > > On 04/18/2017 12:39 PM, PJ Welsh wrote: > > Here is something interesting... I went through the BIOS options and > > found that one R710 that *is* functioning only differed in that

Good news/bad news testing the new kernel on CentOS7 with my now notoriously finicky machines: Good news: 4.9.23-26.el7 (grabbed today via yum update) isn't any worse than 4.9.13-22 was on my xen hosts (as far as I can tell so far at least) Bad news: It isn't any better than 4.9.13 was for me either, if I don't set vcpu limit in the grub/xen config, it still panics like so: [

Hummmm, seems there are still stability issues on the "4.9.2-26.el7.x86_64", recently hear many issue related to Supermicro board! :-( Peace!!! On Fri, Apr 21, 2017 at 9:40 AM, Anderson, Dave <daveanderson at wsu.edu> wrote: > Good news/bad news testing the new kernel on CentOS7 with my now > notoriously finicky machines: > > Good news: 4.9.23-26.el7 (grabbed today

On 03/16/2017 04:22 PM, Kevin Stange wrote: >> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >> server has yet had a NIC issue, with some being up almost a full month. >> It looks promising! (I'm knocking on all the wood everywhere, though.) > > I'm ready to call this conclusive. The problems I was having across the > board seemed to

On 03/27/2017 04:03 PM, Kevin Stange wrote: > On 03/25/2017 02:35 PM, Sarah Newman wrote: >> On 03/16/2017 04:22 PM, Kevin Stange wrote: >> >>>> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >>>> server has yet had a NIC issue, with some being up almost a full month. >>>> It looks promising! (I'm knocking on all the

I've not gotten any bites from my posting on the xen-devel mailing list. Here is the only one to-date: https://lists.xen.org/archives/html/xen-devel/2017-04/msg01069.html >From that email, there needs to be some hypervisor messages. Does anyone know how to produce the hypervisor messages? I've already removed the rhgb and quiet options from the boot. Thanks PJ On Thu, Apr 6, 2017 at

On 02/21/2017 05:32 PM, Kevin Stange wrote: > On 02/21/2017 11:50 AM, Johnny Hughes wrote: >> On 02/21/2017 11:47 AM, Johnny Hughes wrote: >>> >>> >>> Kevin, >>> >>> Please try the 4.9.11-22 kernel that I just released for CentOS-6 (along >>> with the newer linux-firmare packages and xfsprogs). >>> >>> If you enable

Greetings from member BVeale. I would like to recommend an addition to the VNC server Wiki page located here: http://wiki.centos.org/HowTos/VNC-Server I would recommend adding a reference to this blog post from "Code Ghar": http://codeghar.wordpress.com/2009/06/11/remote-login-with-gdm-and-vnc-on-fedora-11/ It could be a summary of the steps given in this post, or just a link to

Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> --- v2: - clarify commit

Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> --- v2: - clarify commit

On 03/24/2017 11:35 AM, PJ Welsh wrote: > As a follow up I was able to test fresh install on Dell R710 and a Dell > R620 with success on CentOS 7.3 without issue on the new kernel. My new > plan will be to just move this C6 to one of the C7 I just created. That sounds like a compiler problem, since I think the C6 and C7 kernels are built from the same source. --Sarah

Per request by toracat in: http://centos.org/modules/newbb/viewtopic.php?topic_id=13455&forum=37 comment #16, I would like to be able to add vnc alternative server setup info (vnc-lts-config and x11vnc) to http://wiki.centos.org/HowTos/VNC-Server, please. pjwelsh -------------- next part -------------- An HTML attachment was scrubbed... URL: