Hello shivaram, Darrell has already asked if VT-d is enabled? Your cmdline options are appropriate as you have iommu enabled(intel_iommu=on iommu=pt). can you also check the output of below mentioned command to see if VT-d is enabled in BIOS?
$ dmesg | grep -e DMAR -e IOMMU Regards, Bhanuprakash. From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Shivaram Mysore Sent: Tuesday, March 28, 2017 6:25 AM To: Darrell Ball <db...@vmware.com> Cc: ovs-discuss@openvswitch.org Subject: Re: [ovs-discuss] Error attaching device to DPDK # uname -r 4.10.0-14-generic # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=/dev/mapper/intelsdn--vg-root ro quiet intel_iommu=on iommu=pt default_hugepagesz=1G hugepagesz=1G hugepages=4 # uname -a Linux intelsdn 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.04 DISTRIB_CODENAME=zesty DISTRIB_DESCRIPTION="Ubuntu Zesty Zapus (development branch)" NAME="Ubuntu" VERSION="17.04 (Zesty Zapus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Zesty Zapus (development branch)" VERSION_ID="17.04" Nothing in the syslog related On Mon, Mar 27, 2017 at 10:02 PM, Darrell Ball <db...@vmware.com<mailto:db...@vmware.com>> wrote: I see the pastebins now. What kernel version are you using ? VT-d enabled ? Anything related in syslog ? From: Shivaram Mysore <shivaram.mys...@gmail.com<mailto:shivaram.mys...@gmail.com>> Date: Monday, March 27, 2017 at 9:34 PM To: Darrell Ball <db...@vmware.com<mailto:db...@vmware.com>> Cc: "ovs-discuss@openvswitch.org<mailto:ovs-discuss@openvswitch.org>" <ovs-discuss@openvswitch.org<mailto:ovs-discuss@openvswitch.org>> Subject: Re: [ovs-discuss] Error attaching device to DPDK One more datapoint, please check the paste bin log in URL sent earlier. Dpdk-devbind works and you can see results in the paste bin log /Shivaram ::Sent from my mobile device:: On Mar 27, 2017, at 8:34 PM, Darrell Ball <db...@vmware.com<mailto:db...@vmware.com>> wrote: see inline below But a few questions: 1) Are you using the recommended version of dpdk with OVS 2.7 – 16.11 ? 2) Are you getting a crash still or is this post crash ? 3) Was the previous crash still happening with 16.11 or only 17.02 ? Thanks Darrell From: <ovs-discuss-boun...@openvswitch.org<mailto:ovs-discuss-boun...@openvswitch.org>> on behalf of Shivaram Mysore <shivaram.mys...@gmail.com<mailto:shivaram.mys...@gmail.com>> Date: Monday, March 27, 2017 at 7:45 PM To: "ovs-discuss@openvswitch.org<mailto:ovs-discuss@openvswitch.org>" <ovs-discuss@openvswitch.org<mailto:ovs-discuss@openvswitch.org>> Subject: [ovs-discuss] Error attaching device to DPDK Hello, I have installed OVS 2.7 running. When I do: 1. # ovs-vsctl add-port ovs-ip64-br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk options:dpdk-devargs=0000:82:00.0 2. ovs-vsctl: Error detected while setting up 'dpdk-p0': Error attaching device '0000:82:00.0' to DPDK. See ovs-vswitchd log for details. Possibly, the port is not bound. Check using $DPDK_DIR/tools/dpdk-devbind.py –status and see the documentation for more detail and the log file shows: 1. 2017-03-28T02:04:40.004Z|00064|netdev_dpdk|WARN|Error attaching device '0000:82:00.0' to DPDK 2. 2017-03-28T02:04:40.004Z|00065|netdev|WARN|dpdk-p0: could not set configuration (Invalid argument) What would cause such a situation? Commands run: https://pastebin.com/0P754x0t<https://urldefense.proofpoint.com/v2/url?u=https-3A__pastebin.com_0P754x0t&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=spZCZ7BnBbu-PD803qcYLxegZkc9PwBLFH3QQ1XxWu0&s=uYWBSaIFlY3aKKwC7PAszDPMtB9xS3zjpwJo8afntY8&e=> Detailed OVS Log: https://pastebin.com/ctBhLuRG<https://urldefense.proofpoint.com/v2/url?u=https-3A__pastebin.com_ctBhLuRG&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=spZCZ7BnBbu-PD803qcYLxegZkc9PwBLFH3QQ1XxWu0&s=PC90IYBZb113gFPdzbbIa2gBRr3H8VIpr9ow0jhi-pk&e=>
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
