Re: [Xen-devel] Kernel panic on Xen virtualisation in Debian

[Andreas Ziegler <ml@xxxxxxxxxxxxxxxxxx>]

Hi,

few months later Ingo decided again to give it a try as he really
doesn't want to keep ipv6 disabled in 2016.
He tried Xen 4.8 - which didn't help, the crash reappeared.
He then managed to build Xen with debug=y and soon it crashed with the
following output, which looks a little bit longer than without debug:

http://paste.debian.net/895464/

If this still doesn't help, we would really appreciate more information
on how to do proper debugging, the information we found online is either
very old, confusing - or it's hidden very good?

Andreas.


-------- Original-Nachricht --------
Betreff: Re: [Xen-devel] Kernel panic on Xen virtualisation in Debian
Von: Wei Liu <wei.liu2@xxxxxxxxxx>
An: Ingo Jürgensmann <ij@xxxxxxxxxxxxxxxxxx>
Datum: 2.8.2016, 14:37:58

> On Tue, Aug 02, 2016 at 12:30:30PM +0200, Ingo Jürgensmann wrote:
>> On 02.08.2016 11:20, Wei Liu wrote:
>>> On Fri, Jul 29, 2016 at 10:17:22PM +0200, Ingo Jürgensmann wrote:
>>> What is also interesting is that you seem to be running some sort of
>>> ip accounting software (pmacctd) which also segfault'ed.
>>
>> Yeah, it is segfaulting, because the database (in a domU VM) where it is
>> storing the accounting is not yet available after the crash. When database
>> is up&running, those segfaults go away.
>>
> 
> At least we can now rule out that it is not related to the issue you
> reported.
> 
>>> Still not sure what to make of that though.
>>
>> Me neither. ;-)
>>
>> I already tried to get a core dump by setting ulimit -c unlimited, but that
>> didn't work as well, which makes me believe that the crash happens in
>> hypervisor not in dom0 kernel. When it's dom0 kernel I would expect dumping
>> a core file should work.
>>
> 
> We can't draw the conclusion that the crash is in hypervisor yet. If
> your dom0 crash, hypervisor would normally decide to reboot the machine.
> 
> Wei.
> 

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