DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick McGleenon <Patrick.McGleenon@owmobility.com>
To: Anjali Kulkarni <anjali@juniper.net>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
Date: Tue, 5 Aug 2014 14:38:48 +0000	[thread overview]
Message-ID: <78e1ff3841f6401c828eab452ea8b4f1@CO2PR0501MB870.namprd05.prod.outlook.com> (raw)
In-Reply-To: <D0053A5F.2D3C5%anjali@juniper.net>

I had this when the PF was down, bringing it back with "ifup" fixed it.   Assuming you've already checked it's not the issue described in the FAQ :)
With a RHEL 6.5 host the ixgbe driver prints the VF MAC addresses in /var/log/syslog when the VFs are enabled

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anjali Kulkarni
Sent: 04 August 2014 21:26
To: Anjali Kulkarni; Richardson, Bruce; dev@dpdk.org
Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps

The 4 devices in qs are at 04:10.0, 04:10.1, 04:10.2, 04:10.3

Anjali

On 8/4/14 1:24 PM, "Anjali Kulkarni" <anjali@juniper.net> wrote:

>It seems to have detected all 4. But I do see a MAC address not valid:
>:
>:
>(scrolled up)
>
>EAL: PCI device 0000:04:10.1 on NUMA socket 0                      │
>EAL:   probe driver: 8086:10ed rte_ixgbevf_pmd                     │
>EAL:   PCI memory mapped at 0x7fd39743e000                         │
>EAL:   PCI memory mapped at 0x7fd39743a000                         │
>PMD:    The MAC address is not valid.                              │
> The most likely cause of this error is that the VM host    │
> has not assigned a valid MAC address to this VF device.    │
> Please consult the DPDK Release Notes (FAQ section) for    │
> a possible solution to this problem.                       │
>EAL: PCI device 0000:04:10.2 on NUMA socket 0                      │
>EAL:   probe driver: 8086:10ed rte_ixgbevf_pmd                     │
>EAL:   PCI memory mapped at 0x7fd397436000                         │
>EAL:   PCI memory mapped at 0x7fd397432000                         │
>EAL: PCI device 0000:04:10.3 on NUMA socket 0                      │
>EAL:   probe driver: 8086:10ed rte_ixgbevf_pmd                     │
>EAL:   PCI memory mapped at 0x7fd39742e000                         │
>EAL:   PCI memory mapped at 0x7fd39742a000                         │
>PMD:    The MAC address is not valid.                              │
> The most likely cause of this error is that the VM host    │
> has not assigned a valid MAC address to this VF device.    │
> Please consult the DPDK Release Notes (FAQ section) for    │
> a possible solution to this problem.
>
>

  reply	other threads:[~2014-08-05 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 20:26 Anjali Kulkarni
2014-08-05 14:38 ` Patrick McGleenon [this message]
2014-08-05 15:09   ` Xie, Huawei
  -- strict thread matches above, loose matches on Subject: below --
2014-08-04 19:43 Anjali Kulkarni
2014-08-04 19:44 ` Anjali Kulkarni
2014-08-04 19:53   ` Richardson, Bruce
2014-08-04 20:24     ` Anjali Kulkarni

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=78e1ff3841f6401c828eab452ea8b4f1@CO2PR0501MB870.namprd05.prod.outlook.com \
    --to=patrick.mcgleenon@owmobility.com \
    --cc=anjali@juniper.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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).