From: Peter Xu <peterx@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: Jintack Lim <jintack@cs.columbia.edu>,
QEMU Devel Mailing List <qemu-devel@nongnu.org>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] iommu emulation
Date: Fri, 3 Mar 2017 11:43:04 +0800 [thread overview]
Message-ID: <20170303034303.GA20768@pxdev.xzpeter.org> (raw)
In-Reply-To: <jpgefyfs4m4.fsf@linux.bootlegged.copy>
On Thu, Mar 02, 2017 at 05:20:19PM -0500, Bandan Das wrote:
> Jintack Lim <jintack@cs.columbia.edu> writes:
>
> > [cc Bandan]
> >
> > On Tue, Feb 21, 2017 at 5:33 AM, Jintack Lim <jintack@cs.columbia.edu>
> > wrote:
> >
> >>
> >>
> >> On Wed, Feb 15, 2017 at 9:47 PM, Alex Williamson <
> >> alex.williamson@redhat.com> wrote:
> ...
> >>
> >
> > I've tried another network device on a different machine. It has "Intel
> > Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection" ethernet
> > controller. I got the same problem of getting the network device
> > initialization failure in L2. I think I'm missing something since I heard
> > from Bandan that he had no problem to assign a device to L2 with ixgbe.
> >
> > This is the error message from dmesg in L2.
> >
> > [ 3.692871] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> > version 4.2.1-k
> > [ 3.697716] ixgbe: Copyright (c) 1999-2015 Intel Corporation.
> > [ 3.964875] ixgbe 0000:00:02.0: HW Init failed: -12
> > [ 3.972362] ixgbe: probe of 0000:00:02.0 failed with error -12
> >
> > I checked that L2 indeed had that device.
> > root@guest0:~# lspci
> > 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM
> > Controller
> > 00:01.0 VGA compatible controller: Device 1234:1111 (rev 02)
> > 00:02.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+
> > Network Connection (rev 01)
>
> Jintack, any progress with this ?
>
> I am testing on a X540-AT2 and I see a different behavior. It appears
> config succeeds but the driver keeps resetting the device due to a Tx
> hang:
>
> [ 568.612391 ] ixgbe 0000:00:03.0 enp0s3: tx hang 38 detected on queue 0,
> resetting adapter
> [ 568.612393 ] ixgbe 0000:00:03.0 enp0s3: initiating reset due to tx
> timeout
> [ 568.612397 ] ixgbe 0000:00:03.0 enp0s3: Reset adapter
>
> This may be device specific but I think the actual behavior you see is
> also dependent on the ixgbe driver in the guest. Are you on a recent
> kernel ? Also, can you point me to the hack (by Peter) that you have
> mentioned above ?
Hi, Bandan,
Are you using the vtd vfio v7 series or another branch?
If it's the upstream one... just a note that we need to make sure
"-device intel-iommu" be the first device specified in QEMU command
line parameters (need to before "-device vfio-pci,..."). Thanks,
-- peterx
next prev parent reply other threads:[~2017-03-03 3:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHyh4xiVKjd+D=qaizUZ02O8xLYhpoVKOqC9cR0ZWWyLq9HtbQ@mail.gmail.com>
[not found] ` <20170208031216.GA5151@pxdev.xzpeter.org>
[not found] ` <CAHyh4xg7NVPjXu3c+xGWNzQqwLgFqFJTPo4SgN-X+FNuHjGihQ@mail.gmail.com>
[not found] ` <CAHyh4xhOPmfLoU_fvtbBF1Wqbzji9q6rp_bRN38qfnwvhQq+9A@mail.gmail.com>
2017-02-09 3:52 ` [Qemu-devel] iommu emulation Peter Xu
2017-02-09 13:01 ` Jintack Lim
2017-02-14 7:35 ` Peter Xu
2017-02-14 12:50 ` Jintack Lim
2017-02-15 2:52 ` Peter Xu
2017-02-15 3:34 ` Peter Xu
2017-02-15 18:15 ` Alex Williamson
2017-02-16 2:28 ` Peter Xu
2017-02-16 2:47 ` Alex Williamson
2017-02-21 10:33 ` Jintack Lim
2017-02-23 23:04 ` Jintack Lim
2017-03-02 22:20 ` Bandan Das
2017-03-02 23:36 ` Jintack Lim
2017-03-03 3:43 ` Peter Xu [this message]
2017-03-03 7:45 ` Bandan Das
2017-02-15 22:05 ` Jintack Lim
2017-02-15 22:50 ` Alex Williamson
2017-02-15 23:25 ` Jintack Lim
2017-02-16 1:17 ` Alex Williamson
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=20170303034303.GA20768@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bsd@redhat.com \
--cc=jintack@cs.columbia.edu \
--cc=qemu-devel@nongnu.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).