Skip to main content

Virtual Machine Orchestrator

The following are common scenarios that you may encounter when using Virtual Machine Orchestrator (VMO).

Scenario - Virtual Machines (VM) Stuck in a Migration Loop​

Clusters with the VMO pack may experience VMs getting stuck in a continuous migration loop, as indicated by a Migrating or Migration VM status. Use the following steps to troubleshoot and resolve the issue.

Debug Steps​

  1. Log in to Palette and click Clusters from the left Main Menu.

  2. Select your cluster and click on the Profile tab.

  3. Select the VMO pack layer and click Values under the Pack Details section.

  4. Comment out the following lines under the kubevirtResource section and click Save.

    workloads: {}
    # workloadsUpdateStrategy:
    #     workloadUpdateMethods:
    #     - LiveMigrate

  5. The KubeVirt custom resource may fail to update after changing the VMO pack values in the Palette UI. To ensure the changes take effect, follow the Access Cluster with CLI guide to connect to your host cluster using the kubectl CLI.

  6. In your terminal, issue the following command to edit the KubeVirt custom resource.

    kubectl edit kubevirt --namespace kubevirt

  7. Comment out the following lines under the spec block and save the file.

    # workloadUpdateStrategy:
    #   workloadUpdateMethods:
    #   - LiveMigrate

  8. Within a few minutes, the VMs will stop being stuck in the continuous migration loop.

    warning

    Step 4 affects the CPU Hotplug functionality. If your cluster has CPU Hotplug enabled, you will need to manually restart your VM each time you add a virtual CPU for the changes to take effect.