CentOS virt - Mar 2017 - Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

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 at 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 at
centos.org
> > > <mailto:johnny at 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/>
> >
> > _______________________________________________
> > CentOS-virt mailing list
> > CentOS-virt at 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

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 at
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 at
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
at centos.org
> > > > <mailto:johnny at 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/>
> > >
> > > _______________________________________________
> > > CentOS-virt mailing list
> > > CentOS-virt at 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 at centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20170320/6d3e3951/attachment-0002.html>

On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis <ricardo at
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
...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20170321/029f92a0/attachment-0002.html>

On 03/21/2017 07:48 AM, PJ Welsh wrote:
> On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis
> <ricardo at palmtx.com.ar <mailto:ricardo at 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.

-- 
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 at steadfast.net | www.steadfast.net