Exporting virtual machines

You can export a virtual machine (VM) and its associated disks in order to import a VM into another cluster or to analyze the volume for forensic purposes.

You create a VirtualMachineExport custom resource (CR) by using the command line interface.

Alternatively, you can use the virtctl vmexport command to create a VirtualMachineExport CR and to download exported volumes.

Creating a VirtualMachineExport custom resource

You can create a VirtualMachineExport custom resource (CR) to export the following objects:

  • Virtual machine (VM): Exports the persistent volume claims (PVCs) of a specified VM.

  • VM snapshot: Exports PVCs contained in a VirtualMachineSnapshot CR.

  • PVC: Exports a PVC. If the PVC is used by another pod, such as the virt-launcher pod, the export remains in a Pending state until the PVC is no longer in use.

The VirtualMachineExport CR creates internal and external links for the exported volumes. Internal links are valid within the cluster. External links can be accessed by using an Ingress or Route.

The export server supports the following file formats:

  • raw: Raw disk image file.

  • gzip: Compressed disk image file.

  • dir: PVC directory and files.

  • tar.gz: Compressed PVC file.

Prerequisites

  • The VM must be shut down for a VM export.

Procedure

  1. Create a VirtualMachineExport manifest to export a volume from a VirtualMachine, VirtualMachineSnapshot, or PersistentVolumeClaim CR according to the following example and save it as example-export.yaml:

    VirtualMachineExport example

    1. apiVersion: export.kubevirt.io/v1alpha1
    2. kind: VirtualMachineExport
    3. metadata:
    4.   name: example-export
    5. spec:
    6.   source:
    7.     apiGroup: "kubevirt.io" (1)
    8.     kind: VirtualMachine (2)
    9.     name: example-vm
    10.   ttlDuration: 1h (3)
    1Specify the appropriate API group:

    • “kubevirt.io” for VirtualMachine.

    • “snapshot.kubevirt.io” for VirtualMachineSnapshot.

    • “” for PersistentVolumeClaim.

    2Specify VirtualMachine, VirtualMachineSnapshot, or PersistentVolumeClaim.
    3Optional. The default duration is 2 hours.

  2. Create the VirtualMachineExport CR:

    1. $ oc create -f example-export.yaml

  3. Get the VirtualMachineExport CR:

    1. $ oc get vmexport example-export -o yaml

    The internal and external links for the exported volumes are displayed in the status stanza:

    Output example

    1. apiVersion: export.kubevirt.io/v1alpha1
    2. kind: VirtualMachineExport
    3. metadata:
    4.   name: example-export
    5.   namespace: example
    6. spec:
    7.   source:
    8.     apiGroup: ""
    9.     kind: PersistentVolumeClaim
    10.     name: example-pvc
    11.   tokenSecretRef: example-token
    12. status:
    13.   conditions:
    14.   - lastProbeTime: null
    15.     lastTransitionTime: "2022-06-21T14:10:09Z"
    16.     reason: podReady
    17.     status: "True"
    18.     type: Ready
    19.   - lastProbeTime: null
    20.     lastTransitionTime: "2022-06-21T14:09:02Z"
    21.     reason: pvcBound
    22.     status: "True"
    23.     type: PVCReady
    24.   links:
    25.     external: (1)
    26.       cert: |-
    27.         -----BEGIN CERTIFICATE-----
    28.         ...
    29.         -----END CERTIFICATE-----
    30.       volumes:
    31.       - formats:
    32.         - format: raw
    33.           url: https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/volumes/example-disk/disk.img
    34.         - format: gzip
    35.           url: https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/volumes/example-disk/disk.img.gz
    36.         name: example-disk
    37.     internal:  (2)
    38.       cert: |-
    39.         -----BEGIN CERTIFICATE-----
    40.         ...
    41.         -----END CERTIFICATE-----
    42.       volumes:
    43.       - formats:
    44.         - format: raw
    45.           url: https://virt-export-example-export.example.svc/volumes/example-disk/disk.img
    46.         - format: gzip
    47.           url: https://virt-export-example-export.example.svc/volumes/example-disk/disk.img.gz
    48.         name: example-disk
    49.   phase: Ready
    50.   serviceName: virt-export-example-export
    1External links are accessible from outside the cluster by using an Ingress or Route.
    2Internal links are only valid inside the cluster.