DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Deme <odeme@druidsoftware.com>
To: "Zhou, Danny" <danny.zhou@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI automatic IP configuration
Date: Thu, 16 Apr 2015 12:16:28 +0100	[thread overview]
Message-ID: <552F9A0C.7040402@druidsoftware.com> (raw)
In-Reply-To: <DFDF335405C17848924A094BC35766CF0AB460E0@SHSMSX104.ccr.corp.intel.com>

Hi, sorry to resurrect this question.
I am now using a virtio network interface in a qemu VM.
Is it possible to use ifplugd to automatically setup the IP 
configuration of a KNI based interface?
Here is the output of lspci:
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
00:06.0 Ethernet controller: Red Hat, Inc Virtio network device

Thanks for your help.
Olivier.


On 05/04/15 02:08, Zhou, Danny wrote:
> e1000 driver supports many different NIC devices.
>
> Do you know your NIC device type or device_id?
>
>> -----Original Message-----
>> From: Olivier Deme [mailto:odeme@druidsoftware.com]
>> Sent: Sunday, April 05, 2015 1:03 AM
>> To: Zhou, Danny
>> Cc: dev@dpdk.org
>> Subject: Re: [dpdk-dev] KNI automatic IP configuration
>>
>> Currently I’m using the e1000 PMD driver.
>>
>> Thanks,
>> Olivier.
>>
>>> On 4 Apr 2015, at 12:51, Zhou, Danny <danny.zhou@intel.com> wrote:
>>>
>>> Which NIC device are you using now?
>>>
>>> KNI does not provide Ethtool support for all NICs supported by the Poll-Mode Drivers.
>>>
>>>> -----Original Message-----
>>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Deme
>>>> Sent: Friday, April 03, 2015 10:03 PM
>>>> To: dev@dpdk.org
>>>> Subject: [dpdk-dev] KNI automatic IP configuration
>>>>
>>>> Hi all,
>>>>
>>>> Is it possible on Linux to get the Linux network manager to automatically configure a KNI virtual network interface as soon as it
>>>> comes up?
>>>> I haven’t been able to get Fedora to apply the configuration under /etc/sysconfig/network-scripts/ifcfg-veth0 file upon
>> starting
>>>> my DPDK application.
>>>>
>>>> Executing ifup veth0 manually works but somehow the fedora network manager seems to have an issue to apply the if cfg
>> config
>>>> automatically.
>>>> In the system logs I can see something along the lines “kni doesn’t support ethtool”. Is this related?
>>>>
>>>> I also tried ifplugd but without success.
>>>>
>>>> Many thanks for your help,
>>>>
>>>> Olivier.

-- 
	*Olivier Demé*
*Druid Software Ltd.*
*Tel: +353 1 202 1831*
*Email: odeme@druidsoftware.com <mailto:odeme@druidsoftware.com>*
*URL: http://www.druidsoftware.com*
Druid Software: Monetising enterprise small cells solutions.


Druid_Footer_Logo

      reply	other threads:[~2015-04-16 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 14:02 Olivier Deme
2015-04-04 11:51 ` Zhou, Danny
2015-04-04 17:02   ` Olivier Deme
2015-04-05  1:08     ` Zhou, Danny
2015-04-16 11:16       ` Olivier Deme [this message]

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=552F9A0C.7040402@druidsoftware.com \
    --to=odeme@druidsoftware.com \
    --cc=danny.zhou@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).