From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yh0-f50.google.com (mail-yh0-f50.google.com [209.85.213.50]) by dpdk.org (Postfix) with ESMTP id 7DFE858DE for ; Mon, 18 Aug 2014 20:13:01 +0200 (CEST) Received: by mail-yh0-f50.google.com with SMTP id v1so4867200yhn.9 for ; Mon, 18 Aug 2014 11:16:24 -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:date:message-id:subject:from:to :content-type; bh=/SqXCzPnozR8L3vf2YY/6nU2kTO8tlrtNdTE32a+W70=; b=U/KeiLHXRNtW2OKOf3gTz4NRWCvwCQWDLmlCuMw73xqgylqPGgMA9sva0c7PxOngta 4zORPTIt0mX12zVz8JoCcxAHf/48+ammmgrbb/izhMptZDEegRgLeg4deKINQcybHy60 EmSmiysmmXneJE5KQ+ZZjkOcYKj0usFRL7XhaOUltGuTvMOd2fu26lCzY9sl/x4Pkkwd TVTJwR4RSsDZL/vU+or0wVDwtfGwKpMEVo6bd8pXLyY5Qpi40nxeK45RnQM+BUDzKW9n bORjtivwIZggutEdF15LpHwi3z01mZNt6H4wCxNC0Pu85jJBZNFWLA59/akrh6xWq4+B 3EBQ== X-Gm-Message-State: ALoCoQnQb9zuvROMju9qeL8BkrZrTt1affcuKRPWoGTVc2lkbG1RPyqJF6d/jn35TwSZ5gjCiR6Y MIME-Version: 1.0 X-Received: by 10.236.114.131 with SMTP id c3mr33089160yhh.56.1408385784277; Mon, 18 Aug 2014 11:16:24 -0700 (PDT) Received: by 10.170.96.213 with HTTP; Mon, 18 Aug 2014 11:16:24 -0700 (PDT) Date: Mon, 18 Aug 2014 13:16:24 -0500 Message-ID: From: Jay Rolette To: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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: Mon, 18 Aug 2014 18:13:01 -0000 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*