Exporting virtual machines - Virtual machines | Virtualization

Creating a VirtualMachineExport custom resource
Accessing exported virtual machine manifests

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.

You can migrate virtual machines between OpenShift Virtualization clusters by using the Migration Toolkit for Virtualization.

edit

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

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

apiVersion: export.kubevirt.io/v1alpha1
kind: VirtualMachineExport
metadata:
  name: example-export
spec:
  source:
    apiGroup: "kubevirt.io" (1)
    kind: VirtualMachine (2)
    name: example-vm
  ttlDuration: 1h (3)

1	Specify the appropriate API group: `"kubevirt.io"` for `VirtualMachine`. `"snapshot.kubevirt.io"` for `VirtualMachineSnapshot`. `""` for `PersistentVolumeClaim`.
2	Specify `VirtualMachine`, `VirtualMachineSnapshot`, or `PersistentVolumeClaim`.
3	Optional. The default duration is 2 hours.

Create the VirtualMachineExport CR:
```
$ oc create -f example-export.yaml
```

Get the VirtualMachineExport CR:

$ oc get vmexport example-export -o yaml

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

Output example

apiVersion: export.kubevirt.io/v1alpha1
kind: VirtualMachineExport
metadata:
  name: example-export
  namespace: example
spec:
  source:
    apiGroup: ""
    kind: PersistentVolumeClaim
    name: example-pvc
  tokenSecretRef: example-token
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2022-06-21T14:10:09Z"
    reason: podReady
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2022-06-21T14:09:02Z"
    reason: pvcBound
    status: "True"
    type: PVCReady
  links:
    external: (1)
      cert: |-
        -----BEGIN CERTIFICATE-----
        ...
        -----END CERTIFICATE-----
      volumes:
      - formats:
        - format: raw
          url: https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/volumes/example-disk/disk.img
        - format: gzip
          url: https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/volumes/example-disk/disk.img.gz
        name: example-disk
    internal:  (2)
      cert: |-
        -----BEGIN CERTIFICATE-----
        ...
        -----END CERTIFICATE-----
      volumes:
      - formats:
        - format: raw
          url: https://virt-export-example-export.example.svc/volumes/example-disk/disk.img
        - format: gzip
          url: https://virt-export-example-export.example.svc/volumes/example-disk/disk.img.gz
        name: example-disk
  phase: Ready
  serviceName: virt-export-example-export

1	External links are accessible from outside the cluster by using an `Ingress` or `Route`.
2	Internal links are only valid inside the cluster.

edit

Accessing exported virtual machine manifests

After you export a virtual machine (VM) or snapshot, you can get the VirtualMachine manifest and related information from the export server.

Prerequisites

You exported a virtual machine or VM snapshot by creating a VirtualMachineExport custom resource (CR).

VirtualMachineExport objects that have the spec.source.kind: PersistentVolumeClaim parameter do not generate virtual machine manifests.

Procedure

To access the manifests, you must first copy the certificates from the source cluster to the target cluster.
1. Log in to the source cluster.
2. Save the certificates to the cacert.crt file by running the following command:
  $ oc get vmexport <export_name> -o jsonpath={.status.links.external.cert} > cacert.crt (1)
  1 Replace <export_name> with the metadata.name value from the VirtualMachineExport object.
3. Copy the cacert.crt file to the target cluster.
Decode the token in the source cluster and save it to the token_decode file by running the following command:
```
$ oc get secret export-token-<export_name> -o jsonpath={.data.token} | base64 --decode > token_decode (1)
```
1 Replace <export_name> with the metadata.name value from the VirtualMachineExport object.
Copy the token_decode file to the target cluster.
Get the VirtualMachineExport custom resource by running the following command:
```
$ oc get vmexport <export_name> -o yaml
```

Review the status.links stanza, which is divided into external and internal sections. Note the manifests.url fields within each section:

Example output

apiVersion: export.kubevirt.io/v1alpha1
kind: VirtualMachineExport
metadata:
  name: example-export
spec:
  source:
    apiGroup: "kubevirt.io"
    kind: VirtualMachine
    name: example-vm
  tokenSecretRef: example-token
status:
#...
  links:
    external:
#...
      manifests:
      - type: all
        url: https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/external/manifests/all (1)
      - type: auth-header-secret
        url: https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/external/manifests/secret (2)
    internal:
#...
      manifests:
      - type: all
        url: https://virt-export-export-pvc.default.svc/internal/manifests/all (3)
      - type: auth-header-secret
        url: https://virt-export-export-pvc.default.svc/internal/manifests/secret
  phase: Ready
  serviceName: virt-export-example-export

1	Contains the `VirtualMachine` manifest, `DataVolume` manifest, if present, and a `ConfigMap` manifest that contains the public certificate for the external URL’s ingress or route.
2	Contains a secret containing a header that is compatible with Containerized Data Importer (CDI). The header contains a text version of the export token.
3	Contains the `VirtualMachine` manifest, `DataVolume` manifest, if present, and a `ConfigMap` manifest that contains the certificate for the internal URL’s export server.

Get the Secret manifest by running the following command:

$ curl --cacert cacert.crt <secret_manifest_url> -H \ (1)
"x-kubevirt-export-token:token_decode" -H \ (2)
"Accept:application/yaml"

1	Replace `<secret_manifest_url>` with an `auth-header-secret` URL from the `VirtualMachineExport` YAML output.
2	Reference the `token_decode` file that you created earlier.

For example:

$ curl --cacert cacert.crt https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/external/manifests/secret -H "x-kubevirt-export-token:token_decode" -H "Accept:application/yaml"

Get the manifests of type: all, such as the ConfigMap and VirtualMachine manifests, by running the following command:

$ curl --cacert cacert.crt <all_manifest_url> -H \ (1)
"x-kubevirt-export-token:token_decode" -H \ (2)
"Accept:application/yaml"

1	Replace `<all_manifest_url>` with a URL from the `VirtualMachineExport` YAML output.
2	Reference the `token_decode` file that you created earlier.

For example:

$ curl --cacert cacert.crt https://vmexport-proxy.test.net/api/export.kubevirt.io/v1alpha1/namespaces/example/virtualmachineexports/example-export/external/manifests/all -H "x-kubevirt-export-token:token_decode" -H "Accept:application/yaml"

Next steps

You can now create the ConfigMap and VirtualMachine objects on the target cluster by using the exported manifests.