Re: [Xen-devel] Immediate reboot on Xen kernel 4.9.13 ->4.9.20 load, but non-Xen is OK

[PJ Welsh <pjwelsh@xxxxxxxxx>]

On Fri, Apr 7, 2017 at 4:11 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:

>>> On 06.04.17 at 19:12, <pjwelsh@xxxxxxxxx> wrote:
> I started off my attempt to figure out what's going on with the centos-virt
> group as that is the Xen entry point I use for server. It was recommended
> to me to put my issue here. This is the beginging of the thread:
> https://lists.centos.org/pipermail/centos-virt/2017-March/005411.html
> George suggested I seek help from xen-devel:
> https://lists.centos.org/pipermail/centos-virt/2017-March/005442.html
>
> Summary:
> Within about 2 seconds of starting the servers with the Xen enabled kernel,
> the server will reboot:
> 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.

It may indeed be unexpected, but without seeing hypervisor
messages we won't know enough details about your issue.

Jan

Thank you for the reply! 

These messages shown are the only ones I get. I removed the rhgb and quiet boot options to show the messages I did get. Is there a way to show more of what you want?

Thanks

pjwelsh

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel