: The node will now be available in the QEMU section of the node types. Ensure you are using EVE-NG version 5.0.1 or newer.
Deploying the .qcow2 image via the Linux CLI using virt-install provides the highest level of granular control. Step 1: Prepare the Image Directory
When transitioning this image from a lab environment to a production virtual data center, ensure the following steps are met: cat9kv-prd-17.12.01prd9.qcow2
Understanding the naming convention of a Cisco virtual image ensures compatibility across target environments. Let’s break down cat9kv-prd-17.12.01prd9.qcow2 :
Cisco does officially release pre-release images like this to the public. If you obtained this file: : The node will now be available in
: The specific IOS XE release version (17.12.1 Amsterdam). This release is part of Cisco’s extended support lifecycle, focusing on stability, advanced routing features, and deep SD-WAN integrations.
: The qcow2 image expands dynamically, but ensure at least 8 GB of physical storage is available for log files and core dumps. Step 1: Prepare the Image Directory When transitioning
Will you be running this in or Controller (SD-WAN) mode?
mv /opt/unetlab/addons/qemu/c8000v-17.12.01prd9/cat9kv-prd-17.12.01prd9.qcow2 /opt/unetlab/addons/qemu/c8000v-17.12.01prd9/virtioa.qcow2 Use code with caution.
Move the downloaded image to your KVM storage pool directory: