R4.1 build 16: Netronome build 73: virtio-forwarder failed to come up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Won't Fix
|
Undecided
|
Pieter Malan | ||
R4.1 |
Won't Fix
|
Critical
|
Pieter Malan | ||
Trunk |
Won't Fix
|
Undecided
|
Pieter Malan |
Bug Description
I've taken netronome build 73 , but see that virtio-forwarder is not able to come up as shown below
root@nodel9:
● virtio-
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Mon 2018-10-22 18:54:05 UTC; 1h 31min ago
Main PID: 4393 (code=exited, status=255)
Oct 22 18:52:59 nodel9 virtio-
Oct 22 18:52:59 nodel9 vio4wd-
Oct 22 18:52:59 nodel9 vio4wd-
Oct 22 18:52:59 nodel9 virtio-
Oct 22 18:54:04 nodel9 vio4wd-
Oct 22 18:54:04 nodel9 vio4wd-
Oct 22 18:54:04 nodel9 vio4wd-
Oct 22 18:54:04 nodel9 systemd[1]: virtio-
Oct 22 18:54:05 nodel9 systemd[1]: virtio-
Oct 22 18:54:05 nodel9 systemd[1]: virtio-
root@nodel9:
exit
tags: | added: blocker |
tags: | added: releasenote |
Changed in juniperopenstack: | |
status: | New → Won't Fix |
tags: | removed: blocker |
This issue is a result of a memory setting which is configured too low by default. 'max_map_count' has to be increased to > 2x the number of 2M pages. For example, vm/max_ map_count
echo 140000 > /proc/sys/
works for 65536 2M pages. virtio-forwarder starts fine with this change in place. Startup time is proportional to the number of pages, so expect a slow start with the above config.