Because it uses qcow2, you can leverage QEMU's snapshot feature. Before attempting a dangerous configuration change or a security update, take a snapshot:
virsh snapshot-create-as panoramakvm1004qcow2 --name "pre-update"
If something breaks, revert in seconds. Raw disk formats cannot do this natively.
Do not manually create a disk; use the downloaded file as your backing image. (Use --import flag for existing disk images). panoramakvm1004qcow2
virt-install \
--name panorama-vm \
--memory 4096 \
--vcpus 2 \
--disk path=/var/lib/libvirt/images/panoramakvm1004qcow2.qcow2,format=qcow2 \
--os-variant detect=on \
--import \
--network bridge=virbr0 \
--graphics vnc
Pro-tip: To use it as a "golden image" for multiple VMs, create an overlay (backing file):
qemu-img create -f qcow2 -b panoramakvm1004qcow2.qcow2 my-clone-vm.qcow2
This allows 10 VMs to share the same 10 GB base image, consuming only the differences per VM. Check:
Putting these together: panoramakvm1004qcow2 is very likely a QEMU/KVM disk image (qcow2) for a VM related to a "panorama" project or product, version/build 1004.
qcow2 images benefit massively from huge pages, reducing TLB misses.
On the host: Mount read-only:
echo 2048 > /proc/sys/vm/nr_hugepages
In the VM XML:
<memoryBacking>
<hugepages/>
</memoryBacking>