Chapter 5. Migrating virtual machines by using the Red Hat OpenShift web console


Use the MTV user interface to migrate virtual machines (VMs). It is located in the Virtualization section of the Red Hat OpenShift web console.

5.1. The MTV user interface

The Migration Toolkit for Virtualization (MTV) user interface is integrated into the OpenShift web console.

In the left-hand panel, you can choose a page related to a component of the migration progress, for example, Providers for virtualization, or, if you are an administrator, you can choose Overview, which contains information about migrations and lets you configure MTV settings.

Figure 5.1. MTV extension interface

In pages related to components, you can click on the Projects list, which is in the upper-left portion of the page, and see which projects (namespaces) you are allowed to work with.

  • If you are an administrator, you can see all projects.
  • If you are a non-administrator, you can see only the projects that you have permissions to work with.

5.1.1. The MTV Overview page

The Migration Toolkit for Virtualization (MTV) Overview page displays system-wide information about migrations and a list of Settings you can change.

If you have Administrator privileges, you can access the Overview page by clicking Migration Overview in the Red Hat OpenShift web console.

The Overview page has 3 tabs:

  • Overview
  • YAML
  • Metrics

5.1.1.1. Overview tab

The Overview tab lets you see:

  • Operator: The namespace on which the MTV Operator is deployed and the status of the Operator
  • Pods: The name, status, and creation time of each pod that was deployed by the MTV Operator
  • Conditions: Status of the MTV Operator:

    • Failure: Last failure. False indicates no failure since deployment.
    • Running: Whether the Operator is currently running and waiting for the next reconciliation.
    • Successful: Last successful reconciliation.

5.1.1.2. YAML tab

The custom resource ForkliftController that defines the operation of the MTV Operator. You can modify the custom resource from this tab.

5.1.1.3. Metrics tab

The Metrics tab lets you see:

  • Migrations: The number of migrations performed using MTV:

    • Total
    • Running
    • Failed
    • Succeeded
    • Canceled
  • Virtual Machine Migrations: The number of VMs migrated using MTV:

    • Total
    • Running
    • Failed
    • Succeeded
    • Canceled
Note

Since a single migration might involve many virtual machines, the number of migrations performed using MTV might vary significantly from the number of virtual machines that have been migrated using MTV.

  • Chart showing the number of running, failed, and succeeded migrations performed using MTV for each of the last 7 days
  • Chart showing the number of running, failed, and succeeded virtual machine migrations performed using MTV for each of the last 7 days

5.1.2. Configuring MTV settings

If you have Administrator privileges, you can access the Overview page and change the following settings in it:

Expand
Table 5.1. MTV settings
SettingDescriptionDefault value

Max concurrent virtual machine migrations

Varies with provider as follows:

  • For all migrations except OVA or VMware migrations: The maximum number of disks that MTV can transfer simultaneously.
  • For OVA migrations: The maximum number of VMs that MTV can migrate simultaneously.
  • For VMware migrations, the setting has the following meanings::

    • Cold migration:

      • To local OpenShift Virtualization: VMs for each ESXi host that can migrate simultaneously.
      • To remote OpenShift Virtualization: Disks for each ESXi host that can migrate simultaneously.
    • Warm migration: Disks for each ESXi host that can migrate simultaneously.

      See Configuring the controller_max_vm_inflight label for a detailed explanation of this setting.

20

Must gather cleanup after (hours)

The duration for retaining must gather reports before they are automatically deleted.

Disabled

Controller main container CPU limit

The CPU limit allocated to the main controller container.

500 m

Controller main container Memory limit

The memory limit allocated to the main controller container.

800 Mi

Precopy internal (minutes)

The interval at which a new snapshot is requested before initiating a warm migration.

60

Snapshot polling interval (seconds)

The frequency with which the system checks the status of snapshot creation or removal during a warm migration.

10

Procedure

  1. In the Red Hat OpenShift web console, click Migration Overview. The Settings list is on the right-hand side of the page.
  2. In the Settings list, click the Edit icon of the setting you want to change.
  3. Choose a setting from the list.
  4. Click Save.

5.2. Migrating virtual machines using the MTV user interface

Use the MTV user interface to migrate VMs from the following providers:

  • VMware vSphere
  • Red Hat Virtualization (RHV)
  • OpenStack
  • Open Virtual Appliances (OVAs) that were created by VMware vSphere
  • OpenShift Virtualization clusters

For all migrations, you specify the source provider, the destination provider, and the migration plan. The specific procedures vary per provider.

Important

You must ensure that all prerequisites are met.

VMware only: You must have the minimal set of VMware privileges.

VMware only: Creating a VMware Virtual Disk Development Kit (VDDK) image will increase migration speed.

맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat