From: Wei Liu <wei.liu2@citrix.com>
To: "Ingo Jürgensmann" <ij@2013.bluespice.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
janprunk@gmail.com, george.dunlap@citrix.com,
804079@bugs.debian.org, Andreas Ziegler <ml@andreas-ziegler.de>,
david.vrabel@citrix.com, xen-devel@lists.xen.org
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Tue, 2 Aug 2016 13:37:58 +0100 [thread overview]
Message-ID: <20160802123758.GK22419@citrix.com> (raw)
In-Reply-To: <af51c39bd919f28c10d4f362279920b1@localhost>
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.
> --
> Ciao... // http://blog.windfluechter.net
> Ingo \X/ XMPP: ij@jabber.windfluechter.net
>
>
> gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-02 12:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 22:29 Kernel panic on Xen virtualisation in Debian Andreas Ziegler
2016-07-10 13:18 ` Ingo Jürgensmann
2016-07-18 16:44 ` Andreas Ziegler
2016-07-22 9:03 ` Ingo Jürgensmann
2016-07-22 10:21 ` Ingo Jürgensmann
2016-07-25 9:38 ` Ingo Jürgensmann
2016-07-25 10:23 ` Wei Liu
2016-07-25 10:42 ` Andreas Ziegler
2016-07-25 10:50 ` Andreas Ziegler
2016-07-25 10:51 ` Wei Liu
2016-07-25 11:27 ` Ingo Jürgensmann
2016-07-25 12:35 ` Sander Eikelenboom
2016-07-25 11:41 ` Ingo Jürgensmann
2016-07-25 13:13 ` Wei Liu
2016-07-29 11:45 ` Andreas Ziegler
2016-07-29 13:01 ` Wei Liu
2016-07-29 20:17 ` Ingo Jürgensmann
2016-08-02 9:20 ` Wei Liu
2016-08-02 10:30 ` Ingo Jürgensmann
2016-08-02 12:37 ` Wei Liu [this message]
2016-11-14 15:55 ` Andreas Ziegler
2016-11-29 9:08 ` Wei Liu
2016-11-29 20:20 ` Ingo Jürgensmann
2016-12-01 13:26 ` Wei Liu
2016-12-01 13:59 ` Ingo Jürgensmann
2016-12-01 14:07 ` Wei Liu
2016-12-01 14:50 ` Sander Eikelenboom
2016-07-25 10:49 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2016-07-04 18:06 Jan Prunk
2016-07-06 14:14 ` George Dunlap
2016-07-08 11:14 ` Wei Liu
2016-07-08 12:22 ` Jan Prunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160802123758.GK22419@citrix.com \
--to=wei.liu2@citrix.com \
--cc=804079@bugs.debian.org \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ij@2013.bluespice.org \
--cc=janprunk@gmail.com \
--cc=ml@andreas-ziegler.de \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).