Legacy Cisco hardware emulation (e.g., Cisco 7200 routers). These are rarely used in modern labs but are supported. They belong in the /opt/unetlab/addons/dynamips/ directory. 2. Official Sources for Downloading Images

Vendors like Fortinet, Palo Alto, and F5 often offer "KVM" or "QCOW2" trial images for lab use. 2. Supported Image Types

Searching for is the natural first step for any engineer building a virtual lab. But the secret is that EVE-NG does not host the images—it simply runs them.

If you want, I can generate step-by-step commands and the exact folder structure for a specific OS (e.g., Cisco IOSv, Juniper vSRX, or pfSense). Which device/image should I detail?

While not official, some community members share resource lists or pre-configured packs: How to load images - - EVE-NG

Vendor → License → RAW Image → Upload → Convert → Permissions → Run.

Which (e.g., Cisco Nexus, Juniper vSRX, FortiGate) are you trying to set up right now?

If the node name is grayed out in the "Add a New Node" side menu, EVE-NG cannot find a folder with the correct prefix inside /opt/unetlab/addons/qemu/ . Double-check your spelling and hyphens.

cd /opt/unetlab/addons/qemu/csr1000vng-16.12.05/ mv target-file-name.qcow2 virtioa.qcow2 Use code with caution.

Once you have downloaded your preferred .qcow2 or image file, follow these precise steps to import it into EVE-NG. For this example, we will use a standard Cisco ASA or generic firewall image. Step 1: Connect to your EVE-NG Server

The process of acquiring and "fixing" images is often the biggest hurdle for new users.

Sometimes you download a .vmdk (VMware) or .img file. EVE-NG prefers . Here is how to convert using QEMU tools.

PAN-OS Vagrant boxes or KVM images can be downloaded via the Palo Alto Customer Support Portal with a valid support contract. 3. Standard Naming Conventions