From: Sander Eikelenboom <linux@eikelenboom.it>
To: "Ingo Jürgensmann" <ij@2013.bluespice.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
george.dunlap@citrix.com, xen-devel@lists.xen.org,
804079@bugs.debian.org, Andreas Ziegler <ml@andreas-ziegler.de>,
david.vrabel@citrix.com, janprunk@gmail.com
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Thu, 1 Dec 2016 15:50:44 +0100 [thread overview]
Message-ID: <191211662.20161201155044@eikelenboom.it> (raw)
In-Reply-To: <e8242fd1febcaf6e5fbe3dfd5c480a1a@2013.bluespice.org>
Thursday, December 1, 2016, 2:59:36 PM, you wrote:
> On 01.12.2016 14:26, Wei Liu wrote:
>> This is still the same kernel log that was sent some time ago.
>> So, if you have built Xen with debug=y, could you try to set Xen log
>> level to the highest and capture "xl dmesg" when guest crashes?
> It's not the guest that crashes, it's dom0. So when the host crashes,
> I'm not able to issue any commands anymore.
>> But I think this is increasingly likely to be a Linux kernel issue
>> because you've tried multiple versions of xen. Maybe it is time to try
>> different versions of Dom0 kernels (sorry if you've tried that, I can't
>> remember all the details over so many moons).
> Yes, indeed I have tried different kernels, but I can't remember details
> as well... ;/
Hi Ingo,
Have you tried without enabling "ndisc" (QoS) and "ipv6" ?
They are both present in your log and i assume you are using a bridged network config ?
You wouldn't be the first to stumble over a more generic kernel network bug
while using Xen, due to less well tested combinations.
So it's worth testing if plain ipv4 and no QoS works.
--
Sander
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-01 14:50 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
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 [this message]
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=191211662.20161201155044@eikelenboom.it \
--to=linux@eikelenboom.it \
--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=wei.liu2@citrix.com \
--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).