mv jammy-server-cloudimg-amd64.img /opt/unetlab/addons/qemu/ubuntu-22.04/virtioa.qcow2
EVE‑NG expects QEMU images in a specific format:
After placing the image, you must fix permissions: eve-ng qemu images download
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
For Cisco/IOL images – You need to use the
qemu-imgconversion tool to turn.bininto.qcow2. Detailed scripts exist in EVE‑NG documentation. mv jammy-server-cloudimg-amd64
The most stable and legal method is downloading the installation ISOs or virtual appliances directly from the vendor.
You can create your own QEMU image from an ISO: After placing the image, you must fix permissions:
After downloading the ISO, install it manually in EVE-NG (covered below).
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. |