Create and Manage VM Images

VM Images live beneath an Arsenal Template family and act as versioned reusable workload-disk baselines. Conceptually, this is closer to the container image/container model than to repeatedly hand-building virtual machines: the reusable image is kept as the baseline, while a deployed VM receives its own writable runtime state. Create a new image version when the baseline disk changes or when a new reusable revision is required.

Choose the Arsenal Template family, define the image version, and set the disk type, size, and format. Arsenal history then provides the revision trail for that image so deployments can be tied back to an exact reusable baseline.

The image version is present beneath the correct template family with the intended disk bus, format, size, and generated filename.