[Starlingx-discuss] Deployment Option (error: compute boot in loop)

Peters, Matt Matt.Peters at windriver.com
Thu Jan 24 15:01:07 UTC 2019 

Sorry, can you do the command again with the -i

dmesg  | grep -i -e DMAR -e IOMMU

From: Himanshu Goyal <himanshugoyal500 at gmail.com>
Date: Thursday, January 24, 2019 at 9:10 AM
To: "Peters, Matt" <Matt.Peters at windriver.com>
Cc: "Hu, Yong" <yong.hu at intel.com>, "starlingx-discuss at lists.starlingx.io" <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Deployment Option (error: compute boot in loop)

Hi Peters,

Output of command :
####################################################
compute-0:~$ dmesg | grep -e DMAR -e IOMMU
[    0.000000] ACPI: DMAR 000000007b69d000 000E0 (v01 INTEL   S2600WT 00000001 INTL 20091013)
[    0.000000] DMAR: IOMMU enabled
[    0.298584] DMAR: Host address width 46
[    0.302872] DMAR: DRHD base: 0x000000fbffc000 flags: 0x0
[    0.308808] DMAR: dmar0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020df
[    0.317647] DMAR: DRHD base: 0x000000c7ffc000 flags: 0x1
[    0.323581] DMAR: dmar1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020df
[    0.332427] DMAR: RMRR base: 0x0000007a3dd000 end: 0x0000007a3dffff
[    0.339426] DMAR: ATSR flags: 0x0
[   11.329277] DMAR: dmar0: Using Queued invalidation
[   11.334645] DMAR: dmar1: Using Queued invalidation
[   11.342303] DMAR: Hardware identity mapping for device 0000:ff:08.0
[   11.349304] DMAR: Hardware identity mapping for device 0000:ff:08.2
[   11.356299] DMAR: Hardware identity mapping for device 0000:ff:08.3
[   11.363296] DMAR: Hardware identity mapping for device 0000:ff:09.0
[   11.370291] DMAR: Hardware identity mapping for device 0000:ff:09.2
[   11.377286] DMAR: Hardware identity mapping for device 0000:ff:09.3
[   11.384281] DMAR: Hardware identity mapping for device 0000:ff:0b.0
[   11.391275] DMAR: Hardware identity mapping for device 0000:ff:0b.1
[   11.398270] DMAR: Hardware identity mapping for device 0000:ff:0b.2
[   11.405265] DMAR: Hardware identity mapping for device 0000:ff:0c.0
[   11.412260] DMAR: Hardware identity mapping for device 0000:ff:0c.1
[   11.419255] DMAR: Hardware identity mapping for device 0000:ff:0c.2
[   11.426250] DMAR: Hardware identity mapping for device 0000:ff:0c.3
[   11.433244] DMAR: Hardware identity mapping for device 0000:ff:0c.4
[   11.440239] DMAR: Hardware identity mapping for device 0000:ff:0c.5
[   11.447234] DMAR: Hardware identity mapping for device 0000:ff:0c.6
[   11.454229] DMAR: Hardware identity mapping for device 0000:ff:0c.7
[   11.461223] DMAR: Hardware identity mapping for device 0000:ff:0d.0
[   11.468218] DMAR: Hardware identity mapping for device 0000:ff:0d.1
[   11.475212] DMAR: Hardware identity mapping for device 0000:ff:0d.2
[   11.482208] DMAR: Hardware identity mapping for device 0000:ff:0d.3
[   11.489202] DMAR: Hardware identity mapping for device 0000:ff:0d.4
[   11.496197] DMAR: Hardware identity mapping for device 0000:ff:0d.5
[   11.503192] DMAR: Hardware identity mapping for device 0000:ff:0d.6
[   11.510186] DMAR: Hardware identity mapping for device 0000:ff:0d.7
[   11.517181] DMAR: Hardware identity mapping for device 0000:ff:0e.0
[   11.524177] DMAR: Hardware identity mapping for device 0000:ff:0e.1
[   11.531172] DMAR: Hardware identity mapping for device 0000:ff:0f.0
[   11.538166] DMAR: Hardware identity mapping for device 0000:ff:0f.1
[   11.545160] DMAR: Hardware identity mapping for device 0000:ff:0f.2
[   11.552155] DMAR: Hardware identity mapping for device 0000:ff:0f.3
[   11.559149] DMAR: Hardware identity mapping for device 0000:ff:0f.4
[   11.566144] DMAR: Hardware identity mapping for device 0000:ff:0f.5
[   11.573138] DMAR: Hardware identity mapping for device 0000:ff:0f.6
[   11.580133] DMAR: Hardware identity mapping for device 0000:ff:10.0
[   11.587128] DMAR: Hardware identity mapping for device 0000:ff:10.1
[   11.594123] DMAR: Hardware identity mapping for device 0000:ff:10.5
[   11.601117] DMAR: Hardware identity mapping for device 0000:ff:10.6
[   11.608111] DMAR: Hardware identity mapping for device 0000:ff:10.7
[   11.615106] DMAR: Hardware identity mapping for device 0000:ff:12.0
[   11.622101] DMAR: Hardware identity mapping for device 0000:ff:12.1
[   11.629095] DMAR: Hardware identity mapping for device 0000:ff:12.4
[   11.636090] DMAR: Hardware identity mapping for device 0000:ff:12.5
[   11.643085] DMAR: Hardware identity mapping for device 0000:ff:13.0
[   11.650079] DMAR: Hardware identity mapping for device 0000:ff:13.1
[   11.657074] DMAR: Hardware identity mapping for device 0000:ff:13.2
[   11.664069] DMAR: Hardware identity mapping for device 0000:ff:13.3
[   11.671063] DMAR: Hardware identity mapping for device 0000:ff:13.6
[   11.678058] DMAR: Hardware identity mapping for device 0000:ff:13.7
[   11.685052] DMAR: Hardware identity mapping for device 0000:ff:14.0
[   11.692047] DMAR: Hardware identity mapping for device 0000:ff:14.1
[   11.699044] DMAR: Hardware identity mapping for device 0000:ff:14.2
[   11.706039] DMAR: Hardware identity mapping for device 0000:ff:14.3
[   11.713034] DMAR: Hardware identity mapping for device 0000:ff:14.4
[   11.720028] DMAR: Hardware identity mapping for device 0000:ff:14.5
[   11.727023] DMAR: Hardware identity mapping for device 0000:ff:14.6
[   11.734018] DMAR: Hardware identity mapping for device 0000:ff:14.7
[   11.741012] DMAR: Hardware identity mapping for device 0000:ff:16.0
[   11.748008] DMAR: Hardware identity mapping for device 0000:ff:16.1
[   11.755002] DMAR: Hardware identity mapping for device 0000:ff:16.2
[   11.761997] DMAR: Hardware identity mapping for device 0000:ff:16.3
[   11.768992] DMAR: Hardware identity mapping for device 0000:ff:16.6
[   11.775987] DMAR: Hardware identity mapping for device 0000:ff:16.7
[   11.782981] DMAR: Hardware identity mapping for device 0000:ff:17.0
[   11.789976] DMAR: Hardware identity mapping for device 0000:ff:17.1
[   11.796971] DMAR: Hardware identity mapping for device 0000:ff:17.2
[   11.803966] DMAR: Hardware identity mapping for device 0000:ff:17.3
[   11.810960] DMAR: Hardware identity mapping for device 0000:ff:17.4
[   11.817955] DMAR: Hardware identity mapping for device 0000:ff:17.5
[   11.824949] DMAR: Hardware identity mapping for device 0000:ff:17.6
[   11.831944] DMAR: Hardware identity mapping for device 0000:ff:17.7
[   11.838939] DMAR: Hardware identity mapping for device 0000:ff:1e.0
[   11.845933] DMAR: Hardware identity mapping for device 0000:ff:1e.1
[   11.852928] DMAR: Hardware identity mapping for device 0000:ff:1e.2
[   11.859923] DMAR: Hardware identity mapping for device 0000:ff:1e.3
[   11.866918] DMAR: Hardware identity mapping for device 0000:ff:1e.4
[   11.873913] DMAR: Hardware identity mapping for device 0000:ff:1f.0
[   11.880908] DMAR: Hardware identity mapping for device 0000:ff:1f.2
[   11.887905] DMAR: Hardware identity mapping for device 0000:7f:08.0
[   11.894899] DMAR: Hardware identity mapping for device 0000:7f:08.2
[   11.901895] DMAR: Hardware identity mapping for device 0000:7f:08.3
[   11.908890] DMAR: Hardware identity mapping for device 0000:7f:09.0
[   11.915885] DMAR: Hardware identity mapping for device 0000:7f:09.2
[   11.922879] DMAR: Hardware identity mapping for device 0000:7f:09.3
[   11.929875] DMAR: Hardware identity mapping for device 0000:7f:0b.0
[   11.936870] DMAR: Hardware identity mapping for device 0000:7f:0b.1
[   11.943865] DMAR: Hardware identity mapping for device 0000:7f:0b.2
[   11.950860] DMAR: Hardware identity mapping for device 0000:7f:0c.0
[   11.957855] DMAR: Hardware identity mapping for device 0000:7f:0c.1
[   11.964849] DMAR: Hardware identity mapping for device 0000:7f:0c.2
[   11.971844] DMAR: Hardware identity mapping for device 0000:7f:0c.3
[   11.978839] DMAR: Hardware identity mapping for device 0000:7f:0c.4
[   11.985833] DMAR: Hardware identity mapping for device 0000:7f:0c.5
[   11.992828] DMAR: Hardware identity mapping for device 0000:7f:0c.6
[   11.999823] DMAR: Hardware identity mapping for device 0000:7f:0c.7
[   12.006818] DMAR: Hardware identity mapping for device 0000:7f:0d.0
[   12.013814] DMAR: Hardware identity mapping for device 0000:7f:0d.1
[   12.020801] DMAR: Hardware identity mapping for device 0000:7f:0d.2
[   12.027796] DMAR: Hardware identity mapping for device 0000:7f:0d.3
[   12.034790] DMAR: Hardware identity mapping for device 0000:7f:0d.4
[   12.041785] DMAR: Hardware identity mapping for device 0000:7f:0d.5
[   12.048781] DMAR: Hardware identity mapping for device 0000:7f:0d.6
[   12.055776] DMAR: Hardware identity mapping for device 0000:7f:0d.7
[   12.062771] DMAR: Hardware identity mapping for device 0000:7f:0e.0
[   12.069766] DMAR: Hardware identity mapping for device 0000:7f:0e.1
[   12.076761] DMAR: Hardware identity mapping for device 0000:7f:0f.0
[   12.083756] DMAR: Hardware identity mapping for device 0000:7f:0f.1
[   12.090752] DMAR: Hardware identity mapping for device 0000:7f:0f.2
[   12.097747] DMAR: Hardware identity mapping for device 0000:7f:0f.3
[   12.104741] DMAR: Hardware identity mapping for device 0000:7f:0f.4
[   12.111736] DMAR: Hardware identity mapping for device 0000:7f:0f.5
[   12.118731] DMAR: Hardware identity mapping for device 0000:7f:0f.6
[   12.125726] DMAR: Hardware identity mapping for device 0000:7f:10.0
[   12.132721] DMAR: Hardware identity mapping for device 0000:7f:10.1
[   12.139716] DMAR: Hardware identity mapping for device 0000:7f:10.5
[   12.146713] DMAR: Hardware identity mapping for device 0000:7f:10.6
[   12.153708] DMAR: Hardware identity mapping for device 0000:7f:10.7
[   12.160703] DMAR: Hardware identity mapping for device 0000:7f:12.0
[   12.167698] DMAR: Hardware identity mapping for device 0000:7f:12.1
[   12.174693] DMAR: Hardware identity mapping for device 0000:7f:12.4
[   12.181688] DMAR: Hardware identity mapping for device 0000:7f:12.5
[   12.188683] DMAR: Hardware identity mapping for device 0000:7f:13.0
[   12.195678] DMAR: Hardware identity mapping for device 0000:7f:13.1
[   12.202673] DMAR: Hardware identity mapping for device 0000:7f:13.2
[   12.209668] DMAR: Hardware identity mapping for device 0000:7f:13.3
[   12.216663] DMAR: Hardware identity mapping for device 0000:7f:13.6
[   12.223658] DMAR: Hardware identity mapping for device 0000:7f:13.7
[   12.230653] DMAR: Hardware identity mapping for device 0000:7f:14.0
[   12.237648] DMAR: Hardware identity mapping for device 0000:7f:14.1
[   12.244643] DMAR: Hardware identity mapping for device 0000:7f:14.2
[   12.251638] DMAR: Hardware identity mapping for device 0000:7f:14.3
[   12.258634] DMAR: Hardware identity mapping for device 0000:7f:14.4
[   12.265629] DMAR: Hardware identity mapping for device 0000:7f:14.5
[   12.272624] DMAR: Hardware identity mapping for device 0000:7f:14.6
[   12.279620] DMAR: Hardware identity mapping for device 0000:7f:14.7
[   12.286615] DMAR: Hardware identity mapping for device 0000:7f:16.0
[   12.293610] DMAR: Hardware identity mapping for device 0000:7f:16.1
[   12.300605] DMAR: Hardware identity mapping for device 0000:7f:16.2
[   12.307600] DMAR: Hardware identity mapping for device 0000:7f:16.3
[   12.314595] DMAR: Hardware identity mapping for device 0000:7f:16.6
[   12.321590] DMAR: Hardware identity mapping for device 0000:7f:16.7
[   12.328585] DMAR: Hardware identity mapping for device 0000:7f:17.0
[   12.335580] DMAR: Hardware identity mapping for device 0000:7f:17.1
[   12.342575] DMAR: Hardware identity mapping for device 0000:7f:17.2
[   12.349570] DMAR: Hardware identity mapping for device 0000:7f:17.3
[   12.356565] DMAR: Hardware identity mapping for device 0000:7f:17.4
[   12.363564] DMAR: Hardware identity mapping for device 0000:7f:17.5
[   12.370563] DMAR: Hardware identity mapping for device 0000:7f:17.6
[   12.377562] DMAR: Hardware identity mapping for device 0000:7f:17.7
[   12.384561] DMAR: Hardware identity mapping for device 0000:7f:1e.0
[   12.391560] DMAR: Hardware identity mapping for device 0000:7f:1e.1
[   12.398555] DMAR: Hardware identity mapping for device 0000:7f:1e.2
[   12.405550] DMAR: Hardware identity mapping for device 0000:7f:1e.3
[   12.412545] DMAR: Hardware identity mapping for device 0000:7f:1e.4
[   12.419541] DMAR: Hardware identity mapping for device 0000:7f:1f.0
[   12.426536] DMAR: Hardware identity mapping for device 0000:7f:1f.2
[   12.433533] DMAR: Hardware identity mapping for device 0000:00:00.0
[   12.440529] DMAR: Hardware identity mapping for device 0000:00:01.0
[   12.447523] DMAR: Hardware identity mapping for device 0000:00:02.0
[   12.454519] DMAR: Hardware identity mapping for device 0000:00:02.2
[   12.461514] DMAR: Hardware identity mapping for device 0000:00:03.0
[   12.468509] DMAR: Hardware identity mapping for device 0000:00:04.0
[   12.475504] DMAR: Hardware identity mapping for device 0000:00:04.1
[   12.482499] DMAR: Hardware identity mapping for device 0000:00:04.2
[   12.489495] DMAR: Hardware identity mapping for device 0000:00:04.3
[   12.496490] DMAR: Hardware identity mapping for device 0000:00:04.4
[   12.503486] DMAR: Hardware identity mapping for device 0000:00:04.5
[   12.510481] DMAR: Hardware identity mapping for device 0000:00:04.6
[   12.517479] DMAR: Hardware identity mapping for device 0000:00:04.7
[   12.524474] DMAR: Hardware identity mapping for device 0000:00:05.0
[   12.531469] DMAR: Hardware identity mapping for device 0000:00:05.1
[   12.538465] DMAR: Hardware identity mapping for device 0000:00:05.2
[   12.545461] DMAR: Hardware identity mapping for device 0000:00:05.4
[   12.552456] DMAR: Hardware identity mapping for device 0000:00:11.0
[   12.559451] DMAR: Hardware identity mapping for device 0000:00:11.1
[   12.566449] DMAR: Hardware identity mapping for device 0000:00:11.4
[   12.573444] DMAR: Hardware identity mapping for device 0000:00:14.0
[   12.580440] DMAR: Hardware identity mapping for device 0000:00:16.0
[   12.587436] DMAR: Hardware identity mapping for device 0000:00:16.1
[   12.594433] DMAR: Hardware identity mapping for device 0000:00:1a.0
[   12.601429] DMAR: Hardware identity mapping for device 0000:00:1c.0
[   12.608424] DMAR: Hardware identity mapping for device 0000:00:1c.3
[   12.615419] DMAR: Hardware identity mapping for device 0000:00:1d.0
[   12.622415] DMAR: Hardware identity mapping for device 0000:00:1f.0
[   12.629410] DMAR: Hardware identity mapping for device 0000:00:1f.2
[   12.636405] DMAR: Hardware identity mapping for device 0000:00:1f.3
[   12.643402] DMAR: Hardware identity mapping for device 0000:02:00.0
[   12.650397] DMAR: Hardware identity mapping for device 0000:02:00.1
[   12.657394] DMAR: Hardware identity mapping for device 0000:04:00.0
[   12.664390] DMAR: Hardware identity mapping for device 0000:04:00.3
[   12.671390] DMAR: Hardware identity mapping for device 0000:08:00.0
[   12.678388] DMAR: Hardware identity mapping for device 0000:80:04.0
[   12.685384] DMAR: Hardware identity mapping for device 0000:80:04.1
[   12.692371] DMAR: Hardware identity mapping for device 0000:80:04.2
[   12.699358] DMAR: Hardware identity mapping for device 0000:80:04.3
[   12.706346] DMAR: Hardware identity mapping for device 0000:80:04.4
[   12.713341] DMAR: Hardware identity mapping for device 0000:80:04.5
[   12.720336] DMAR: Hardware identity mapping for device 0000:80:04.6
[   12.727331] DMAR: Hardware identity mapping for device 0000:80:04.7
[   12.734331] DMAR: Hardware identity mapping for device 0000:80:05.0
[   12.741327] DMAR: Hardware identity mapping for device 0000:80:05.1
[   12.748314] DMAR: Hardware identity mapping for device 0000:80:05.2
[   12.755301] DMAR: Hardware identity mapping for device 0000:80:05.4
[   12.762287] DMAR: Setting RMRR:
[   12.765793] DMAR: Ignoring identity map for HW passthrough device 0000:00:1a.0 [0x7a3dd000 - 0x7a3dffff]
[   12.776376] DMAR: Ignoring identity map for HW passthrough device 0000:00:1d.0 [0x7a3dd000 - 0x7a3dffff]
[   12.786965] DMAR: Prepare 0-16MiB unity mapping for LPC
[   12.792797] DMAR: Ignoring identity map for HW passthrough device 0000:00:1f.0 [0x0 - 0xffffff]
[   12.802607] DMAR: Intel(R) Virtualization Technology for Directed I/O
[   14.693008] DMAR: 32bit 0000:00:1a.0 uses non-identity mapping
[   14.702309] DMAR: Setting identity map for device 0000:00:1a.0 [0x7a3dd000 - 0x7a3dffff]
[   14.762084] DMAR: 32bit 0000:00:1d.0 uses non-identity mapping
[   14.770843] DMAR: Setting identity map for device 0000:00:1d.0 [0x7a3dd000 - 0x7a3dffff]
compute-0:~$
compute-0:~$
####################################################################################

Regards,
Himanshu Goyal

On Thu, Jan 24, 2019 at 6:56 PM Peters, Matt <Matt.Peters at windriver.com<mailto:Matt.Peters at windriver.com>> wrote:
Can you confirm that VT-d is enabled properly by running the following?

dmesg | grep -e DMAR -e IOMMU

From: Himanshu Goyal <himanshugoyal500 at gmail.com<mailto:himanshugoyal500 at gmail.com>>
Date: Thursday, January 24, 2019 at 8:19 AM
To: "Peters, Matt" <Matt.Peters at windriver.com<mailto:Matt.Peters at windriver.com>>
Cc: "Hu, Yong" <yong.hu at intel.com<mailto:yong.hu at intel.com>>, "starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>" <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: Re: [Starlingx-discuss] Deployment Option (error: compute boot in loop)

Hi Peters,

Error logs ovs-vswitched.log:
#######################################
2019-01-24T18:42:04.213Z|00830|dpdk|INFO|EAL: PCI device 0000:02:00.0 on NUMA socket 0
2019-01-24T18:42:04.213Z|00831|dpdk|INFO|EAL:   probe driver: 8086:10fb net_ixgbe
2019-01-24T18:42:04.215Z|00832|dpdk|ERR|EAL:   0000:02:00.0 failed to select IOMMU type
2019-01-24T18:42:04.215Z|00833|dpdk|ERR|EAL: Driver cannot attach the device (0000:02:00.0)
2019-01-24T18:42:04.215Z|00834|netdev_dpdk|WARN|Error attaching device '0000:02:00.0' to DPDK
2019-01-24T18:42:04.215Z|00835|netdev|WARN|eth0: could not set configuration (Invalid argument)
########################################

Please find attached log file also.

Regards,
Himanshu Goyal

On Thu, Jan 24, 2019 at 6:32 PM Peters, Matt <Matt.Peters at windriver.com<mailto:Matt.Peters at windriver.com>> wrote:
The name of eth0 is correct.  It is just an assigned name by configuration management.

What err logs are present in /var/log/openvswitch/ovs-vswitchd.log?

From: Himanshu Goyal <himanshugoyal500 at gmail.com<mailto:himanshugoyal500 at gmail.com>>
Date: Thursday, January 24, 2019 at 6:52 AM
To: "Hu, Yong" <yong.hu at intel.com<mailto:yong.hu at intel.com>>
Cc: "starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>" <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: Re: [Starlingx-discuss] Deployment Option (error: compute boot in loop)

Thanks a lot Yong,

Checked OVS/DPDK status, It is giving me the error as output shown below:
In br-phy0 is attaching a port name as eth0, but my compute port name is ens513f0, i think that may be the issue.

#################################################################################
ovs-vsctl show output:
compute-0:/usr/share/openvswitch/scripts$ sudo ovs-vsctl show
543d08f4-ff1e-4a8d-8e48-11f01356750d
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge "br-phy0"
        Controller "tcp:127.0.0.1:6633<http://127.0.0.1:6633>"
            is_connected: true
        fail_mode: secure
        Port "phy-br-phy0"
            Interface "phy-br-phy0"
                type: patch
                options: {peer="int-br-phy0"}
        Port "br-phy0"
            Interface "br-phy0"
                type: internal
        Port "lldpabeb30a6-6c"
            Interface "lldpabeb30a6-6c"
                type: internal
        Port "eth0"
            Interface "eth0"
                type: dpdk
                options: {dpdk-devargs="0000:02:00.0", n_rxq="2"}
                error: "Error attaching device '0000:02:00.0' to DPDK"
    Bridge br-int
        Controller "tcp:127.0.0.1:6633<http://127.0.0.1:6633>"
            is_connected: true
        fail_mode: secure
        Port "int-br-phy0"
            Interface "int-br-phy0"
                type: patch
                options: {peer="phy-br-phy0"}
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "2.9.0"
#####################################################################################################

##############################################################################
Output of dpdk-devbind.py:

compute-0:/usr/share/openvswitch/scripts$ python /usr/share/openvswitch/scripts/dpdk-devbind.py --status

Network devices using DPDK-compatible driver
============================================
0000:02:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=vfio-pci unused=

Network devices using kernel driver
===================================
0000:02:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' if=ens513f1 drv=ixgbe unused=vfio-pci *Active*
0000:04:00.0 'I350 Gigabit Network Connection 1521' if=enp4s0f0 drv=igb unused=vfio-pci
0000:04:00.3 'I350 Gigabit Network Connection 1521' if=enp4s0f3 drv=igb unused=vfio-pci

Other Network devices
=====================
<none>

Crypto devices using DPDK-compatible driver
===========================================
<none>

Crypto devices using kernel driver
==================================
<none>

Other Crypto devices
====================
<none>

Eventdev devices using DPDK-compatible driver
=============================================
<none>

Eventdev devices using kernel driver
====================================
<none>

Other Eventdev devices
======================
<none>

Mempool devices using DPDK-compatible driver
============================================
<none>

Mempool devices using kernel driver
===================================
<none>

Other Mempool devices
=====================
<none>
compute-0:/usr/share/openvswitch/scripts$
 #############################################################

Both management and OAM ports support DPDK.

lspci output:
##################################################
compute-0:/usr/share/openvswitch/scripts$ lspci -nn | grep Eth
02:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
02:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
04:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
04:00.3 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
###############################################################
compute-0:/usr/share/openvswitch/scripts$


Many Thanks,
Himanshu Goyal


On Thu, Jan 24, 2019 at 2:24 PM Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>> wrote:
I saw you enabled VT-D, how about VT-x in BIOS?

Another possibility is that your ethernet NIC is not compatible with OVS/DPDK.
Please follow these steps, to dig out more info

  1.  lock your compute-node
  2.  ssh to your compute-node and check OVS/DPDK status by “sudo ovs-vsctl show” and “python /usr/share/openvswitch/scripts/dpdk-devbind.py --status”

From: Himanshu Goyal <himanshugoyal500 at gmail.com<mailto:himanshugoyal500 at gmail.com>>
Date: Thursday, 24 January 2019 at 4:46 PM
To: "Hu, Yong" <yong.hu at intel.com<mailto:yong.hu at intel.com>>
Cc: "Alonso, Juan Carlos" <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>, "starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>" <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: Re: [Starlingx-discuss] Deployment Option (error: compute boot in loop)
Hi Yong,

I checked server BIOS setting Intel VT-D is enabled in my compute machine
compute machine is rebooting only after unlocking, Before reboot it came in unlocked, enabled & online.

Please suggest how can i debug this.

Many Thanks,
Himanshu Goyal

On Wed, Jan 23, 2019 at 9:40 PM Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>> wrote:
Intel_iommu=on and immmu are for PCI PT and SR-IOV, as far as I know.
There are other 2, like VT-x and VT-d flags, to be enabled. Please have a look in BIOS.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190124/e3c250d8/attachment-0001.html>

More information about the Starlingx-discuss mailing list