Custom VM Images¶
CML is bundled with a set of node definitions, such as ASAv and IOSv,
and a single VM image for each node definition. CML permits you to
upload additional VM images (as qcow2
files) for use in your labs. After you
upload a new qcow2
file, you must create an image definition for the new VM
image. For example, you could add an alternate version of ASAv to your
CML server to match the ASAv version used in a real network that you are
modeling in CML. The system would then have two image definitions
associated with the ASAv node definition. When you use an ASAv node in your
CML lab, you could then choose which of the ASAv image definitions to
use for that node.
In addition to uploading alternate versions of existing VM images, the custom image feature permits you to upload third-party VM images, such as a Windows VM, that are not bundled by default. You are responsible for obtaining and properly licensing the third-party VM image. In addition to creating an image definition for the third-party VM image, you may also need to create a new node definition. While we do not provide support for VM images that are not included with the product, if the third-party VM runs on qemu-kvm on CentOS Linux, then CML can generally start the VM and link it to the other nodes in the lab topology. This chapter shows how to load a custom image into the CML server and use it in your labs.