From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jonas Meurer <jonas@freesources.org>
Cc: xen-devel@lists.xen.org
Subject: Re: [BUG] PCI passtrough causes driver crash in DomU (Xen 4.3, Linux kernel 3.12)
Date: Fri, 7 Mar 2014 12:03:05 +0000 [thread overview]
Message-ID: <5319B579.6090206@citrix.com> (raw)
In-Reply-To: <5319B37A.9010602@freesources.org>
On 07/03/14 11:54, Jonas Meurer wrote:
> Hello,
>
> as already written to xen-users a few days ago, I've troubles using pci
> passthrough for an Intel 82574L ethernet device (kernel module e1000e).
> The device is passed through by xen-pciback, and can be seen by 'lspci'
> inside the DomU. Still, the corresponding network interface doesn't
> appear in /proc/net/dev and even more striking, the DomU kernel driver
> crashes with a traceback.
>
> All this happens on a Debian/Jessie Dom0 with Xen 4.3 and Linux kernel
> 3.12. The DomU in question has a similar Debian/Jessie setup.
>
> I searched the archives for similar issues and found the following
> thread from October 2013 that describes a similar issue starting with
> Linux kernel 3.8:
> http://thread.gmane.org/gmane.comp.emulators.xen.user/80672
>
> Below in my original post to xen-users you find details about the kernel
> drvier crash and relevant logs.
>
> I'll gladly provide more details if you give me advice on how to further
> debug this issue :)
>
> Kind regards,
> jonas
Do you have the Xen dmesg (xl/xm dmesg) from an affected run?
~Andrew
next prev parent reply other threads:[~2014-03-07 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ae3db63354065feba956b28e900cc44@imap.steindlberger.de>
2014-03-07 11:54 ` [BUG] PCI passtrough causes driver crash in DomU (Xen 4.3, Linux kernel 3.12) Jonas Meurer
2014-03-07 12:03 ` Andrew Cooper [this message]
2014-03-07 12:04 ` Jonas Meurer
2014-03-08 20:32 ` [Xen-users] " Jonas Meurer
2014-03-07 12:49 Konrad Rzeszutek Wilk
2014-03-16 15:52 ` Jonas Meurer
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=5319B579.6090206@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jonas@freesources.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.