EVE-NG needs a vmx.sh startup script to link VCP and VFP. Create the file:

nano /opt/unetlab/addons/qemu/vmx-20.4R3.8/vmx.sh

Paste the following:

#!/bin/bash
/opt/qemu/bin/qemu-system-x86_64 -nographic -device e1000,netdev=net0,mac=50:00:00:01:00:00 -netdev user,id=net0 \
  -drive file=virtioa.qcow2,if=virtio -drive file=virtiob.qcow2,if=virtio -m 4096 -smp 2

Make executable:

chmod +x /opt/unetlab/addons/qemu/vmx-20.4R3.8/vmx.sh

Juniper vMX is a virtualized version of the Juniper MX Series 3D Universal Edge Routers. It is widely used by network engineers to simulate MPLS, BGP, and advanced routing scenarios in EVE-NG. Unlike some vendor images that are distributed as single ISO files, vMX requires a specific "nested virtualization" architecture (KVM inside EVE-NG) and typically consists of multiple disk images.

Key Challenge: You cannot legally download vMX via a simple "link" without authorization. It requires a valid Juniper account and an active license or evaluation entitlement.

Once the software package is obtained from Juniper, it cannot be uploaded directly. It must be converted and structured specifically for EVE-NG.

A. Step-by-Step Preparation:

  • Upload to EVE-NG: Using SCP (WinSCP) or FileZilla, upload the specific image files to the EVE-NG server directory: /opt/unetlab/addons/qemu/vmx-<version>/.

    • B. Folder Structure Best Practices: EVE-NG expects a specific naming convention for the disk files inside the created directory.

    Solution: Your VFP image is corrupt or not found. Verify virtiob.qcow2 exists and rerun fixpermissions.

    If the download hurdles are too high, consider:

    Each of these is easier to obtain for EVE-NG.