Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted to run the current "testing" kernel of 4.9.16 with the exact same results.
Anyone have an idea? The 3.18.x series runs without issue of course.
Thanks
PJ
On 03/20/2017 08:35 AM, PJ Welsh wrote:
Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted to run the current "testing" kernel of 4.9.16 with the exact same results.
Anyone have an idea? The 3.18.x series runs without issue of course.
Try this kernel (the noarch kernel-doc is not done yet), but that is not a required package:
https://people.centos.org/hughesjr/4.9.16/x86_64/
Let me know if that works or not .. we can try adjusting some other config settings.
Don't worry about the centos.plus dist tag .. that will change when we subnit it via the regular process.
Thanks, Johnny Hughes
On 03/20/2017 08:35 AM, PJ Welsh wrote:
Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted to run the current "testing" kernel of 4.9.16 with the exact same results.
Anyone have an idea? The 3.18.x series runs without issue of course.
I think the APIC ID MISMATCH is an expected and ignorable error .. see:
https://patchwork.kernel.org/patch/9539933/
I applied that patch and I am building a 4.9.16-23 right now, I 'll publish it when it finishes. Maybe with the error gone we can get a better error in the console.
On 03/20/2017 11:21 AM, Johnny Hughes wrote:
On 03/20/2017 08:35 AM, PJ Welsh wrote:
Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted to run the current "testing" kernel of 4.9.16 with the exact same results.
Anyone have an idea? The 3.18.x series runs without issue of course.
I think the APIC ID MISMATCH is an expected and ignorable error .. see:
https://patchwork.kernel.org/patch/9539933/
I applied that patch and I am building a 4.9.16-23 right now, I 'll publish it when it finishes. Maybe with the error gone we can get a better error in the console.
OK, try the 4.9.16-23 packages here:
No warning, but still just reboots with no notice. Is there any other system info you need? Thanks PJ
On Mon, Mar 20, 2017 at 11:47 AM, Johnny Hughes johnny@centos.org wrote:
On 03/20/2017 11:21 AM, Johnny Hughes wrote:
On 03/20/2017 08:35 AM, PJ Welsh wrote:
Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted to run the current "testing" kernel of 4.9.16 with the exact same results.
Anyone have an idea? The 3.18.x series runs without issue of course.
I think the APIC ID MISMATCH is an expected and ignorable error .. see:
https://patchwork.kernel.org/patch/9539933/
I applied that patch and I am building a 4.9.16-23 right now, I 'll publish it when it finishes. Maybe with the error gone we can get a better error in the console.
OK, try the 4.9.16-23 packages here:
https://people.centos.org/hughesjr/4.9.16/x86_64/
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On 03/20/2017 01:20 PM, PJ Welsh wrote:
No warning, but still just reboots with no notice. Is there any other system info you need? Thanks PJ
Try the new 4.9.16-24 packages there now. (reworked the config based on a fedora kernel)
On Mon, Mar 20, 2017 at 11:47 AM, Johnny Hughes <johnny@centos.org mailto:johnny@centos.org> wrote:
On 03/20/2017 11:21 AM, Johnny Hughes wrote: > On 03/20/2017 08:35 AM, PJ Welsh wrote: >> Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel >> boot message of a few like "APIC ID MISMATCH" and the system reboots >> immediately without any other bits of info. This is on a Dell R710 with >> 64GB RAM and 2x 6-core Intel CPU's. >> As an additional test, I installed and attempted to run the current >> "testing" kernel of 4.9.16 with the exact same results. >> >> Anyone have an idea? The 3.18.x series runs without issue of course. >> > > I think the APIC ID MISMATCH is an expected and ignorable error .. see: > > https://patchwork.kernel.org/patch/9539933/ <https://patchwork.kernel.org/patch/9539933/> > > I applied that patch and I am building a 4.9.16-23 right now, I 'll > publish it when it finishes. Maybe with the error gone we can get a > better error in the console. > > OK, try the 4.9.16-23 packages here: https://people.centos.org/hughesjr/4.9.16/x86_64/ <https://people.centos.org/hughesjr/4.9.16/x86_64/>
Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. Thanks PJ
On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes johnny@centos.org wrote:
On 03/20/2017 01:20 PM, PJ Welsh wrote:
No warning, but still just reboots with no notice. Is there any other system info you need? Thanks PJ
Try the new 4.9.16-24 packages there now. (reworked the config based on a fedora kernel)
On Mon, Mar 20, 2017 at 11:47 AM, Johnny Hughes <johnny@centos.org mailto:johnny@centos.org> wrote:
On 03/20/2017 11:21 AM, Johnny Hughes wrote: > On 03/20/2017 08:35 AM, PJ Welsh wrote: >> Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel >> boot message of a few like "APIC ID MISMATCH" and the systemreboots
>> immediately without any other bits of info. This is on a Dell R710 with >> 64GB RAM and 2x 6-core Intel CPU's. >> As an additional test, I installed and attempted to run thecurrent
>> "testing" kernel of 4.9.16 with the exact same results. >> >> Anyone have an idea? The 3.18.x series runs without issue ofcourse.
>> > > I think the APIC ID MISMATCH is an expected and ignorable error .. see: > > https://patchwork.kernel.org/patch/9539933/ <https://patchwork.kernel.org/patch/9539933/> > > I applied that patch and I am building a 4.9.16-23 right now, I 'll > publish it when it finishes. Maybe with the error gone we can geta
> better error in the console. > > OK, try the 4.9.16-23 packages here: https://people.centos.org/hughesjr/4.9.16/x86_64/ <https://people.centos.org/hughesjr/4.9.16/x86_64/>
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
El Lunes 20/03/2017, PJ Welsh escribió:
Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. Thanks PJ
Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it.
On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes johnny@centos.org wrote:
On 03/20/2017 01:20 PM, PJ Welsh wrote:
No warning, but still just reboots with no notice. Is there any other system info you need? Thanks PJ
Try the new 4.9.16-24 packages there now. (reworked the config based on a fedora kernel)
On Mon, Mar 20, 2017 at 11:47 AM, Johnny Hughes <johnny@centos.org mailto:johnny@centos.org> wrote:
On 03/20/2017 11:21 AM, Johnny Hughes wrote: > On 03/20/2017 08:35 AM, PJ Welsh wrote: >> Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields >> a kernel >> boot message of a few like "APIC ID MISMATCH" and the systemreboots
>> immediately without any other bits of info. This is on a Dell R710 with >> 64GB RAM and 2x 6-core Intel CPU's. >> As an additional test, I installed and attempted to run thecurrent
>> "testing" kernel of 4.9.16 with the exact same results. >> >> Anyone have an idea? The 3.18.x series runs without issue ofcourse.
> I think the APIC ID MISMATCH is an expected and ignorable error > .. see: > https://patchwork.kernel.org/patch/9539933/ <https://patchwork.kernel.org/patch/9539933/> > I applied that patch and I am building a 4.9.16-23 right now, I > 'll publish it when it finishes. Maybe with the error gone we > can geta
> better error in the console. OK, try the 4.9.16-23 packages here: https://people.centos.org/hughesjr/4.9.16/x86_64/ <https://people.centos.org/hughesjr/4.9.16/x86_64/>
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Sure thing. I will need to wait until AM Tuesday USA time to test now. Thanks PJ
On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis ricardo@palmtx.com.ar wrote:
El Lunes 20/03/2017, PJ Welsh escribió:
Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. Thanks PJ
Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it.
On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes johnny@centos.org
wrote:
On 03/20/2017 01:20 PM, PJ Welsh wrote:
No warning, but still just reboots with no notice. Is there any other system info you need? Thanks PJ
Try the new 4.9.16-24 packages there now. (reworked the config based
on
a fedora kernel)
On Mon, Mar 20, 2017 at 11:47 AM, Johnny Hughes <johnny@centos.org mailto:johnny@centos.org> wrote:
On 03/20/2017 11:21 AM, Johnny Hughes wrote: > On 03/20/2017 08:35 AM, PJ Welsh wrote: >> Updating my CentOS 6.8 Xen server with new 4.9.13 kernelyields
>> a kernel >> boot message of a few like "APIC ID MISMATCH" and the systemreboots
>> immediately without any other bits of info. This is on a Dell R710 with >> 64GB RAM and 2x 6-core Intel CPU's. >> As an additional test, I installed and attempted to run thecurrent
>> "testing" kernel of 4.9.16 with the exact same results. >> >> Anyone have an idea? The 3.18.x series runs without issue ofcourse.
> I think the APIC ID MISMATCH is an expected and ignorable error > .. see: > https://patchwork.kernel.org/patch/9539933/ <https://patchwork.kernel.org/patch/9539933/> > I applied that patch and I am building a 4.9.16-23 right now, I > 'll publish it when it finishes. Maybe with the error gone we > can geta
> better error in the console. OK, try the 4.9.16-23 packages here: https://people.centos.org/hughesjr/4.9.16/x86_64/ <https://people.centos.org/hughesjr/4.9.16/x86_64/>
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
-- Ricardo J. Barberis Usuario Linux Nº 250625: http://counter.li.org/ Usuario LFS Nº 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis ricardo@palmtx.com.ar wrote:
El Lunes 20/03/2017, PJ Welsh escribió:
Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. Thanks PJ
Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it.
"noreboot" grub.conf option still produced nothing other than a flashing cursor on the top left. Also, neither num-lock nor caps-lock respond at this time... I seem no closer with helpful information other than, "it's broken" :( Here is the grub.conf stanza for the kernel: title CentOS (4.9.16-24.el6.centos.plus.x86_64) root (hd0,1) kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all gue st_loglvl=all noreboot module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro root=UUID=bc0727e1-882c-4fbc-a4d9-e4c f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto K EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img
Thanks PJ ...
On 03/21/2017 07:48 AM, PJ Welsh wrote:
On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis <ricardo@palmtx.com.ar mailto:ricardo@palmtx.com.ar> wrote:
El Lunes 20/03/2017, PJ Welsh escribió: > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it."noreboot" grub.conf option still produced nothing other than a flashing cursor on the top left. Also, neither num-lock nor caps-lock respond at this time... I seem no closer with helpful information other than, "it's broken" :( Here is the grub.conf stanza for the kernel: title CentOS (4.9.16-24.el6.centos.plus.x86_64) root (hd0,1) kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all gue st_loglvl=all noreboot module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro root=UUID=bc0727e1-882c-4fbc-a4d9-e4c f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto K EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img
Try removing "rhgb" and "quiet" from your boot options as well.
The last few lines are NMI watchdog: disabled CPU0 hardware events not enabled NMI watchdog: shutting down hard lockup detector on all CPUS installing Xen timer for CPU1 installing Xen timer for CPU2 installing Xen timer for CPU3 installing Xen timer for CPU4 installing Xen timer for CPU5 installing Xen timer for CPU6
Here is the screen shot: https://goo.gl/photos/yNQqaQY9bJBWQ84X8 It stops at CPU6. This is a dual socket server with 2x 6core L5639 CPUs (HT disabled). I'm surprised to see it stop at 6.
Thanks PJ
On Tue, Mar 21, 2017 at 1:39 PM, Kevin Stange kevin@steadfast.net wrote:
On 03/21/2017 07:48 AM, PJ Welsh wrote:
On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis <ricardo@palmtx.com.ar mailto:ricardo@palmtx.com.ar> wrote:
El Lunes 20/03/2017, PJ Welsh escribió: > Still just starts the kernel and wihtin 4 seconds reboots with4.9.16-24.
> Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it."noreboot" grub.conf option still produced nothing other than a flashing cursor on the top left. Also, neither num-lock nor caps-lock respond at this time... I seem no closer with helpful information other than, "it's broken" :( Here is the grub.conf stanza for the kernel: title CentOS (4.9.16-24.el6.centos.plus.x86_64) root (hd0,1) kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all gue st_loglvl=all noreboot module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro root=UUID=bc0727e1-882c-4fbc-a4d9-e4c f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto K EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img
Try removing "rhgb" and "quiet" from your boot options as well.
-- Kevin Stange Chief Technology Officer Steadfast | Managed Infrastructure, Datacenter and Cloud Services 800 S Wells, Suite 190 | Chicago, IL 60607 312.602.2689 X203 | Fax: 312.602.2688 kevin@steadfast.net | www.steadfast.net _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
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.
On Wed, Mar 22, 2017, 6:27 AM PJ Welsh pjwelsh@gmail.com wrote:
The last few lines are NMI watchdog: disabled CPU0 hardware events not enabled NMI watchdog: shutting down hard lockup detector on all CPUS installing Xen timer for CPU1 installing Xen timer for CPU2 installing Xen timer for CPU3 installing Xen timer for CPU4 installing Xen timer for CPU5 installing Xen timer for CPU6
Here is the screen shot: https://goo.gl/photos/yNQqaQY9bJBWQ84X8 It stops at CPU6. This is a dual socket server with 2x 6core L5639 CPUs (HT disabled). I'm surprised to see it stop at 6.
Thanks PJ
On Tue, Mar 21, 2017 at 1:39 PM, Kevin Stange kevin@steadfast.net wrote:
On 03/21/2017 07:48 AM, PJ Welsh wrote:
On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis <ricardo@palmtx.com.ar mailto:ricardo@palmtx.com.ar> wrote:
El Lunes 20/03/2017, PJ Welsh escribió: > Still just starts the kernel and wihtin 4 seconds reboots with4.9.16-24.
> Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it."noreboot" grub.conf option still produced nothing other than a flashing cursor on the top left. Also, neither num-lock nor caps-lock respond at this time... I seem no closer with helpful information other than, "it's broken" :( Here is the grub.conf stanza for the kernel: title CentOS (4.9.16-24.el6.centos.plus.x86_64) root (hd0,1) kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all gue st_loglvl=all noreboot module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro root=UUID=bc0727e1-882c-4fbc-a4d9-e4c f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto K EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img
Try removing "rhgb" and "quiet" from your boot options as well.
-- Kevin Stange Chief Technology Officer Steadfast | Managed Infrastructure, Datacenter and Cloud Services 800 S Wells, Suite 190 | Chicago, IL 60607 312.602.2689 X203 | Fax: 312.602.2688 kevin@steadfast.net | www.steadfast.net _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
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
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 /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman srn@prgmr.com wrote:
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 _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
I ran into this also.
back up to an older kernel. At least that was my solution till a kernel came out that would boot.
It seems that some kernel builds are not friendly to xen.
On 03/28/2017 05: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 update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman <srn@prgmr.com mailto:srn@prgmr.com> wrote:
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 _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org <mailto:CentOS-virt@centos.org> https://lists.centos.org/mailman/listinfo/centos-virt <https://lists.centos.org/mailman/listinfo/centos-virt>
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Maybe the BIOS versions are different on the two machines if they are the same models. Different disc controllers or modes set up? Different NICs or other add on cards?
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 update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman <srn@prgmr.com mailto:srn@prgmr.com> wrote:
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
On Tue, Mar 28, 2017 at 10:55 PM, PJ Welsh pjwelsh@gmail.com 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 update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
PJ,
Thanks for your testing and report. Would you mind reporting this on xen-devel? If there's actually a bug in the Linux 4.9.x on Xen boot path on your box, I don't think Johnny or I are going to be able to help you debug it. :-)
-George
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 update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman <srn@prgmr.com mailto:srn@prgmr.com> wrote:
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.
OK, I have a new CentOS-6 4.9.20-26 kernel here for testing:
https://people.centos.org/hughesjr/4.9.16/6/x86_64/
I am building the el7 one right now as well, it will be at:
https://people.centos.org/hughesjr/4.9.16/7/x86_64/
George and I found some issues with the 4.9.x config files for the xen kernel. Hopefully this one is much more stable as it has many changes from the fedora/rhel type configs now (what is built into the kernel, what is loaded as a kernel module, etc.)
Please test these kernels so we can get them released.
Thanks, Johnny Hughes
On Tue, Apr 4, 2017 at 11:13 AM, Johnny Hughes johnny@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 update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman <srn@prgmr.com mailto:srn@prgmr.com> wrote:
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 aDell
> 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.OK, I have a new CentOS-6 4.9.20-26 kernel here for testing:
https://people.centos.org/hughesjr/4.9.16/6/x86_64/
I am building the el7 one right now as well, it will be at:
https://people.centos.org/hughesjr/4.9.16/7/x86_64/
George and I found some issues with the 4.9.x config files for the xen kernel. Hopefully this one is much more stable as it has many changes from the fedora/rhel type configs now (what is built into the kernel, what is loaded as a kernel module, etc.)
Please test these kernels so we can get them released.
Thanks, Johnny Hughes
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
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!
A semi-close look at the /etc/grub2.cfg yields no discernible difference between a properly functional Dell R620 and the non-properly functioning Dell R710.
Sorry, I had been distracted with other issues and have not yet submitted information to the xen-devel group yet.
Thanks PJ
So interesting and challenging too, IT seems to Xen compatibility to Dell board BIOS related.
I have Dell R710 and R7200 with same Xen version, but the outcome is completely different, that R720 is slow in performance and reboot too.
xlord
On Apr 5, 2017 23:42, "PJ Welsh" pjwelsh@gmail.com wrote:
On Tue, Apr 4, 2017 at 11:13 AM, Johnny Hughes johnny@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 update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman <srn@prgmr.com mailto:srn@prgmr.com> wrote:
On 03/24/2017 11:35 AM, PJ Welsh wrote: > As a follow up I was able to test fresh install on Dell R710 anda 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.OK, I have a new CentOS-6 4.9.20-26 kernel here for testing:
https://people.centos.org/hughesjr/4.9.16/6/x86_64/
I am building the el7 one right now as well, it will be at:
https://people.centos.org/hughesjr/4.9.16/7/x86_64/
George and I found some issues with the 4.9.x config files for the xen kernel. Hopefully this one is much more stable as it has many changes from the fedora/rhel type configs now (what is built into the kernel, what is loaded as a kernel module, etc.)
Please test these kernels so we can get them released.
Thanks, Johnny Hughes
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
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!
A semi-close look at the /etc/grub2.cfg yields no discernible difference between a properly functional Dell R620 and the non-properly functioning Dell R710.
Sorry, I had been distracted with other issues and have not yet submitted information to the xen-devel group yet.
Thanks PJ
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On 03/28/2017 02: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 update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
I am having no similar issues with several Dell Proliant DL160p's and CentOS 6. They are either G5 or G6, I don't recall which.
--Sarah
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 11:21 PM, Sarah Newman srn@prgmr.com wrote:
On 03/28/2017 02: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 update. I hope I'm not introducing something odd. They
only
"interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused.
I am having no similar issues with several Dell Proliant DL160p's and CentOS 6. They are either G5 or G6, I don't recall which.
--Sarah
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On Fri, Apr 7, 2017 at 6:58 AM, PJ Welsh pjwelsh@gmail.com wrote:
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
I spoke too soon. To get more information: Please see https://wiki.xenproject.org/wiki/Reporting_Bugs_against_Xen_Project and https://wiki.xenproject.org/wiki/Xen_Serial_Console or alternatively at least add "vga=keep".
pjwelsh
-
Alvin Starr -
George Dunlap -
Johnny Hughes -
Kevin Stange -
Mark L Sung -
PJ Welsh -
Ricardo J. Barberis -
Sarah Newman