Version 5.0

Adapting VMs to run on Google Cloud

To function properly on Google Cloud, migrated VMs require changes to their configuration. These changes are referred to as OS adaptations. Migrate for Compute Engine performs OS adaptations automatically at the end of each replication cycle.

OS adaptations are made to both Linux and Windows VMs. At a high level, these adaptations include changes to:

  • Enable booting on Google Cloud
  • Enable the serial console
  • Configure network settings
  • Install packages required by the VM to enable Google Cloud features and functionality

The specific changes for both Linux and Windows VMs are described below.

Linux adaptations

At the end of each replication cycle for a Linux VM, Migrate for Compute Engine performs OS adaptations on the replicated VM. These adaptations include:

  • Configuring NIC to use DHCP

    • If they exists, remove persistent network udev rules.
  • If they exist, uninstall VMware Tools/open-vm-tools.

  • Set the bootloader to print console logs to serial port 1.

  • Validate virtio drivers:

    • If virtio drivers are not available in the default kernel, choose an existing kernel which is compatible with virtio driver.

    • If virtio drivers are missing from initrd then rebuild initrd with virtio drivers.

  • Add Google Cloud repositories to the repository list. These repositories include:

  • Install the following Google packages:

  • Set systemd.target to multiuser.

  • Where applicable, set fstab to use volume UUIDs.

  • If target instance license is PAYG:

    • Red Hat - Install the google-rhui-client-rhel package specific to the Red Hat version.

    • SLES - Install Google's region service client packages.

Windows adaptations

At the end of each replication cycle for a Windows VM, Migrate for Compute Engine performs OS adaptations on the replicated VM. These adaptations include:

  • Set bootloader to print console logs to serial port 2.

  • Enable RDP.

  • Configure the power scheme:

    • Disable hibernation mode.

    • Set power scheme to balanced.

    • Disable display turn off in power configurations.

  • Disable startup animation.

  • Disable CTRL-ALT-DEL.

  • If they exist, uninstall VMware Tools.

  • Set the time:

    • Change timezone to UTC.

    • Configure NTP.

  • Add access to instance metadata:

    • Add allow access rule to instance metadata server IP address in Windows firewall.

    • Add instance metadata server to hosts file.

  • On first boot:

    • If target instance license is PAYG (default), then register KMS and Windows activation.

    • Configure DHCP settings.