Tested on VM with 7,5 Gb of RAM
```
vyos@vyos# set vpp settings interface eth1 driver dpdk
[edit]
vyos@vyos# commit
[edit]
vyos@vyos:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address MAC VRF MTU S/L Description
----------- ------------------ ----------------- ------- ----- ----- -------------
eth0 192.168.122.174/24 0c:1f:39:e1:00:00 default 1500 u/u
eth1 192.168.11.1/24 0c:1f:39:e1:00:01 default 1500 u/u
eth2 192.168.12.1/24 0c:1f:39:e1:00:02 default 1500 u/u
eth3 192.168.134.150/24 0c:1f:39:e1:00:03 default 1500 u/u
lo 127.0.0.1/8 00:00:00:00:00:00 default 65536 u/u
::1/128
vyos@vyos:~$ ip link show eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 0c:1f:39:e1:00:01 brd ff:ff:ff:ff:ff:ff
altname enp0s3
```
Changes:
```
vyos@vyos# set vpp settings memory main-heap-size '8G'
[edit]
vyos@vyos# commit
[ vpp ]
We are sorry that you encountered a problem while using VyOS.
There are a few things you can do to help us (and yourself):
- Contact us using the online help desk if you have a subscription:
https://support.vyos.io/
- Make sure you are running the latest version of VyOS available at:
https://vyos.net/get/
- Consult the community forum to see how to handle this issue:
https://forum.vyos.io
- Join us on Slack where our users exchange help and advice:
https://vyos.slack.com
When reporting problems, please include as much information as possible:
- do not obfuscate any data (feel free to contact us privately if your
business policy requires it)
- and include all the information presented below
Report time: 2024-03-21 11:15:05
Image version: VyOS 1.5-rolling-202403190019
Release train: current
Built by: autobuild@vyos.net
Built on: Tue 19 Mar 2024 02:19 UTC
Build UUID: a0790664-80d6-4ab6-bac3-346ef6f1f8aa
Build commit ID: a690a02bdcda23
Architecture: x86_64
Boot via: installed image
System type: KVM guest
Hardware vendor: QEMU
Hardware model: Standard PC (Q35 + ICH9, 2009)
Hardware S/N:
Hardware UUID: bd1f39e1-2eb2-46e7-8936-ee44eef14915
Traceback (most recent call last):
File "/usr/libexec/vyos/conf_mode/addons/vpp/vpp.py", line 433, in <module>
apply(c)
File "/usr/libexec/vyos/conf_mode/addons/vpp/vpp.py", line 366, in apply
vpp_control = VPPControl(attempts=20, interval=500)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/vyos/addons/vpp/control_vpp.py", line 111, in __init__
raise VPPIOError(2, 'Cannot connect to VPP API')
vpp_papi.vpp_papi.VPPIOError: [Errno 2] Cannot connect to VPP API
[[vpp]] failed
Commit failed
```
With the next commit we get message "Interface does not exist":
```
vyos@vyos# set vpp settings memory main-heap-size '4G'
[edit]
vyos@vyos# commit
[ vpp ]
Interface eth1 does not exist or is not Ethernet!
[[vpp]] failed
Commit failed
[edit]
vyos@vyos# run show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address MAC VRF MTU S/L Description
----------- ------------------ ----------------- ------- ----- ----- -------------
eth0 192.168.122.174/24 0c:1f:39:e1:00:00 default 1500 u/u
eth2 192.168.12.1/24 0c:1f:39:e1:00:02 default 1500 u/u
eth3 192.168.134.150/24 0c:1f:39:e1:00:03 default 1500 u/u
lo 127.0.0.1/8 00:00:00:00:00:00 default 65536 u/u
::1/128
[edit]
vyos@vyos# ip link show eth1
Device "eth1" does not exist.
[edit]
vyos@vyos#
```