[dpdk-dev] Question on using SR-IOV with dpdk apps

[Patrick McGleenon]

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 at dpdk.org] On Behalf Of Anjali Kulkarni
Sent: 04 August 2014 21:26
To: Anjali Kulkarni; Richardson, Bruce; dev at 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 at 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.
>
>