All of lore.kernel.org
 help / color / mirror / Atom feed
From: David White <dwhite@speakeasy.net>
To: xen-devel@lists.xensource.com
Subject: SR-IOV problems - HVM cannot access network
Date: Tue, 01 Mar 2011 11:31:47 -0800	[thread overview]
Message-ID: <4D6D49A3.90902@speakeasy.net> (raw)

Hi all,

I am having problems getting SR-IOV functions to work in my HVMs.  My 
hardware has VT-d support, and pci passthrough works fine for physical 
functions.  In a nutshell here is the current state:

Dom0 :  NICs are 2-port 82576.  I can get full network access using 
either PF or VF interfaces.
HVM : PCI passthrough of physical functions work -- full network access
HVM : PCI passthrough of virtual functions fail -- can send pkts but 
cannot receive.

The best lead I have right now is evident from the qemu logs.

when PF (04:00.0) is assigned to HVM:

pt_msix_init: get MSI-X table bar base fafbc000
pt_msix_init: table_off = 0, total_entries = 10
pt_msix_init: errno = 2
pt_msix_init: mapping physical MSI-X table to 7f23a03d5000
pt_msi_setup: msi mapped with pirq 37
pci_intx: intx=1
register_real_device: Real physical device 04:00.0 registered successfuly!
IRQ type = MSI-INTx

when VF (04:10.2) is assigned to HVM:

pt_msix_init: get MSI-X table bar base fae24000
pt_msix_init: table_off = 0, total_entries = 3
pt_msix_init: errno = 2
pt_msix_init: mapping physical MSI-X table to 7fc918846000
register_real_device: Real physical device 04:10.2 registered successfuly!
IRQ type = INTx

VFs don't seem to be using MSI/MSI-X interupts.  Does this indicate a 
problem?

Can anyone give some insight on this?
thanks  - david

             reply	other threads:[~2011-03-01 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 19:31 David White [this message]
2011-03-01 20:50 ` SR-IOV problems - HVM cannot access network Rose, Gregory V
2011-03-01 22:04   ` David White
2011-03-01 22:41     ` Rose, Gregory V
2011-03-02  2:41       ` David White
2011-03-02 11:06         ` Stefano Stabellini
2011-03-02 20:55           ` David white
2011-03-02 21:58             ` Stefano Stabellini

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=4D6D49A3.90902@speakeasy.net \
    --to=dwhite@speakeasy.net \
    --cc=xen-devel@lists.xensource.com \
    /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.