Eve-ng Huawei Images Download Page

Many users fail because they grab a random .qcow2 file and wonder why the node won’t boot. Here is what you actually need:

EVE-NG community and professional editions support several Huawei virtual images. Below are the most common ones:

| Device Type | Image File Name (Example) | Typical Use Case | | :--- | :--- | :--- | | Huawei AR1000V | huawei-ar1000v-5.170.img | Enterprise router, MPLS, VPN, firewall features | | Huawei CX (CloudEngine) | hda-cx.img | Data center switch, VXLAN, EVPN | | Huawei NE (NetEngine) | ne5000e.img | Service provider router | | Huawei USG6000v | usg6000v.img | Next-generation firewall | eve-ng huawei images download

Note: Filenames and versions may vary. Always use the image format required by your EVE-NG version (usually .img or .qcow2).

  • Resize QCOW2 if necessary (only when you know what you’re doing).
  • Create the EVE-NG node directory:
  • Place the QCOW2 file and rename per EVE-NG expectations (often hda.qcow2 or huawei.qcow2).
  • Fix permissions and ownership: 
    /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
  • Edit node metadata (if required) so EVE-NG recognizes the node type and console settings.
  • Import in the EVE-NG web UI by adding the node to a lab topology and selecting the node image.

    • Not all Huawei images work well in EVE-NG. Here is the "Sweet Spot" list that runs flawlessly without eating up all your RAM: Many users fail because they grab a random

    Huawei network operating systems are proprietary software. You cannot legally download the full .iso or .img files from a random GitHub repo. To stay compliant, you need a valid Huawei support account (usually tied to a company or an official Huawei Academy) to download images from the official Huawei enterprise portal.

    For lab/practice purposes, many users rely on pre-packaged QEMU images shared within the community, but you should always try to source your software legally. Note: Filenames and versions may vary

    The official EVE-NG Forum has a dedicated “Image Requests” section.