From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id CC3222E8A for ; Tue, 5 Aug 2014 17:07:28 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 05 Aug 2014 08:02:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,805,1400050800"; d="scan'208";a="572020439" Received: from fmsmsx104.amr.corp.intel.com ([10.19.9.35]) by fmsmga001.fm.intel.com with ESMTP; 05 Aug 2014 08:09:16 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by FMSMSX104.amr.corp.intel.com (10.19.9.35) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 5 Aug 2014 08:09:15 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.252]) by shsmsx102.ccr.corp.intel.com ([169.254.2.172]) with mapi id 14.03.0195.001; Tue, 5 Aug 2014 23:09:14 +0800 From: "Xie, Huawei" To: Patrick McGleenon , Anjali Kulkarni , "Richardson, Bruce" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Question on using SR-IOV with dpdk apps Thread-Index: AQHPsCJeUSjpLEQ42U+wY3VofjJpepvCE+iQgAAJ0bA= Date: Tue, 5 Aug 2014 15:09:13 +0000 Message-ID: References: <78e1ff3841f6401c828eab452ea8b4f1@CO2PR0501MB870.namprd05.prod.outlook.com> In-Reply-To: <78e1ff3841f6401c828eab452ea8b4f1@CO2PR0501MB870.namprd05.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2014 15:07:29 -0000 Since some version of ixgbe driver, it will not generate mac address for th= e VFs. You could use ip link set to set mac address for the VFs. > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Patrick McGleenon > Sent: Tuesday, August 05, 2014 10:39 PM > To: Anjali Kulkarni; Richardson, Bruce; dev@dpdk.org > Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps >=20 > 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 >=20 > -----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 >=20 > The 4 devices in qs are at 04:10.0, 04:10.1, 04:10.2, 04:10.3 >=20 > Anjali >=20 > On 8/4/14 1:24 PM, "Anjali Kulkarni" wrote: >=20 > >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 =81 > >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd =81 > >EAL: PCI memory mapped at 0x7fd39743e000 =81 > >EAL: PCI memory mapped at 0x7fd39743a000 =81 > >PMD: The MAC address is not valid. =81 > > The most likely cause of this error is that the VM host =81 > > has not assigned a valid MAC address to this VF device. =81 > > Please consult the DPDK Release Notes (FAQ section) for =81 > > a possible solution to this problem. =81 > >EAL: PCI device 0000:04:10.2 on NUMA socket 0 =81 > >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd =81 > >EAL: PCI memory mapped at 0x7fd397436000 =81 > >EAL: PCI memory mapped at 0x7fd397432000 =81 > >EAL: PCI device 0000:04:10.3 on NUMA socket 0 =81 > >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd =81 > >EAL: PCI memory mapped at 0x7fd39742e000 =81 > >EAL: PCI memory mapped at 0x7fd39742a000 =81 > >PMD: The MAC address is not valid. =81 > > The most likely cause of this error is that the VM host =81 > > has not assigned a valid MAC address to this VF device. =81 > > Please consult the DPDK Release Notes (FAQ section) for =81 > > a possible solution to this problem. > > > >