Pa-vm-kvm-10.1.0.qcow2

Edit the VM's XML via virsh edit pa-vm-10-1-0:

<disk type='file' device='disk'>
  <driver name='qemu' type='qcow2' cache='none' io='native'/>
  ...
</disk>

After the VM boots, you will likely encounter a login prompt or a "Network Configuration" wizard.

Before running a single virsh command, let's break down the nomenclature: pa-vm-kvm-10.1.0.qcow2

| Component | Meaning | Technical Implication | | :--- | :--- | :--- | | pa | Product Code (Likely PowerAdmin, PacketAnalyzer, or Private Appliance) | Indicates a purpose-built OS; likely stripped of unnecessary packages. Expect CLI or Web GUI management. | | vm | Virtual Machine | Confirms this is not a container (Docker/LXC) or bare-metal ISO. It expects hardware virtualization extensions (VT-x/AMD-V). | | kvm | Target Hypervisor | Optimized for KVM. While it may run on Proxmox or oVirt, the virtio drivers are tailored for raw KVM + libvirt. | | 10.1.0 | Version Number | Major.Minor.Patch. Check changelogs for breaking changes between 10.0.x and 10.1.0. | | qcow2 | QEMU Copy-On-Write v2 | Supports snapshots, thin provisioning, and compression. Native to KVM/QEMU. |

Critical Note: Do not attempt to convert this file to VMDK (VMware) or VHDX (Hyper-V) unless absolutely necessary. The kvm tag in the filename suggests the kernel and disk drivers are compiled against virtio, which may fail to boot on non-KVM platforms. Edit the VM's XML via virsh edit pa-vm-10-1-0

Because the filename explicitly says kvm, the kernel should have loaded:

Run inside the VM: lsmod | grep virtio. If empty, the image was built incorrectly. After the VM boots, you will likely encounter

If the "pa" appliance does real-time analysis:

Copy the image to your KVM storage pool (e.g., /var/lib/libvirt/images/):

sudo cp PA-VM-KVM-10.1.0.qcow2 /var/lib/libvirt/images/pavm101.qcow2