From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by dpdk.org (Postfix) with ESMTP id F2D6F5932 for ; Wed, 20 Aug 2014 09:56:33 +0200 (CEST) Received: by mail-oi0-f52.google.com with SMTP id h136so5404750oig.39 for ; Wed, 20 Aug 2014 01:00:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Hp/ZU08pbFZsxtOoAq9VVFxEDHn41l5q/54+nESjyAw=; b=Efti7dN+0+do4+bT/9OuzJs7emX9WdLKhvddExd3bqyJeVDRX5D0EDNl9NKBGxgv9I n8d7AlLFUwL/PYzVIzNCDM6l9ZbAzmGCE8YByrVZ/c8y1JLsGDNDUFQwCdc/hNsdLQVg KMpl14ERXQDJyhHzvtV+a3r2WDtOmu1hUA3YU57nCyt5h40Qwn2L5IhOY6Y+rJ5YEHGw 3xEDLfZDfIFzYKk3XYlMGeyJHIbJl7Gm4CB70SXsuv/Avzf/PjHTN/GkTdxXOXJgAvz1 bzNd0+H/dO+Escz8pMdYgA1SpGAKhZGcGbfBgNJMUPqRJq2NujfLwdsO8EUvjd0YalO+ MFSA== X-Gm-Message-State: ALoCoQkQTWr4j1iHn402LwbdFHvo0seu35OrEufWPpUMKyaRyiXc2SMxEGaXp5dAUVcq5TY2GIpI MIME-Version: 1.0 X-Received: by 10.182.246.39 with SMTP id xt7mr48159057obc.63.1408521604215; Wed, 20 Aug 2014 01:00:04 -0700 (PDT) Received: by 10.202.55.134 with HTTP; Wed, 20 Aug 2014 01:00:04 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 11:00:04 +0300 Message-ID: From: Alex Markuze To: Jay Rolette Content-Type: text/plain; charset=UTF-8 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] VMware Fusion + DPDK and KNI 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: Wed, 20 Aug 2014 07:56:34 -0000 I'm pretty sure I will stumble on this issue in the near feature. Thanks for the heads up. On Mon, Aug 18, 2014 at 9:16 PM, Jay Rolette wrote: > Thought I'd put this out there in case anyone else runs into it. > > Using DPDK 1.6 on Ubuntu 14.04 LTS in a hardware appliance. Also using KNI > to share the data ports with an app that needs a normal TCP/IP stack > interface. > > We had everything working reasonably well on the hardware, but most of our > developers run their code in a VM on their laptops: OS X (Mavericks) + > VMware Fusion 6 Pro. > > On some VMs, we were getting errors trying to configure KNI ports: > > $ sudo ifconfig ffEth0 10.111.2.100 netmask 255.255.0.0 up > SIOCSIFFLAGS: Timer expired > SIOCSIFFLAGS: Timer expired > > Skipping the "fun" involved with trying to track down the problem, here's > what ended up fixing it. > > We had 4 network ports on the VM: > > - eth0 - Management port > - eth1 - "other" function not related to the problem > - eth2 & eth3 - inline datapath (bump-in-the-wire), but also KNI mapped > to ffEth0 & ffEth1 by our DPDK app > > If eth2 and eth3 are on the same vmnet, you'll get the "SIOCSIFFLAGS: Timer > expired" errors. Depending on what parameters you try to set, ifconfig may > think some of them have taken effect (they haven't) or it won't (setting > the MTU, etc.). > > If you put eth2 and eth3 on separate vmnets, then no issues and you can > configure the KNI ports via ifconfig as expected. > > No idea why having the ports on the same vmnet matters, since our app > doesn't care, but I haven't gone spelunking through the KNI source to find > the root cause. > > Doubtful this will matter to many (any?), but maybe it'll save someone some > time. > > Jay Rolette > *infinite io*