Junguk Cho <jman...@gmail.com> writes: > Hi, > > I use ovs-dpdk (ovs-2.7, dpdk-16.11.1) with one application which talks to > ovs by using ring device and "--proc-type=secondary" (secondary processes). > It generally works well, but sometimes it shows this error. > > It seems it could not find correct memory mapping in the application. > > 2017-06-13 11:21:40.988 STDERR Thread-2 [INFO] EAL: Probing VFIO support... > 2017-06-13 11:21:40.988 STDERR Thread-2 [INFO] EAL: WARNING: Address Space > Layout Randomization (ASLR) is enabled in the kernel. > 2017-06-13 11:21:40.988 STDERR Thread-2 [INFO] EAL: This may cause > issues with mapping memory into secondary processes > 2017-06-13 11:21:40.989 STDERR Thread-2 [INFO] EAL: Could not mmap > 17146314752 <(714)%20631-4752> bytes in /dev/zero at [0x7f662c800000], got > [0x7f6506000000] - please use '--base-virtaddr' option > 2017-06-13 11:21:40.989 STDERR Thread-2 [INFO] EAL: It is recommended to > disable ASLR in the kernel and retry running both primary and secondary > processes > 2017-06-13 11:21:40.990 STDERR Thread-2 [INFO] PANIC in rte_eal_init(): > 2017-06-13 11:21:40.990 STDERR Thread-2 [INFO] Cannot init memory > > I tried to disable ASLR, but it did not work. > > Does anyone have a similar situation? > Based on this page (https://github.com/collectd/collectd/issues/2284), this > is known issue and it seemed we can avoid this with "--base-virtaddr" > option. > Does anyone know how to use this option in ovs-dpdk?
You will need to use populate this option into other_config:dpdk-extra in the ovsdb. ovs-vsctl --no-wait set Open_vSwitch \ . other_config:dpdk-extra="--base-virtaddr=..." I don't know the base virtual address value you should use, however. -Aaron _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev