This is very bare-bones at the moment. It only has minimal documentation and has no tests at all. Nevertheless, this adds a new -o kubevirt mode, so you can import guests into Kubevirt, a system which adds virtualization support to Kubernetes[0]. Example of generated YAML metadata can be found at the end of this cover email. Upstream examples of metadata to compare it to can be found in [1]. I wasn't able to test this yet since my Kubernetes instance died and no one knows how to fix it ... I only bothered to map out the basic hardware and disks, there are many to-dos which will require reading the Kubevirt source code to finish. Generating YAML is an adventure. The format is full of nasty beartraps. What I'm doing is probably mostly safe, but I wouldn't be surprised if there are security holes. Rich. --- # generated by virt-v2v 2.1.1local,libvirt apiVersion: kubevirt.io/v1 kind: VirtualMachineInstance metadata: name: fedora-35 spec: domain: devices: disks: - disk: bus: virtio name: disk-0 resources: requests: memory: 2048Mi cpu: cores: 1 features: acpi: {} apic: {} pae: {} volumes: - hostDisk: path: /var/tmp//fedora-35-sda type: Disk name: disk-0 terminationGracePeriodSeconds: 0 [0] https://github.com/kubevirt/kubevirt [1] https://github.com/kubevirt/kubevirt/tree/main/examples