Is this bug always on the same machine or different machines?
The similar issue (https://bugs.launchpad.net/starlingx/+bug/1829390) is caused by that hugepage is not allocated. Could you please run following commands on compute-3 to check the hugepage and attach the outputs?
sudo find /sys -name "nr_huge*"
sudo find /sys -name "nr_huge*" | xargs -L1 grep -E "^"
sudo find /sys -name "free_hugepages*"
sudo find /sys -name "free_hugepages" | xargs -L1 grep -E "^"
mount | grep -i huge
cat /proc/cmdline
If hugepage is not allocated, could you please try to allocate hugepage by following command and then restart ovs-vswitchd as I described in comment #2 in https://bugs.launchpad.net/starlingx/+bug/1829390
Hi Peng,
Is this bug always on the same machine or different machines?
The similar issue (https:/ /bugs.launchpad .net/starlingx/ +bug/1829390) is caused by that hugepage is not allocated. Could you please run following commands on compute-3 to check the hugepage and attach the outputs?
sudo find /sys -name "nr_huge*"
sudo find /sys -name "nr_huge*" | xargs -L1 grep -E "^"
sudo find /sys -name "free_hugepages*"
sudo find /sys -name "free_hugepages" | xargs -L1 grep -E "^"
mount | grep -i huge
cat /proc/cmdline
If hugepage is not allocated, could you please try to allocate hugepage by following command and then restart ovs-vswitchd as I described in comment #2 in https:/ /bugs.launchpad .net/starlingx/ +bug/1829390