From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-00103a01.pphosted.com (mx0a-00103a01.pphosted.com [67.231.144.234]) by dpdk.org (Postfix) with ESMTP id 7B8D35A54 for ; Fri, 27 Feb 2015 15:37:10 +0100 (CET) Received: from pps.filterd (m0000419.ppops.net [127.0.0.1]) by mx0a-00103a01.pphosted.com (8.14.5/8.14.5) with SMTP id t1REZWBE017500; Fri, 27 Feb 2015 09:37:09 -0500 Received: from vawvcgsie2k1302.ciena.com (LIN1-118-36-36.ciena.com [63.118.36.36]) by mx0a-00103a01.pphosted.com with ESMTP id 1st325n1rj-2 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 27 Feb 2015 09:37:08 -0500 Received: from MDWEXCHCGSIHT01.ciena.com (10.4.140.106) by VAWVCGSIE2K1302.ciena.com (10.4.62.16) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 27 Feb 2015 09:37:02 -0500 Received: from ONWVEXCHHT01.ciena.com (10.128.6.16) by MDWEXCHCGSIHT01.ciena.com (10.4.140.106) with Microsoft SMTP Server (TLS) id 8.3.298.1; Fri, 27 Feb 2015 09:22:17 -0500 Received: from ONWVEXCHMB04.ciena.com ([::1]) by ONWVEXCHHT01.ciena.com ([::1]) with mapi; Fri, 27 Feb 2015 09:17:19 -0500 From: "Mussar, Gary" Date: Fri, 27 Feb 2015 09:17:18 -0500 Thread-Topic: [Dpdk-ovs] [dpdk-dev] problem in binding interfaces of virtio-pci on the VM Thread-Index: AdBSfIMYYBVRF5uASM2daOw9g0LaEQAGtHLg Message-ID: References: <745DB4B8861F8E4B9849C970520ABBF1496BD5CC@ORSMSX102.amr.corp.intel.com> <20150226170001.GA11632@bricha3-MOBL3> <20150227100631.GA10816@bricha3-MOBL3> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-TM-AS-Product-Ver: SMEX-10.0.0.1412-7.000.1014-21360.004 X-TM-AS-Result: No--13.359000-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68, 1.0.33, 0.0.0000 definitions=2015-02-27_05:2015-02-27,2015-02-27,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1502270154 X-Mailman-Approved-At: Fri, 27 Feb 2015 15:38:35 +0100 Cc: "dev@dpdk.org" , "dpdk-ovs@lists.01.org" Subject: Re: [dpdk-dev] [Dpdk-ovs] problem in binding interfaces of virtio-pci on the VM 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, 27 Feb 2015 14:37:11 -0000 This may be a long shot, but I have noticed that using dissimilar device ty= pes when launching the VM that these devices might not be bound to the same= eth devices in the VM. Are you sure that esn3 is the device you are expect= ing to use to talk to the host? Gary -----Original Message----- From: Dpdk-ovs [mailto:dpdk-ovs-bounces@lists.01.org] On Behalf Of Srinivas= reddy R Sent: Friday, February 27, 2015 06:00 To: Bruce Richardson Cc: dev@dpdk.org; dpdk-ovs@lists.01.org Subject: Re: [Dpdk-ovs] [dpdk-dev] problem in binding interfaces of virtio-= pci on the VM hi , please fine the oputput On the VM . /tools/dpdk_nic_bind.py --status 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 '82540EM Gigabit Ethernet Controller' if=3Dens3 drv=3De1000 un= used=3Digb_uio *Active* 0000:00:04.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Digb_ui= o 0000:00:05.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Digb_ui= o Other network devices =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D i am trying to bind "virtio network devices " with pci 00:04.0 , 00:05.0 . . when i give the below command i face the issue. ./dpdk_nic_bind.py --bind=3Digb_uio 00:04.0 00:05.0 when qemu does not able to allocate memory for vm on /dev/hugepages . it= gives the below error message . "Cannot allocate memory " In this case i am able to bind the interfaces to igb_uio . does this gives any hint on what wrong i am doing . do i need to handle any thing on the host when i bind to igb_uio on the gue= st for usvhost . ./x86_64-softmmu/qemu-system-x86_64 -cpu host -boot c -hda /home/utils/im= ages/vm1.img -m 4096M -smp 3 --enable-kvm -name 'VM1' -nographic -vnc :1 -pidfile /tmp/vm1.pid -drive file=3Dfat:rw:/tmp/qemu_sha= re,snapshot=3Doff -monitor unix:/tmp/vm1monitor,server,nowait -net none -n= o-reboot -mem-path /dev/hugepages -mem-prealloc -netdev type=3Dtap,id=3Dnet= 1,script=3Dno,downscript=3Dno,ifname=3Dusvhost1,vhost=3Don -device virtio-n= et-pci,netdev=3Dnet1,mac=3D00:16:3e:00:03:03,csum=3Doff,gso=3Doff,guest_tso= 4=3Doff,guest_tso6=3Doff,guest_ecn=3Doff -netdev type=3Dtap,id=3Dnet2,script=3Dno,downscript=3Dno,ifname=3Dusvhost2,= vhost=3Don -device virtio-net-pci,netdev=3Dnet2,mac=3D00:16:3e:00:03:04,csum=3Doff,gso=3Doff,g= uest_tso4=3Doff,guest_tso6=3Doff,guest_ecn=3Doff -net nic -net tap,ifname=3Dtap6,script=3Dno vvfat /tmp/qemu_share chs 1024,16,63 file_ram_alloc: can't mmap RAM pages: Cannot allocate memory qemu-system-x86_64: unable to start vhost net: 22: falling back on userspac= e virtio qemu-system-x86_64: unable to start vhost net: 22: falling back on userspac= e virtio thanks, srinivas. On Fri, Feb 27, 2015 at 3:36 PM, Bruce Richardson < bruce.richardson@intel.= com> wrote: > On Thu, Feb 26, 2015 at 10:46:58PM +0530, Srinivasreddy R wrote: > > hi Bruce , > > Thank you for your response . > > I am accessing my VM via " vncviewer " . so ssh doesn't come into > picture . > > Is there any way to find the root cause of my problem . does dpdk=20 > > stores any logs while binding interfaces to igb_uio. > > i have seen my /var/log/messages . but could not find any clue. > > > > the movement i gave the below command my vm got struck and not=20 > > responding untill i forcefully kill the qemu and relaunch . > > ./dpdk_nic_bind.py --bind=3Digb_uio 00:04.0 00:05.0 > > > > Does VNC not also connect using a network port? What is the output of=20 > ./dpdk_nic_bind.py --status before you run this command? > > /Bruce > > > > > > > thanks, > > srinivas. > > > > > > > > On Thu, Feb 26, 2015 at 10:30 PM, Bruce Richardson <=20 > > bruce.richardson@intel.com> wrote: > > > > > On Thu, Feb 26, 2015 at 10:08:59PM +0530, Srinivasreddy R wrote: > > > > hi Mike, > > > > Thanks for our detailed explanation of your example . usually i=20 > > > > do > > > similar > > > > to u and i am aware of working with dpdk applications . > > > > my problem is : > > > > 1. i have written a code for host to guest communication=20 > > > > .[taken > form > > > > usvhost which is developed in ovdk vswitch] . > > > > 2. i launched VM with two interfaces . > > > > 3. i am able to send and receive traffic to and from guest to=20 > > > > host on > > > these > > > > interfaces . > > > > 4. when i try to bind these interfaces to igb_uio to run dpdk > > > application > > > > . i am not able to access my instance . it got struck and not > responding > > > . > > > > i need to hard reboot the vm. > > > > > > Are you sure you are not trying to access the vm via one of the > interfaces > > > now bount to igb_uio? If you bind the interface you use for ssh to > igb_uio, > > > you won't be able to ssh to that vm any more. > > > > > > /Bruce > > > > > > > > > > > My Question is : > > > > surely i might done something wrong in code . as my VM is not=20 > > > > able to access any more when i try to bind interfaces to igb_uio =20 > > > > . not able > to > > > > debug the issue . > > > > someone please help me in figuring the issue . i dont find=20 > > > > anything > in > > > > /var/log/messages after relaunching the instance . > > > > > > > > > > > > thanks, > > > > srinivas. > > > > > > > > > > > > > > > > On Thu, Feb 26, 2015 at 8:42 PM, Polehn, Mike A < > mike.a.polehn@intel.com > > > > > > > > wrote: > > > > > > > > > In this example, the control network 00:03.0, remains unbound=20 > > > > > to > UIO > > > > > driver but remains attached > > > > > to Linux device driver (ssh access with putty) and just the=20 > > > > > target interfaces are bound. > > > > > Below, it shows all 3 interfaces bound to the uio driver,=20 > > > > > which > are not > > > > > usable until a task uses the UIO driver. > > > > > > > > > > [root@F21vm l3fwd-vf]# lspci -nn > > > > > 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX=20 > > > > > PMC > > > [Natoma] > > > > > [8086:1237] (rev 02) > > > > > 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA=20 > > > > > [Natoma/Triton II] [8086:7000] > > > > > 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3=20 > > > > > IDE [Natoma/Triton II] [8086:7010] > > > > > 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4=20 > > > > > ACPI [8086:7113] (rev 03) > > > > > 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 > > > [1013:00b8] > > > > > 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio=20 > > > > > network > device > > > > > [1af4:1000] > > > > > 00:04.0 Ethernet controller [0200]: Intel Corporation=20 > > > > > XL710/X710 > > > Virtual > > > > > Function [8086:154c] (rev 01) > > > > > 00:05.0 Ethernet controller [0200]: Intel Corporation=20 > > > > > XL710/X710 > > > Virtual > > > > > Function [8086:154c] (rev 01) > > > > > > > > > > [root@F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py > > > > > --bind=3Digb_uio 00:04.0 > > > > > [root@F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py > > > > > --bind=3Digb_uio 00:05.0 > > > > > [root@F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py > --status > > > > > > > > > > Network devices using DPDK-compatible driver=20 > > > > > =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 > > > > > 0000:00:04.0 'XL710/X710 Virtual Function' drv=3Digb_uio > unused=3Di40evf > > > > > 0000:00:05.0 'XL710/X710 Virtual Function' drv=3Digb_uio > unused=3Di40evf > > > > > > > > > > Network devices using kernel driver=20 > > > > > =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=20 > > > > > 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 > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: Dpdk-ovs [mailto:dpdk-ovs-bounces@lists.01.org] On=20 > > > > > Behalf Of Srinivasreddy R > > > > > Sent: Thursday, February 26, 2015 6:11 AM > > > > > To: dev@dpdk.org; dpdk-ovs@lists.01.org > > > > > Subject: [Dpdk-ovs] problem in binding interfaces of=20 > > > > > virtio-pci on > the > > > VM > > > > > > > > > > hi , > > > > > I have written sample program for usvhost supported by ovdk. > > > > > > > > > > i have initialized VM using the below command . > > > > > On the VM : > > > > > > > > > > I am able to see two interfaces . and working fine with=20 > > > > > traffic in rawsocket mode . > > > > > my problem is when i bind the interfaces to pmd driver[=20 > > > > > ibg_uio ] > my > > > > > virtual machine is getting hanged . and i am not able to=20 > > > > > access it > > > further > > > > > . > > > > > now my question is . what may be the reason for the behavior .=20 > > > > > and > how > > > can > > > > > in debug the root cause . > > > > > please help in finding out the problem . > > > > > > > > > > > > > > > > > > > > ./tools/dpdk_nic_bind.py --status > > > > > > > > > > Network devices using DPDK-compatible driver=20 > > > > > =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=20 > > > > > =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 '82540EM Gigabit Ethernet Controller' if=3Dens3 > drv=3De1000 > > > > > unused=3Digb_uio *Active* > > > > > 0000:00:04.0 'Virtio network device' if=3D drv=3Dvirtio-pci > unused=3Digb_uio > > > > > 0000:00:05.0 'Virtio network device' if=3D drv=3Dvirtio-pci > unused=3Digb_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 > > > > > > > > > > > > > > > > > > > > ./dpdk_nic_bind.py --bind=3Digb_uio 00:04.0 00:05.0 > > > > > > > > > > > > > > > > > > > > ./x86_64-softmmu/qemu-system-x86_64 -cpu host -boot c -hda=20 > > > > > /home/utils/images/vm1.img -m 2048M -smp 3 --enable-kvm -name > 'VM1' > > > > > -nographic -vnc :1 -pidfile /tmp/vm1.pid -drive=20 > > > > > file=3Dfat:rw:/tmp/qemu_share,snapshot=3Doff -monitor=20 > > > > > unix:/tmp/vm1monitor,server,nowait -net none -no-reboot=20 > > > > > -mem-path /dev/hugepages -mem-prealloc -netdev=20 > > > > > type=3Dtap,id=3Dnet1,script=3Dno,downscript=3Dno,ifname=3Dusvhost= 1,vhost > > > > > =3Don > > > -device > > > > > > > > > virtio-net-pci,netdev=3Dnet1,mac=3D00:16:3e:00:03:03,csum=3Doff,gso=3Doff= ,gues > t_tso4=3Doff,guest_tso6=3Doff,guest_ecn=3Doff > > > > > -netdev > > > type=3Dtap,id=3Dnet2,script=3Dno,downscript=3Dno,ifname=3Dusvhost2,vh= ost=3Don > > > > > -device > > > > > > > > > > > > > > virtio-net-pci,netdev=3Dnet2,mac=3D00:16:3e:00:03:04,csum=3Doff,gso=3Doff= ,gues > t_tso4=3Doff,guest_tso6=3Doff,guest_ecn=3Doff > > > > > > > > > > > > > > > > > > > > > > > > > ---------- > > > > > thanks > > > > > srinivas. > > > > > _______________________________________________ > > > > > Dpdk-ovs mailing list > > > > > Dpdk-ovs@lists.01.org > > > > > https://lists.01.org/mailman/listinfo/dpdk-ovs > > > > > > > > > > > > > > > > > > > > > -- > > > > thanks > > > > srinivas. > > > > > > > > > > > -- > > thanks > > srinivas. > -- thanks srinivas. _______________________________________________ Dpdk-ovs mailing list Dpdk-ovs@lists.01.org https://lists.01.org/mailman/listinfo/dpdk-ovs