You can now use Hyperdisk Storage Pools with migrating VMs if you need large-scale storage. Hyperdisk Storage Pools help you manage large-scale storage and can optimize costs and performance.
]]>Migrate to Virtual Machines now supports all available versions of AlmaLinux EL 8 and 9.
]]>Generally available: The Basic Input/Output System (BIOS) to Unified Extensible Firmware Interface (UEFI) conversion option is now generally available. Migrate to Virtual Machines lets you convert the OS boot type of a VM instance from BIOS to UEFI. This option is useful when you want to securely boot your VM instance, as secure boot is only supported by UEFI. For more information, see the table in Configure the target for a migrated VM.
]]>Starting with version Migrate Connector 2.7, throttling is supported for a second NIC.
]]>Migrate to Virtual Machines now introduces an expiration time for a migrating VM. A migrating VM is a VM that you create during the migration process to migrate your workloads to Google Cloud.
A migrating VM stays active for 100 days from the time that the VM appears in the VM Migrations tab. After 100 days, the VM is moved to the EXPIRED state and stays in the EXPIRED state for 30 days. If you need more time to complete your migration, you can extend the lifespan of the migrating VM by an additional 100 days. You can only extend the lifespan of a migrating VM two weeks before the VM expires and throughout the expiration period (between 86 to 130 days from the creation of the VM). If you don't extend the lifespan of the VM during this period, the VM expires.
Migrate to Virtual Machines supports importing Arm disk images to Google Cloud. For information on operating systems supporting this feature, see Supported operating systems.
]]>Generally available: Migrate to Virtual Machines support for the Arm64 migration journey is now generally available. This feature lets you migrate Arm virtual machine (VM) instances from AWS and Azure cloud services to Arm VM instances on Compute Engine, and it is supported for the following operating systems:
Experimental: Migrate to Virtual Machines now supports the migration of VM instances running Amazon Linux 2 to Rocky Linux 8 as part of an open access experimental program. In order to migrate a VM running Amazon Linux 2, Migrate to Virtual Machines first converts Amazon Linux 2 to Rocky Linux 8, and then completes the migration.
]]>Preview: Migrate to Virtual Machines lets you migrate Elastic Block Store (EBS) volumes not attached to a VM from AWS to Google Cloud, as part of a preview program. Use this feature when you have detached the disks associated with a VM to archive data and need to migrate these disks to Google cloud.
To participate in the preview, contact us at m2vm-independent-disks-migration@google.com.
]]>As Container Registry is deprecated, Migrate to Virtual Machines is transitioning from Container Registry to Artifact Registry to store images running on Migrate Connector. This transition will be completed by October 15, 2025. For the most part, this change should not affect your usage of Migrate Connector or Migrate to Virtual Machines. However, for some configurations, you might have to add VPC-SC rules to allow Migrate Connector to access Artifact Registry. If you need help using Artifact Registry with Migrate to Virtual Machines, contact the Migrate to Virtual Machines support team.
]]>Experimental: As CentOS Linux 7 has reached end-of-life (EOL) on June 30, 2024, Migrate to Virtual Machines lets you convert CentOS Linux 7 to Rocky Linux 8 as part of your migration.
Note: This product or feature is subject to the Pre-GA Offerings Terms in the General Service Terms section of the Service Specific Terms. Pre-GA products and features are available as is and might have limited support.
]]>On April 30, 2024, the 4.x versions of Migrate for Compute Engine reached end of life, and the product was deprecated on Google Cloud.
To migrate your virtual machines (VMs) to Compute Engine, use Migrate to Virtual Machines.
]]>Generally available: Migrate to Virtual Machines lets you import a machine image from a virtual appliance. You can use machine images to store the configuration, metadata, permissions, and data from one or more disks for a virtual machine (VM) instance running on Compute Engine.
]]>The Migrate Connector, the virtual appliance used to connect VMware sources to Migrate to Virtual Machines, is exposed to a security vulnerability on SSHD (CVE-2024-6387). Migrate Connector version 2.6.2497 has been released to mitigate this issue and is being gradually rolled out. For information, see the GCP-2024-040 security bulletin.
]]>Generally available: Migrate to Virtual Machines lets you import a virtual disk image to a Compute Engine image. If you have virtual disk images with software and configurations that you need, you can save time by importing these virtual disk images to Compute Engine images, and use this image to create virtual machine instances or persistent disks.
]]>Migrate to Virtual Machines now supports importing virtual disk image files in the following formats:
In addition to these formats, Virtual machine disk (VMDK), and raw files compressed as a .tar.gz file are also supported.
]]>Preview: Migrate to Virtual Machines supports the ARM64 migration journey. This feature lets you migrate ARM virtual machine (VM) instances from AWS and Azure cloud services to ARM VM instances on Compute Engine, and it is supported for the following operating systems:
Generally available: You can now use Customer-Managed Encryption Keys (CMEK) in Migrate to Virtual Machines to do the following:
Preview: Migrate to Virtual Machines lets you import a virtual disk image to a Compute Engine image. If you have virtual disk images with software and configurations that you need, you can save time by importing these virtual disk images to Compute Engine images, and use this image to create virtual machine instances or persistent disks.
]]>Generally available: Migrate to Virtual Machines lets you migrate virtual machine (VM) disks to Persistent Disk volumes on Google Cloud. The migrated disks can be attached to a new VM during the migration process, or an existing VM after the migration is complete.
]]>Preview: Migrate to Virtual Machines lets you convert the OS boot type of a VM instance from Basic Input/Output System (BIOS) to Unified Extensible Firmware Interface (UEFI). This option is useful when you want to securely boot your VM instance, as secure boot is only supported by UEFI. For more information, see the table in Configure the target for a migrated VM.
To participate in the preview of this feature, send a request to the email address: m2vm-bios-to-uefi@google.com.
]]>Generally Available: Migrate to Virtual Machines supports migrating virtual machine instances (VMs) to Compute Engine 1st, 2nd, and 3rd generation machine series. For more information, see Support for Compute Engine machine series.
]]>Preview: You can now use Customer-Managed Encryption Keys (CMEK) in Migrate to Virtual Machines to do the following:
]]>Preview: Migrate to Virtual Machines now supports migrating VMs to the C3, H3, and M3 machine types. These machine types support non-volatile memory express (NVMe) and Google Virtual NIC (gVNIC). Before you migrate your VMs to any of these machine types, ensure that source VMs support NVMe and gVNIC. For more information on different machine types that support NVMe and gVNIC, go to the Machine series comparison section, click Choose VM properties to compare, and select Disk interface type and Network interfaces.
]]>Generally Available: Migrate to Virtual Machines from an Azure source lets you migrate VM instances running on Azure to Google Cloud Compute Engine.
]]>Preview: Migrate to Virtual Machines lets you migrate the disks of source virtual machine (VM) instances to Persistent Disk volumes on Google Cloud with the following options:
Preview: Migrate to Virtual Machines from an Azure source is now open to all users. Migrate to Virtual Machines from an Azure source lets you migrate Azure VM instances to Compute Engine.
]]>Preview: Migrate to Virtual Machines supports the migration of VMs running Amazon Linux 2 to Google Cloud as part of a preview program. In order to migrate a VM running Amazon Linux 2, Migrate to Virtual Machines first converts Amazon Linux 2 to Rocky Linux 8 and then completes the migration. To participate in the preview, contact us at m2vm-amazon-linux-migration@google.com.
]]>Preview: Migrate to Virtual Machines lets you migrate disks from source virtual machine (VM) instances to Persistent Disk volumes on Google Cloud. This feature helps you migrate the workload state (VM disks) from a source VM and attach it as a Persistent Disk volume to a VM on Google Cloud, with minimal interruptions to the workload.
]]>Generally Available: Migrate to Virtual Machines lets you migrate your VM instances running on Google Cloud VMware Engine to VM instances running on Compute Engine.
]]>Migrate to Virtual Machines lets you set up throttling on the Migrate Connector to control the rate at which data is transferred from the Migrate Connector. Throttling ensures that the migration process distributes bandwidth evenly between the migration and any other tasks using the network. In this way, the migration can complete successfully without disrupting any other tasks.
]]>