From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0080.outbound.protection.outlook.com [65.55.169.80]) by dpdk.org (Postfix) with ESMTP id F3C595A50 for ; Fri, 29 May 2015 07:22:09 +0200 (CEST) Received: from BN3PR0301MB1202.namprd03.prod.outlook.com (10.161.207.155) by BN3PR0301MB1203.namprd03.prod.outlook.com (10.161.207.156) with Microsoft SMTP Server (TLS) id 15.1.172.22; Fri, 29 May 2015 05:22:05 +0000 Received: from BN3PR0301MB1202.namprd03.prod.outlook.com ([10.161.207.155]) by BN3PR0301MB1202.namprd03.prod.outlook.com ([10.161.207.155]) with mapi id 15.01.0172.012; Fri, 29 May 2015 05:22:05 +0000 From: "Dey, Souvik" To: "dev@dpdk.org" Thread-Topic: Unable to bind Virtio_pci in DPDK1.7 Thread-Index: AdCZzAPCwh7zFxw4RNm5B3/INRXs/Q== Date: Fri, 29 May 2015 05:22:05 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=sodey@sonusnet.com; x-originating-ip: [121.242.142.135] x-microsoft-exchange-diagnostics: 1; BN3PR0301MB1203; 3:P3ibv9ZYiw6ra+MRS3a3PycAI7QMSHjk2EB5rBHCC37CwcrSo7PsY5b7XVwmGKkuVWLW4c4uo31ciMV2/X0XoGprg1yOcwh7um0sEFAXvFcY/VD7nUqe7ok17t9LBMh1ms9sxqPhOMW0BVlyftZZdg==; 10:AR8CkoOMdVVsz87aqIg1m4kz2k5WoUJ0AX7WrBX+fKXEVfSCCVON9rklDSRi5RwrJPjIDF/R+DUVFBxNfUs1ZyeMAyqApBOeg0BZFUYo8A8=; 6:cHptUwir/zkJQQHaq20wKQEPsiGw1F2RUdYRJOs0wNmSnJRFU3sVZNPd8sVQGfbl x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR0301MB1203; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(520003)(3002001); SRVR:BN3PR0301MB1203; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0301MB1203; x-forefront-prvs: 059185FE08 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(53754006)(199003)(189002)(87936001)(2656002)(77096005)(229853001)(106356001)(97736004)(4001540100001)(81156007)(76576001)(64706001)(74316001)(92566002)(5002640100001)(102836002)(46102003)(99286002)(15975445007)(2351001)(54356999)(66066001)(50986999)(101416001)(19580395003)(2900100001)(40100003)(2501003)(450100001)(62966003)(5001860100001)(19625215002)(68736005)(105586002)(5001830100001)(33656002)(122556002)(19300405004)(16236675004)(86362001)(77156002)(110136002)(107886002)(5001960100002)(189998001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0301MB1203; H:BN3PR0301MB1202.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: sonusnet.com does not designate permitted sender hosts) MIME-Version: 1.0 X-OriginatorOrg: sonusnet.com X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2015 05:22:05.4247 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0301MB1203 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7 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: Fri, 29 May 2015 05:22:10 -0000 Hi All, I am currently facing a weird issue where I am not able to = bind the virtio_pci device to igb_uio in DPDK1.7 on QEMU/KVM. I can see the= re are two fold issues. 1.The pci_unbind.py script where the virt_path is removed from 1.6 to 1.7 v= ersion due to which the initial status is not able to show any interface na= me. Network devices using DPDK-compatible driver =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Network devices using kernel driver =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 0000:00:03.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Dvirtio= _pci,igb_uio 0000:00:04.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Dvirtio= _pci,igb_uio 0000:00:05.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Dvirtio= _pci,igb_uio 0000:00:06.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Dvirtio= _pci,igb_uio Other network devices =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 2. After correcting the above issue , I am stuck where the interface is fai= ling to bind to igb_uio. I tried to bind the interface manually to igb_uio= but I am getting the following error lspci -k 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device Subsystem: Red Hat, Inc Device 0001 Kernel modules: virtio_pci echo 0000:00:05.0 > /sys/bus/pci/drivers/igb_uio/bind -bash: echo: write error: No such device Due to this the bind fails and the virtio_pmd is not able to take and my ap= p is not coming up. EAL: PCI device 0000:00:03.0 on NUMA socket -1 EAL: probe driver: 1af4:1000 rte_virtio_pmd EAL: 0000:00:06.0 not managed by UIO driver, skipping EAL: Error - exiting with code: 1 Cause: No Ethernet ports - bye I see lots of email threads on similar issue but none had the final conclus= ion. So can someone guide me on how to proceed further or get out of this e= rror. -- Regards, Souvik