In certain situations, you need to move your workload from an existing virtual machine instance (VM) to a new VM. Examples include needing to upgrade the operating system to a new release, or wanting to switch from the x86 architecture to the Arm architecture. In these cases, you must create a new VM and move your workload to the new VM.
Preparing to migrate to an Arm VM
If you want to migrate your VM to use the Arm CPU platform, for example, from
t2a-standard-32, complete the following steps.
- Check that the operating system version for your current VM is supported for
T2A VMs. View the operating system details
documentation for your operating system for more information.
- If the Arm instance requires a newer version of the operating system, verify that your applications are compatible with the newer version.
- If an Arm image is not available for your current operating system, choose a new operating system to run your applications on and verify that your applications are compatible with the new operating system.
- Review the Tau T2A machine series overview to see what features are available. The T2A machine series might not support the same network or storage features that you use with your current VM.
- The T2A machine series might not support the same interfaces as your current machine type. Review the supported interfaces for the operating system to see what network and storage interfaces are supported. Make sure your applications support the supported interfaces.
- Review the available regions and zones for the T2A machine series. The T2A machine series might not be available in all the regions as your current VM. Adjust your deployment, availability, and disaster recovery plans as needed.
Moving your workload from an existing VM to a new VM
To move your workload to a new VM, you create new VM, then move your workload to the new VM. You might do this when you need to upgrade to the latest operating system version, or switch to a VM running on the Arm platform.
- Update your applications and programs, if necessary, to support the gVNIC network interface, the NVMe storage interface, or the new operating system version.
- If your existing VM uses local SSD disks that contain data you want to keep, move the contents of those disks to a persistent disk.
Create a new VM according to your specifications.
- Configure the necessary users, drivers, packages, and file directories on the new VM to support your workload.
- Update your applications and programs to use the gVNIC network interface or the NVMe storage interface, if necessary.
- Move persistent disks from the old VM to the new VM. You can do this by detaching the persistent disk from the old VM and adding it to the new VM. You can alternatively [transfer files](/compute/docs/instances/transfer-files) from one VM to the other.
- Install your modified applications and programs on the new VM. Recompile the programs on the new OS, if required.
- Reassign any static IP addresses associated with the original VM to the new Arm VM.
- Optionally, move the saved data from persistent disks back to a local SSD.
If you encounter issues when moving your workload from an x86 VM to an Arm VM, contact your Technical Account Manager (TAM) or the Google Professional Services Organization (PSO) for assistance.
- Read the troubleshooting tips.
- Learn more about T2A machine series.
- Learn more about the migration process.