The Digital Workbench: Understanding QEMU Images in EVE-NG In the realm of network engineering and cybersecurity, the ability to simulate complex environments is not just a luxury—it is a professional necessity. EVE-NG (Emulated Virtual Environment Next Generation)
stands as a premier platform for this purpose, providing a robust framework where engineers can build, test, and troubleshoot intricate topologies. At the heart of this platform’s versatility lies the QEMU (Quick Emulator)
image system, which serves as the fundamental building block for virtualizing high-end networking hardware and operating systems. The Role of QEMU in Virtualization
QEMU is a hosted virtual machine monitor that performs hardware virtualization. Within EVE-NG, QEMU images act as the "software DNA" of physical devices. Whether it is a Cisco router, a Palo Alto firewall, or a Linux server, the QEMU image contains the necessary operating system and configuration files to mimic the behavior of physical hardware. This allows users to run actual vendor software—not just simulations—providing a high-fidelity experience that reflects real-world performance and syntax. The Importance of Sourcing Images
Downloading and integrating these images is a critical step in setting up a functional lab. However, it is a process governed by two major factors: technical compatibility legal compliance Technical Compatibility:
EVE-NG requires specific naming conventions and folder structures (such as the virtioa.qcow2 format) to recognize and boot images correctly. Legal Compliance:
Most enterprise networking images are proprietary. Users are generally expected to download these directly from official vendor portals—such as Cisco Software Central Juniper Support Portal
—using valid support contracts or licenses. Using unauthorized "pre-made" image packs from third-party sites often risks malware exposure and violates End User License Agreements (EULAs). The Impact on Professional Development
The accessibility of QEMU images has democratized high-level networking education. Previously, mastering enterprise-grade gear required access to expensive physical labs. Today, a well-provisioned EVE-NG server populated with the right QEMU images allows a student or professional to: Iterate Rapidly:
Test configuration changes in seconds without the risk of a network outage. Validate Designs:
Mock up a client’s entire infrastructure to ensure a new feature won't break existing routing. Cross-Train:
Easily switch between different vendors (e.g., Arista to Fortinet) within the same interface. Conclusion
The "EVE-NG QEMU image" is more than just a file; it is the bridge between theoretical knowledge and practical expertise. By mastering the acquisition and deployment of these images, network professionals transform their computers into powerful laboratories, fostering an environment of continuous learning and rigorous testing that is essential in today’s rapidly evolving technological landscape. step-by-step technical guide
on how to upload and name these images within the EVE-NG CLI?
Correct placement of files is critical for EVE-NG to recognize the image in the "Add Node" wizard.
Standard Path:
/opt/unetlab/addons/qemu/
Naming Convention:
EVE-NG identifies the node type by the folder name. The syntax generally follows:
[Vendor]-[Product]-[Version]
Example Structure for a FortiGate Firewall:
/opt/unetlab/addons/qemu/
└── fortinet-FortiGate-7.0/
├── hda.qcow2 (The virtual hard drive)
└── config_thumb (Generated by EVE-NG, ignore this)
``
Finding reliable EVE-NG QEMU images often involves a mix of official vendor sources and community repositories. Because EVE-NG does not provide copyrighted images directly
, users typically obtain them from vendor accounts (like Cisco CCO or CML) or community-shared lists that include direct download links and default credentials. Top Resources for EVE-NG Images Official EVE-NG Documentation
: This is the best starting point to see which vendors and versions are supported. It provides specific How-To guides
for preparing images like Cisco ASA, Firepower, and Palo Alto. Hegdepavankumar GitHub Repository
: A frequently cited community resource that offers a collection of free images for personal lab use, along with a QEMU Image Naming Guide to ensure correct file placement. EVE-NG Pro QEMU Images Download List (Scribd) eve-ng qemu images download
: A comprehensive document listing over 50 images across various vendors with direct download links and default credentials. Cisco Modeling Labs (CML)
: If you have a valid CCO account, you can download high-quality, verified images directly from Cisco. How to Install a QEMU Image
Once you have downloaded an image, follow these standard steps to load it into EVE-NG: Linux images - - EVE-NG
To master EVE-NG, understanding how to source and install QEMU images is essential. EVE-NG does not provide copyrighted vendor images for download. Instead, it acts as a hypervisor that runs images you provide yourself. 1. Where to Legally Download Images
Finding reliable images requires knowing where vendors officially host them.
Cisco: The most standard method is purchasing a Cisco Modeling Labs (CML) subscription. This provides access to a "refplat" ISO containing verified QEMU images for IOSv, IOSvL2, ASAv, and more.
Arista: You can download vEOS-lab images for free by registering an account on the Arista Support Portal.
Fortinet: FortiGate VM images (QEMU/KVM) are available through the Fortinet Support site. These often include a 15-day trial period.
Juniper: vJunos-switch and vJunos-router images are frequently available for labbing purposes on the Juniper Downloads page.
Linux: Generic distributions like Ubuntu or Alpine can be downloaded from their official mirrors and then converted or installed within EVE-NG. 2. The Critical Naming Convention
EVE-NG uses a strict naming system to recognize which "node type" an image belongs to. If the folder name is wrong, the node will not appear in your lab.
Structure: /opt/unetlab/addons/qemu/ Vendor/Device Required Folder Prefix Example Folder Name Cisco ASAv asav- asav-9.14.1 Cisco IOSv vios- vios-adventerprisek9-m.15.6 Palo Alto paloalto- paloalto-10.1.0 Windows win- win-10-pro Ubuntu linux- linux-ubuntu-22.04
Note: Inside the folder, the actual virtual disk file must typically be named virtioa.qcow2 or hda.qcow2. 3. Installation Workflow
Once you have downloaded your image (often in .vmdk, .iso, or .qcow2 format), follow these steps: Linux images - - EVE-NG
EVE-NG (Emulated Virtual Environment Next Generation) is the premier platform for network engineers to build high-fidelity labs, but its power is entirely dependent on the QEMU images you import into it.
Because EVE-NG does not come pre-loaded with proprietary vendor software due to licensing restrictions, you must manually source and prepare these images to create a functional lab. This guide covers everything you need to know about acquiring, formatting, and installing QEMU images for EVE-NG. 1. Understanding QEMU Images in EVE-NG
EVE-NG uses QEMU (Quick Emulator) as its back-end virtualization layer. Unlike standard ISO files, EVE-NG requires images to be in the qcow2 format. These images represent the hard drive of the virtual appliance (e.g., a Cisco router, a Palo Alto firewall, or a Linux server). 2. Where to Download EVE-NG QEMU Images
While many third-party sites offer "pre-made" bundles, the most stable and legal way to acquire images is directly from the vendors.
Cisco (CML/VIRL): The best source for legal Cisco images (IOSv, IOS-XE, NX-OS) is a Cisco Modeling Labs (CML) subscription. You can download the .qcow2 files directly from your Cisco account.
Arista: Arista provides vEOS images for free on their website with a guest account.
Juniper: vMX and vQFX images are available via the Juniper support portal (requires a valid support contract).
Fortinet & Palo Alto: These vendors offer KVM/QEMU-compatible trial images on their respective support sites. The Digital Workbench: Understanding QEMU Images in EVE-NG
Open Source: For Linux nodes, pfSense, or VyOS, you can download their standard KVM/QEMU images directly from their project pages. 3. Proper Naming Conventions (Critical)
EVE-NG is highly sensitive to folder and file names. If you do not follow the EVE-NG Naming Convention, the template will not recognize the image.
Folder Names: Must start with a specific prefix followed by a hyphen and the version (e.g., viios-adventerprisek9-m.152-4.M1).
File Names: Inside the folder, the image file must be renamed to a specific name, usually virtioa.qcow2. Common Prefix Examples: Cisco IOSv: viios- Cisco ASAv: asav- Palo Alto: paloalto- Fortinet: fortinet- 4. How to Install a Downloaded QEMU Image
Once you have downloaded your image, follow these steps to integrate it into your lab:
Upload the Image: Use an SCP client (like WinSCP or FileZilla) to upload your image folder to /opt/unetlab/addons/qemu/ on your EVE-NG server.
Rename the File: Ensure the image inside the folder is named correctly (e.g., virtioa.qcow2).
Fix Permissions: This is the most important step. Run the following command via the EVE-NG CLI: /opt/unetlab/wrappers/unl_wrapper -a fixpermissions Use code with caution.
Add the Node: Open your EVE-NG web interface, right-click, select Node, and your newly added image should now be highlighted in blue, indicating it is ready to use. 5. Best Practices for Image Management
Thin Provisioning: Always use .qcow2 format to save disk space on your EVE-NG VM.
Resource Allocation: Check the vendor documentation for the minimum RAM and CPU requirements. Over-allocating resources to a single node can crash your entire EVE-NG instance.
Backup: Keep a library of your original .qcow2 files on an external drive. If you need to reinstall EVE-NG, you can simply re-upload your library. Summary Table: Popular Image Filenames Folder Prefix Required Filename Cisco IOSv viios- virtioa.qcow2 Cisco ASAv asav- virtioa.qcow2 paloalto- virtioa.qcow2 mikrotik- virtioa.qcow2
EVE-NG requires users to independently source QEMU (.qcow2) images for network emulation, as the platform does not provide copyrighted vendor files. Proper installation involves placing images in /opt/unetlab/addons/qemu/ with specific naming conventions, followed by executing the fixpermissions command. For detailed naming conventions and image preparation, refer to EVE-NG Documentation. Qemu image namings - - EVE-NG
Downloading QEMU images for EVE-NG involves a strict process because EVE-NG does not provide copyrighted vendor images. You must legally acquire these images from vendors or use open-source alternatives, then name and upload them following specific conventions. 1. Where to Legally Download Images
Since EVE-NG is just the platform, you need to source the virtual disk files (often in .qcow2, .img, or .iso format) yourself:
Cisco Images: The most legal and common way is through a Cisco Modeling Labs (CML) subscription, which provides access to VIRL/CML images like IOSv, IOSv-L2, and ASAv.
Open-Source Linux: You can download cloud images for Ubuntu or Debian directly using wget within your EVE-NG CLI.
Other Vendors: Many vendors like Palo Alto, Arista, and Juniper provide KVM/QEMU-ready images on their support portals, though these usually require a valid support contract or account. 2. Required Naming Conventions
EVE-NG uses a specific folder and file naming system to recognize images. All QEMU images must be stored in /opt/unetlab/addons/qemu/.
Folder Name: Must start with a predefined prefix followed by a hyphen and your version name (e.g., asav-9.14.1 or linux-ubuntu-24.04).
Filename: The virtual disk inside that folder must be renamed to a standard name, usually virtioa.qcow2 or hda.qcow2. 3. Step-by-Step Upload & Installation
Once you have the image file on your local computer, follow these steps: Linux images - - EVE-NG Finding reliable EVE-NG QEMU images often involves a
To download and use QEMU images in EVE-NG, you must source them legally from vendor websites, as EVE-NG does not provide copyrighted images directly. Most users obtain official images from sources like the Cisco Software Download portal or through a Cisco Modeling Labs (CML) subscription. How to Get and Load Images
Official Vendor Sources: Download images directly from vendors such as Cisco, Juniper, or Palo Alto.
Third-Party Packs: Some providers like CloudMyLab offer "ready-to-go" Linux image packs that simplify the setup process.
Creating Custom Images: You can create your own Linux or Windows images using the EVE-NG How-to Guides. Critical Setup Requirements
Once you have an image, it must follow strict naming conventions to work. Linux images - - EVE-NG
Downloading and setting up QEMU images for EVE-NG involves obtaining vendor-specific software and correctly formatting it within the EVE-NG file system. EVE-NG does not provide copyrighted vendor images (like Cisco, Palo Alto, or Juniper) directly for download. You must acquire these from official vendor sites or authorized repositories. 1. Obtain Your Image
To legally obtain images, you should use official vendor support accounts:
Cisco: Images such as vIOS or ASAv can be downloaded if you have a Cisco Learning Labs or VIRL/CML subscription.
Palo Alto: Download KVM-based images (e.g., .qcow2 files) from the Palo Alto Customer Support Portal.
Linux: You can find "ready-to-go" packs or create your own using Ubuntu ISOs. 2. Prepare the Image Folder
EVE-NG is very strict about folder and file naming. Images must be placed in /opt/unetlab/addons/qemu/.
Folder Naming: Must follow a specific prefix (e.g., asav-, paloalto-, linux-) followed by the version. Example: /opt/unetlab/addons/qemu/asav-9.12.1/
File Naming: The virtual disk file inside the folder must be named correctly, typically virtioa.qcow2 or hda.qcow2. 3. Upload and Deploy
Transfer: Use an SCP/FTP client (like WinSCP or FileZilla) to move the folder from your PC to the /opt/unetlab/addons/qemu/ directory on your EVE-NG server.
Fix Permissions: This is a critical step for the image to show up in the web interface. Run the following command in the EVE-NG CLI: /opt/unetlab/wrappers/unl_wrapper -a fixpermissions Use code with caution. Copied to clipboard
Add Node: Open your EVE-NG web browser, right-click on the canvas, select Node, and your newly added image should now be listed in blue.
For detailed, vendor-specific naming conventions, refer to the official EVE-NG QEMU Image Namings guide. Linux images - - EVE-NG
Even with a successful "eve-ng qemu images download," issues arise.
| Problem | Likely Cause | Solution |
|---------|--------------|----------|
| Node fails to boot (black screen) | Wrong disk naming (virtioa vs hda) | Rename image to hda.qcow2 or virtioa.qcow2 based on image requirements. |
| Permission denied | Fixpermissions not run | Run unl_wrapper -a fixpermissions as root. |
| No QEMU option in node type | Missing KVM acceleration | Ensure nested virtualization is enabled on your hypervisor (ESXi/Workstation/Proxmox). |
| Downloaded image is a .ova or .vmdk | Wrong format | Convert with qemu-img convert. |
| EVE-NG reports "image not found" | Folder name mismatch | Node image name in UI must exactly match the folder name. |
After uploading:
qemu-img check virtioa.qcow2)fixpermissions stepEVE-NG is optimized to use the QEMU Copy-On-Write version 2 (qcow2) file format. This format allows for snapshotting and efficient disk space usage.
The EVE-NG community and development team provide some pre-configured, ready-to-use images: