Page MenuHomeVyOS Platform

VPP does not support veth interfaces
Closed, ResolvedPublicBUG

Description

Attempt to use VPP VyOS in the containerlab

admin@vyos1# sudo ethtool -i eth1
driver: veth
version: 1.0
firmware-version: 
expansion-rom-version: 
bus-info: 
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
[edit]
admin@vyos1#

Config:

admin@vyos1# set vpp settings interface eth1 driver dpdk 
[edit]
admin@vyos1# commit
[ vpp ]
Traceback (most recent call last):
  File "/usr/libexec/vyos/services/vyos-configd", line 145, in run_script
    script.verify(c)
  File "/usr/libexec/vyos/conf_mode/vpp.py", line 483, in verify
    if not verify_dev_driver(iface, iface_config['driver']):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/vyos/vpp/config_verify.py", line 169, in verify_dev_driver
    driver: str = get_eth_driver(iface_name)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/vyos/vpp/control_host.py", line 273, in get_eth_driver
    raise FileNotFoundError(f'PCI device {iface} not found in ethernet interfaces')
FileNotFoundError: PCI device eth1 not found in ethernet interfaces

[[vpp]] failed
Commit failed
[edit]
admin@vyos1# 


admin@vyos1# run show ver
Version:          VyOS 2025.09.27-0018-rolling
Release train:    current
Release flavor:   generic

Built by:         autobuild@vyos.net
Built on:         Sat 27 Sep 2025 00:18 UTC
Build UUID:       af6c0769-8971-4f88-a9e4-e81f5aa7e246
Build commit ID:  137b20e4253f02

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest
Secure Boot:      n/a (BIOS)

Hardware vendor:  QEMU
Hardware model:   Standard PC (Q35 + ICH9, 2009)
Hardware S/N:     
Hardware UUID:    ca1f5536-cdd2-468a-b19b-b26702f81070

Copyright:        VyOS maintainers and contributors
[edit]
admin@vyos1#

The containerlab topology:

$ cat vyos.clab.yml 
name: vyos_lab

topology:
  #kinds:
  #  vyosnetworks_vyos:
  #    startup-config: vyos-custom-startup.cfg
  nodes:
    # vyos1 will boot with vyos-custom-startup.cfg as set in the kind parameters
    vyos1:
      kind: vyosnetworks_vyos
      image: ghcr.io/sever-sever/vyos-container:latest
    # vyos2 will boot with its own specific startup config, as it overrides the kind variables
    vyos2:
      kind: vyosnetworks_vyos
      image: ghcr.io/sever-sever/vyos-container:latest
      #startup-config: node-specific-startup.cfg
  links:
    - endpoints: ["vyos1:eth1", "vyos2:eth1"]

Details

Version
VyOS 2025.09.27-0018-rolling
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Event Timeline

At least there should be a proper Error message.

Unknown Object (User) triaged this task as Normal priority.Oct 3 2025, 12:00 PM
Viacheslav changed the task status from Open to In progress.Oct 10 2025, 12:35 PM
Viacheslav claimed this task.
natali-rs1985 changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
natali-rs1985 moved this task from Need Triage to Completed on the VyOS Rolling board.