From: Jonas Meurer <jonas@freesources.org>
To: xen-devel@lists.xen.org
Cc: xen-users@lists.xen.org
Subject: Re: [BUG] PCI passtrough causes driver crash in DomU (Xen 4.3, Linux kernel 3.12)
Date: Sun, 16 Mar 2014 16:52:53 +0100 [thread overview]
Message-ID: <5325C8D5.8080002@freesources.org> (raw)
In-Reply-To: <201403071249.s27CnmZg007972@aserz7021.oracle.com>
Hello again,
Am 07.03.2014 13:49, schrieb Konrad Rzeszutek Wilk:
>> Am 07.03.2014 12:54, schrieb Jonas Meurer:
>>> 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.
>
> This was fixed in 3.14 I believe by me. Is it possible for you to use that version?
today I finally managed to give linux kernel 3.14-rc5 a try. I was happy
to discover that the bug in question has been fixed in that kernel release.
In other words: with kernel 3.14-rc5 in DomU, the pci passthrough
feature works again even without the 'pci=nomsi' workaround.
Thanks a lot.
Kind regards,
jonas
next prev parent reply other threads:[~2014-03-16 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 12:49 [BUG] PCI passtrough causes driver crash in DomU (Xen 4.3, Linux kernel 3.12) Konrad Rzeszutek Wilk
2014-03-16 15:52 ` Jonas Meurer [this message]
[not found] <4ae3db63354065feba956b28e900cc44@imap.steindlberger.de>
2014-03-07 11:54 ` Jonas Meurer
2014-03-07 12:03 ` Andrew Cooper
2014-03-07 12:04 ` 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=5325C8D5.8080002@freesources.org \
--to=jonas@freesources.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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).