Edged process not starting for KVM virtual Edge deployment on top of third party vendor due to FATAL error

Products

• VMware VeloCloud SD-WAN

Issue/Introduction

When customer deploying KVM edge on top of third party hypervisor such as juniper device , customer might face the issue of edged process not starting and debug commands displaying the output of "server not listening" instead of relevant outputs

Environment

VMware Velocloud SDWAN

Cause

The issue might be caused due to proper resource allocation wasn't provided on third party hypervisor such CPU/Memory allocation.

Example <vcpu pin vcpu='0' cpuset='1'/> . the virtual cpu is binded to physical core.

In the above example virtual cpu was incorrectly configured as zero.

Incase proper allocation wasn't provided for the virtual edge , below FATAL error will be generated on the edge.

Error Message :

INFO [edged 5999(6009)] err: [7076 ] EAL: FATAL: Cannot get hugepage information.

Resolution

We request the customer to engage third party hypervisor and verify whether proper resource allocation allotted for the virtual edge on hypervisor environment.