ivshmem target may cause hugepage allocation to fail.

Bug #1517032 reported by sean mooney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovs-dpdk
Fix Released
High
sean mooney

Bug Description

using the ivshmem dpdk build target may intermitently cause the following error

>>
EAL: 25568 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Searching for IVSHMEM devices...
EAL: No IVSHMEM configuration found!
EAL: Setting up memory...
EAL: Ask a virtual area of 0x3c0000000 bytes
EAL: Virtual area found at 0x7fcbc0000000 (size = 0x3c0000000)
EAL: Segment sanity check failed: wrong physaddr at 0x7fcc80000000 (offset 0xc0000000: 0x29c0000000 (expected 0x14c0000000)
EAL: Failed to remap 1024 MB pages
PANIC in rte_eal_init():
Cannot init memory
7: [/usr/sbin/ovs-vswitchd() [0x4082f3]]
6: [/lib64/libc.so.6(__libc_start_main+0xf0) [0x7fd0099a8fe0]]
5: [/usr/sbin/ovs-vswitchd() [0x407329]]
4: [/usr/sbin/ovs-vswitchd() [0x67ac17]]
3: [/usr/sbin/ovs-vswitchd() [0x52214e]]
2: [/usr/sbin/ovs-vswitchd() [0x406442]]
1: [/usr/sbin/ovs-vswitchd() [0x48bf86]]
>>

to avoid this edge case in the ci the default RTE_TARGET should be change to x86_64-native-linuxapp-gcc

Changed in networking-ovs-dpdk:
status: New → Triaged
importance: Undecided → High
Revision history for this message
sean mooney (sean-k-mooney) wrote :
Changed in networking-ovs-dpdk:
assignee: nobody → sean mooney (sean-k-mooney)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovs-dpdk (master)

Reviewed: https://review.openstack.org/246375
Committed: https://git.openstack.org/cgit/openstack/networking-ovs-dpdk/commit/?id=76854d0223729ecd6ef08e486ee3670bb0a3b354
Submitter: Jenkins
Branch: master

commit 76854d0223729ecd6ef08e486ee3670bb0a3b354
Author: Sean Mooney <email address hidden>
Date: Tue Nov 17 13:06:19 2015 +0000

    Updated default RTE_TARGET

    - set default RTE_TARGET to x86_64-native-linuxapp-gcc to pervent
      EAL: Segment sanity check failed: wrong physaddr at 0x7fcc80000000
      (offset 0xc0000000: 0x29c0000000 (expected 0x14c0000000) error.

    Change-Id: I2eb5aa0c11f7efdc9ad93c4e66e61ca522255277
    Closes-Bug: #1517032

Changed in networking-ovs-dpdk:
status: Triaged → Fix Committed
Changed in networking-ovs-dpdk:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.