Version 4.11

Starting, stopping, and rebooting VMs

You can use tools provided by Migrate for Compute Engine to manage migrating VMs on Compute Engine. You can start, stop, or reboot VMs on Compute Engine. You can perform these actions using the following tools:

  • Migrate for Compute Engine Manager
  • vCenter (for VMs migrating from vSphere)
  • PowerShell

You can also use the Migrate for Compute Engine Manager and vCenter to move a migrating VM back to run on vSphere. For more information, see Moving a VM back on-premises.

Starting a VM on Compute Engine

Using the Migrate for Compute Engine Manager

You can start a VM if its Power State is currently Off.

  1. Log in to your Migrate for Compute Engine Manager.
  2. Click Migration Waves.
  3. When prompted for a username and password, use apiuser as the username.
  4. Select one of the following, depending on whether your VM is included in a wave:
    • For a VM in a wave, click the monitor icon.
    • For a VM not in a wave, click Unassigned VMs.
  5. Select the VM and click Start.

    Screenshot of starting a VM in a wave (click to enlarge)
    Screenshot of **Migration Waves** tab (click to enlarge)

Using vCenter

  1. In vSphere vCenter, select the virtual machine.
  2. Right-click the VM and select Migrate for Google Compute Engine Operations > Power On.

Using PowerShell (supported for vSphere VMs)

  1. In PowerShell, connect to the Migrate for Compute Engine Manager by running Connect-VelostrataManager.
  2. When prompted, enter details for the server, username (apiuser) and your password.
  3. To power on a VM, run:

    Start-VelosVm [-Id] 

    where VM-IDs is an array of vSphere VM IDs.

Rebooting a VM on Compute Engine

You can reboot a VM if its Power State is currently On.

Using the Migrate for Compute Engine Manager

  1. Log in to your Migrate for Compute Engine Manager.
  2. Click the Migration Waves tab.
  3. Select one of the following, depending on whether your VM is included in a wave:
    • For a VM in a wave, click the monitor icon.
    • For a VM not in a wave, click Unassigned VMs.
  4. Select the VM and click Reboot.

When you reboot a VM in the cloud and the instance doesn't pass health checks, Migrate for Compute Engine attempts to heal the VM automatically.

Using vCenter

  1. In the vSphere vCenter, select the virtual machine.
  2. Right-click the VM and select Migrate for Google Compute Engine Operations > Restart.

Using PowerShell (supported for vSphere VMs)

  1. In PowerShell, connect to the Migrate for Compute Engine Manager by running Connect-VelostrataManager.

  2. When prompted, enter details for the server, username (apiuser), and password.

  3. To restart a VM, run:

    Restart-VelosVm [-Id] VM-IDs

    where VM-IDs is an array of vSphere VM IDs.

Stopping a VM on Compute Engine

You can stop a VM if its Power State is currently On.

Using the Migrate for Compute Engine Manager

  1. Log in to your Migrate for Compute Engine Manager.
  2. Click the Migration Waves tab.
  3. Select one of the following, depending on whether your VM is included in a wave:
    • For a VM in a wave, click the monitor icon.
    • For a VM not in a wave, click Unassigned VMs.
  4. Select the VM and click Stop.

Using vCenter

  1. In vSphere vCenter, select the virtual machine.
  2. Right-click the VM and select Migrate for Google Compute Engine Operations > Shutdown.

Using PowerShell (supported for vSphere VMs)

  1. In PowerShell, connect to the Migrate for Compute Engine Manager by running Connect-VelostrataManager.
  2. When prompted, enter details for the server, username (apiuser), and password.
  3. To shut down a VM, run:

    Stop-VelosVm [-Id] VM-IDs

    where VM-IDs is an array of vSphere VM IDs.