Offline assessment rules

The mcdc CLI examines the data collected from a physical or virtual machine (VM) instance, applies a set of rules, and creates a report containing the assessment results. The rules and descriptions are listed in the following table.

Rule ID Journey OS Category Tested Feature Severity Summary Recommendation Status
A1N-FIT-1 Containerize | GKE and GDC N/A Internal Available VM data 6 No guest level data for this VM. Please collect guest level data and re-run the assessment. implemented
A1L-APP-2 Containerize | GKE and GDC Linux Application Running processes and services 2 Suspected database process found. Consider migrating to Cloud SQL. implemented
A1L-APP-3 Containerize | GKE and GDC Linux Application Running processes 1 Docker process found. If the workload already runs in a container, consider running it directly on GKE/Anthos or using Migrate to Virtual Machines to migrate it to Compute Engine. implemented
A1L-APP-5 Containerize | GKE and GDC Linux Application Disk Usage 1 The workload might contain data and require you to use image+data migration, please prepare the list of data folders ahead of time. Please prepare the list of data folders ahead of time. implemented
A1L-HRD-3 Containerize | GKE and GDC Linux Hardware CPU Architecture 5 ARM VMs are not supported. implemented
A1L-NET-1 Containerize | GKE and GDC Linux Networking Bound IP addresses 2 Found a listener on non 0.0.0.0 IP address. Change application behavior to listen on a local address. implemented
A1L-NET-2 Containerize | GKE and GDC Linux Networking Bound IP addresses 2 Found listeners on multiple IP addresses. Change application behavior to listen on a single IP address. implemented
A1L-NET-3 Containerize | GKE and GDC Linux Networking Bound IP ports 3 Found multiple listeners on the same IP port. Change application behavior to have a single listener on any port. implemented
A1L-NET-4 Containerize | GKE and GDC Linux Networking Network interface cards (NICs) 3 Found multiple NICs in use. Change application behavior to listen on a single IP address. implemented
A1L-NET-5 Containerize | GKE and GDC Linux Networking Static hosts configuration 1 Found Static host configuration. See Adding entries to Pod /etc/hosts with HostAliases in documentation for information on modifying your static hosts. implemented
A1L-STO-1 Containerize | GKE and GDC Linux Storage Network mounts 1 Found network mounts. See Mounting External Volumes in documentation for more on how to attach NFS/CIFS volumes to deployment YAML. implemented
A1L-STO-2 Containerize | GKE and GDC Linux Storage Mounted file systems 3 Found incompatible mounted file system. Consider removing the mounted file system or migrating the data. implemented
A1L-STO-3 Containerize | GKE and GDC Linux Storage Mounted file systems 2 Found mounted file system with Security Enhanced Linux (SELinux) enforced. Disable SELinux or manually apply an apparmor profile before migrating. implemented
A1L-STO-5 Containerize | GKE and GDC Linux Storage Exported Network File Systems (NFS) 3 Found an exported NFS. To continue exporting the NFS, ensure there is no internal dependency on the detected NFS Server. If there is a dependency, leave the original VM in place after migration. implemented
A1L-STO-7 Containerize | GKE and GDC Linux Storage Open files 5 Found an open block device. Attempt closing the open block device. implemented
A2L-APP-2 Containerize | GKE Autopilot Linux Application Running processes and services 2 Suspected database process found. For optimal compatibility, migrate database services to Cloud SQL. implemented
A2L-APP-3 Containerize | GKE Autopilot Linux Application Running processes 1 Docker process found. Instead of migrating the VM, consider running its containers on GKE or Anthos. Alternatively, you can use Migrate to VMs to run the VM as-is on Compute Engine. implemented
A2L-APP-5 Containerize | GKE Autopilot Linux Application CPU count 4 CPU count exceeds max Pod vCPU count. Re-allocate CPU resources to reduce the resulting number of CPUs used per pod in the migration target. Learn about resource ranges here: https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#allowable_resource_ranges. implemented
A2L-APP-6 Containerize | GKE Autopilot Linux Application Memory size 4 Memory size exceeds max Pod memory size. Re-allocate CPU resources to reduce the resulting amount of memory used per pod in the migration target. Learn about resource ranges here: https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#allowable_resource_ranges. implemented
A2L-APP-7 Containerize | GKE Autopilot Linux Application Disk Usage 1 The workload might contain data and require you to use image+data migration, please prepare the list of data folders ahead of time. When migrating data as well as images, prepare a list of your data folders before migration. implemented
A2L-FIT-1 Containerize | GKE Autopilot Linux Internal Available VM data 6 No guest level data for this VM. Please collect guest level data and re-run the assessment. implemented
A2L-HRD-3 Containerize | GKE Autopilot Linux Hardware CPU Architecture 5 ARM VMs are not supported. implemented
A2L-NET-1 Containerize | GKE Autopilot Linux Networking Bound IP addresses 2 Found a listener on non 0.0.0.0 IP address. The application listens on an IP address other than 0.0.0.0. Modify the application to listen on a local IP address. implemented
A2L-NET-2 Containerize | GKE Autopilot Linux Networking Bound IP addresses 2 Found listeners on multiple IP addresses. There are multiple listeners on the same port. Modify the application to listen on a single IP address. implemented
A2L-NET-3 Containerize | GKE Autopilot Linux Networking Bound IP ports 3 Found multiple listeners on the same IP port. The application listens on multiple IP addresses. Modify the application to have only one listener per port. implemented
A2L-NET-4 Containerize | GKE Autopilot Linux Networking Network interface cards (NICs) 3 Found multiple NICs in use. The application uses multiple network interface cards (NICs). Modify the application to listen on a single IP address. implemented
A2L-NET-5 Containerize | GKE Autopilot Linux Networking Static hosts configuration 1 Found Static host configuration. Replace your static host configurations with HostAliases entries in the pod's /etc/hosts file. Learn about host aliases here: https://kubernetes.io/docs/tasks/network/customize-hosts-file-for-pods. implemented
A2L-STO-1 Containerize | GKE Autopilot Linux Storage Network mounts 1 Found network mounts. Existing network mounts are not supported. Attach your NFS and CIFS volumes using YAML. See this article for details: https://cloud.google.com/migrate/containers/docs/mounting-external-volumes. implemented
A2L-STO-2 Containerize | GKE Autopilot Linux Storage Mounted file systems 3 Found incompatible mounted file system. Consider removing the mounted file system or migrating the data. implemented
A2L-STO-3 Containerize | GKE Autopilot Linux Storage Mounted file systems 2 Found mounted file system with Security Enhanced Linux (SELinux) enforced. Disable Security Enhanced Linux (SELinux), or manually apply an AppArmor profile. implemented
A2L-STO-5 Containerize | GKE Autopilot Linux Storage Exported Network File Systems (NFS) 3 Found an exported NFS. To continue exporting the NFS, ensure there is no internal dependency on the detected NFS Server. If there is a dependency, leave the original VM in place after migration. implemented
A2L-STO-7 Containerize | GKE Autopilot Linux Storage Open files 5 Found an open block device. Close all open block devices. implemented
A3L-APP-2 Containerize | Cloud Run Linux Application Running processes and services 5 Suspected database process found. Consider migrating to Cloud SQL. implemented
A3L-APP-3 Containerize | Cloud Run Linux Application Running processes 1 Docker process found. Consider using Migrate to VMs or running the containers directly on GKE/Anthos. implemented
A3L-APP-5 Containerize | Cloud Run Linux Application CPU count 4 CPU count exceeds max CPU count. Consider re-allocating CPU resources. See: https://cloud.google.com/run/quotas. implemented
A3L-APP-6 Containerize | Cloud Run Linux Application Memory size 4 Memory size exceeds max memory size. Consider re-allocating memory resources. See: https://cloud.google.com/run/quotas. implemented
A3L-APP-7 Containerize | Cloud Run Linux Application Disk Usage 1 The workload might contain data and require you to use image+data migration, please prepare the list of data folders ahead of time. Please prepare the list of data folders ahead of time. implemented
A3L-FIT-1 Containerize | Cloud Run Linux Internal Available VM data 6 No guest level data for this VM. Please collect guest level data and re-run the assessment. implemented
A3L-HRD-3 Containerize | Cloud Run Linux Hardware CPU Architecture 5 ARM VMs are not supported. implemented
A3L-NET-1 Containerize | Cloud Run Linux Networking Bound IP addresses 2 Found a listener on non 0.0.0.0 IP address. Change application behavior to listen on a local address. implemented
A3L-NET-2 Containerize | Cloud Run Linux Networking Bound IP addresses 2 Found listeners on multiple IP addresses. Change application behavior to listen on a single IP address. implemented
A3L-NET-3 Containerize | Cloud Run Linux Networking Bound IP ports 3 Found multiple listeners on the same IP port. Change application behavior to have a single listener on any port. implemented
A3L-NET-4 Containerize | Cloud Run Linux Networking Network interface cards (NICs) 3 Found multiple NICs in use. Change application behavior to listen on a single IP address. implemented
A3L-NET-5 Containerize | Cloud Run Linux Networking Static hosts configuration 1 Found Static host configuration. See Adding entries to Pod /etc/hosts with HostAliases in documentation for information on modifying your static hosts. implemented
A3L-STO-1 Containerize | Cloud Run Linux Storage Network mounts 1 Found network mounts. See Mounting External Volumes in documentation for more on how to attach NFS/CIFS volumes to deployment YAML. implemented
A3L-STO-2 Containerize | Cloud Run Linux Storage Mounted file systems 3 Found incompatible mounted file system. Consider removing the mounted file system or migrating the data. implemented
A3L-STO-3 Containerize | Cloud Run Linux Storage Mounted file systems 2 Found mounted file system with Security Enhanced Linux (SELinux) enforced. Disable SELinux or manually apply an apparmor profile before migrating. implemented
A3L-STO-5 Containerize | Cloud Run Linux Storage Exported Network File Systems (NFS) 3 Found an exported NFS. To continue exporting the NFS, ensure there is no internal dependency on the detected NFS Server. If there is a dependency, leave the original VM in place after migration. implemented
A3L-STO-7 Containerize | Cloud Run Linux Storage Open files 5 Found an open block device. Attempt closing the open block device. implemented
A5N-APP-1 Containerize | Tomcat App Container N/A Application Tomcat version 3 Found unsupported Tomcat version. Supported Tomcat versions are 8.5 - 10.0. Unsupported Tomcat server version detected. Migration is possible but some features may not work. implemented
A5N-APP-2 Containerize | Tomcat App Container N/A Application Tomcat Clustering 2 Clustering configuration detected in Tomcat server config. Consider changing to a Kubernetes supported clustering implementation or remove it from server.xml. implemented
A5N-APP-3 Containerize | Tomcat App Container N/A Application Tomcat Proxy configuration 2 Reverse proxy configuration detected in Tomcat server config. The Tomcat server is configured to run behind a reverse proxy. Consider removing or adjusting the proxy configuration in server.xml. implemented
A5N-APP-4 Containerize | Tomcat App Container N/A Application Java Proxy configuration 2 Java proxy configuration detected in Tomcat server's JVM args. Consider updating proxy configuration in JVM args to use the correct proxy or remove it if a proxy is no longer needed. implemented
A5N-APP-5 Containerize | Tomcat App Container N/A Application JMX configuration 2 JMX configuration detected in Tomcat server's JVM args. JMX configuration detected. Please note that some features of JMX might not work as expected on Kubernetes. implemented
A5N-APP-6 Containerize | Tomcat App Container N/A Application Java version 3 Java version 8 and higher is supported. Unsupported Java version detected. Migration is possible but some features may not work. implemented
A5N-APP-7 Containerize | Tomcat App Container N/A Application Tomcat configuration 5 server.xml configuration file is missing or invalid. implemented
A5N-APP-8 Containerize | Tomcat App Container N/A Application Tomcat jvmRoute 2 jvmRoute detected in Tomcat server config. Consider removing jvmRoute configuration from server.xml. implemented
A5N-APP-9 Containerize | Tomcat App Container N/A Application Java Endorsed Dirs 2 Java endorsed dirs configuration detected in Tomcat server's JVM args. Consider adding Java endorsed paths to the additionalFiles section in the migration plan and include ENV CATALINA_OPTS="${CATALINA_OPTS} -Djava.endorsed.dirs=..." in the Dockerfile. implemented
A5N-APP-10 Containerize | Tomcat App Container N/A Application Database connections 2 Found database connections. Check if Tomcat is using an external database. If so, make sure the deployment cluster has access to it. implemented
A5N-APP-11 Containerize | Tomcat App Container N/A Application Web server connections 2 Found web server connections. Check if Tomcat is using an external web server. If so, make sure the deployment cluster has access to it. implemented
A5N-STO-1 Containerize | Tomcat App Container N/A Storage Network mounts 2 Found network mounts. Check if Tomcat uses NFS mounts. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A5N-STO-2 Containerize | Tomcat App Container N/A Storage Exported Network File Systems (NFS) 3 Found an exported NFS. Make sure to leave the current VM in place once the tomcat server is deleted. Check if Tomcat uses the parts of the filesystem exported as NFS servers. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A6N-APP-1 Containerize | Windows IIS App Container N/A Application Operating system 5 Windows version not supported. Consider upgrading Windows. implemented
A6N-APP-2 Containerize | Windows IIS App Container N/A Application Virtual Directories 2 Found virtual directory located on a network drive. Consider moving the virtual directory to a local drive. implemented
A6N-APP-3 Containerize | Windows IIS App Container N/A Application Virtual Directories 2 Found a missing virtual directory. Consider excluding the virtual directory from the migration plan. implemented
A6N-APP-4 Containerize | Windows IIS App Container N/A Application Application pool identities 3 Application uses an application pool with an Active Directory identity. Configure a Group Managed Service Account (GMSA). implemented
A6N-APP-5 Containerize | Windows IIS App Container N/A Application ASP.NET Core 5 ASP.NET Core is not supported. implemented
A7N-APP-1 Containerize | Apache2 App Container N/A Application SSL detected 3 Apache VirtualHost SSL is enabled. SSL usage detected, but the current version does not support migrating SSL certificates. Consider configuring it manually: https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html. implemented
A7N-APP-2 Containerize | Apache2 App Container N/A Application Apache Version 4 Apache version unsupported. Unsupported Apache version detected. Consider using Apache 2.4. implemented
A7N-APP-3 Containerize | Apache2 App Container N/A Application Apache Installation Location 2 Apache is not installed in the default location. Consider moving the Apache configuration directory to /etc/apache2 on Ubuntu/Debian system, or /etc/httpd on CentOS system, before running the migration. implemented
A7N-APP-4 Containerize | Apache2 App Container N/A Application Apache Unsupported Modules 3 Unsupported Apache modules detected. Unsupported modules detected. Consider installing them manually on the migrated image. List of supported modules: https://cloud.google.com/migrate/containers/docs/apache/apache-customizing-a-migration-plan#load_and_install. implemented
A7N-APP-5 Containerize | Apache2 App Container N/A Application Unsupported PHP Version 2 Unsupported PHP version detected. Unsupported PHP version, consider using PHP 7.4. implemented
A7N-APP-6 Containerize | Apache2 App Container N/A Application WordPress Detected 4 WordPress virtual host detected. Consider using Migrate to Containers WordPress migration for this server. implemented
A7N-APP-7 Containerize | Apache2 App Container N/A Application Drupal Detected 4 Drupal virtual host detected. Drupal virtual hosts not supported in the current version of Migrate to Containers. implemented
A7N-APP-8 Containerize | Apache2 App Container N/A Application Magento Detected 4 Magento virtual host detected. Magento virtual hosts not supported in the current version of Migrate to Containers. implemented
A7N-APP-9 Containerize | Apache2 App Container N/A Application Database connections 2 Found database connections. Check if Apache2 is using an external database. If so, make sure the deployment cluster has access to it. implemented
A7N-APP-10 Containerize | Apache2 App Container N/A Application Web server connections 2 Found web server connections. Check if Apache2 is using an external web server. If so, make sure the deployment cluster has access to it. implemented
A7N-STO-1 Containerize | Apache2 App Container N/A Storage Network mounts 2 Found network mounts. Check if Apache2 uses NFS mounts. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A7N-STO-2 Containerize | Apache2 App Container N/A Storage Exported Network File Systems (NFS) 3 Found an exported NFS. Make sure to leave the current VM in place after the Apache2 server is deleted. Check if Apache2 uses the parts of the filesystem exported as NFS servers. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A8N-APP-1 Containerize | JBoss App Container N/A Application JBoss version 3 JBoss version unsupported. Unsupported JBoss version detected. Consider upgrading to a supported one. For the supported versions list, see: https://cloud.google.com/migrate/containers/docs/migrating-overview#migrate_a_jboss_server. implemented
A8N-APP-2 Containerize | JBoss App Container N/A Application JBoss key store 4 JBoss uses local key store. JBoss secrets are not supported yet, as a result the key store will be copied into the image, it should be moved manually during migration. implemented
A8N-APP-3 Containerize | JBoss App Container N/A Application JBoss running mode 5 JBoss migration is supported only when migrating JBoss servers in standalone mode. implemented
A8N-APP-4 Containerize | JBoss App Container N/A Application JBoss Java version 1 Unsupported Java version detected. Migration is possible but some features may not work. implemented
A8N-APP-5 Containerize | JBoss App Container N/A Application Database connections 2 Found database connections. Check if JBoss is using an external database. If so, make sure the deployment cluster has access to it. implemented
A8N-APP-6 Containerize | JBoss App Container N/A Application Web server connections 2 Found web server connections. Check if JBoss is using an external web server. If so, make sure the deployment cluster has access to it. implemented
A8N-STO-1 Containerize | JBoss App Container N/A Storage Network mounts 2 Found network mounts. Check if JBoss uses NFS mounts. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A8N-STO-2 Containerize | JBoss App Container N/A Storage Exported Network File Systems (NFS) 3 Found an exported NFS. Make sure to leave the current VM in place after the JBoss server is deleted. Check if JBoss uses the parts of the filesystem exported as NFS servers. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A9N-APP-1 Containerize | WordPress App Container N/A Application WordPress Version 3 WordPress version unsupported. Unsupported WordPress version detected. Migrate to Containers supports migration of wordpress v4.0 and newer. Consider upgrading WordPress to the latest version. implemented
A9N-APP-2 Containerize | WordPress App Container N/A Application Database connections 2 Found database connections. Check if WordPress is using an external database. If so, make sure the deployment cluster has access to it. See documentation here https://cloud.google.com/migrate/containers/docs/planning-best-practices#ensure_databases_are_accessible. implemented
A9N-APP-3 Containerize | WordPress App Container N/A Application WordPress Plugins 1 Found install plugins that may affect the migration. If you plan to change the site URL, some installed plugins may require extra effort. Refer to the plugin's support for more inforation. implemented
A9N-STO-1 Containerize | WordPress App Container N/A Storage Network mounts 2 Found network mounts. Check if WordPress uses NFS mounts. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A9N-STO-2 Containerize | WordPress App Container N/A Storage Exported Network File Systems (NFS) 3 Found an exported NFS. Make sure to leave the current VM in place after the WordPress server is deleted. Check if WordPress uses the parts of the filesystem exported as NFS servers. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A10N-APP-1 Containerize | WebSphere App Container N/A Application Database connections 2 Found database connections. Check if WebSphere is using an external database. If so, make sure the deployment cluster has access to it. implemented
A10N-APP-2 Containerize | WebSphere App Container N/A Application Web server connections 2 Found web server connections. Check if WebSphere is using an external web server. If so, make sure the deployment cluster has access to it. implemented
A10N-STO-1 Containerize | WebSphere App Container N/A Storage Network mounts 2 Found network mounts. Check if WebSphere is using NFS mounts. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
A10N-STO-2 Containerize | WebSphere App Container N/A Storage Exported Network File Systems (NFS) 3 Found an exported NFS. Make sure to leave the current VM in place once WebSphere is deleted. Check if WebSphere uses the parts of the filesystem exported as NFS servers. If so, make sure the NFS servers are accessible from the deployment cluster hosting the migrated container workload. See documentation here https://cloud.google.com/migrate/containers/docs/customizing-a-migration-plan#customize_nfs_mounts. implemented
C1N-HRD-1 Shift | Compute Engine VM N/A Hardware Media devices 1 Found CDROM or floppy disks. Migrate to VMs automatically removes CDROM or floppy disks. Remove all CD-ROM and floppy disks. If needed, migrate the data before removing the disks. implemented
C1N-HRD-2 Shift | Compute Engine VM N/A Hardware ESX version 5 Found unsupported ESXi version. Supported ESXi versions are 5.5 - 8.0. Use vMotion to move the VM to an ESX host running ESXi version 5.5 - 8.0. implemented
C1N-HRD-3 Shift | Compute Engine VM N/A Hardware vCenter version 5 Found unsupported vCenter version. Supported vCenter versions are 5.5 - 8.0. Update vCenter to versions 5.5 - 8.0. implemented
C1N-HRD-4 Shift | Compute Engine VM N/A Hardware CPU Architecture 1 Support for ARM VMs coming soon. implemented
C1N-STO-1 Shift | Compute Engine VM N/A Storage Shared volume 3 Found a shared VMDK attached to the VM. Shared drives cannot be migrated with Migrate to VMs since they do not support snapshot operations. Update the VM storage configuration to not share the VMDK file. You cannot back up shared drives using snapshots. implemented
C1N-STO-2 Shift | Compute Engine VM N/A Storage Independent disks 3 Found an Independent Disk attached to the VM. Independent Disks cannot be migrated with Migrate to VMs since they do not support snapshot operations. Reconfigure the VM storage, which currently uses disks configured as independent-persistent. You cannot back up independent disks using snapshots. See this article: https://kb.vmware.com/s/article/1004094. implemented
C1N-STO-3 Shift | Compute Engine VM N/A Storage RDM Disk 4 Found RDM drive with physical compatibility mode attached to the VM. RDM drives with physical compatibility mode enabled cannot be migrated with Migrate to VMs since they do not support snapshot operations. Disable physical compatibility mode for RDM drives that have it enabled. You cannot back up these types of disks using snapshots. See this article: https://kb.vmware.com/s/article/1005241?lang=en_US&queryTerm=RDM+Disk+issue. implemented
C1N-STO-5 Shift | Compute Engine VM N/A Storage CBT support 4 Disk CBT (Change Block Tracking) support is required. Make sure all storage supports Change Block Tracking, as described in this article: https://kb.vmware.com/s/article/1020128. implemented
C1L-APP-1 Shift | Compute Engine VM Linux Application Operating system 3 OS version not supported by Migrate to VMs. Update your OS to a supported version, as shown in this list: https://cloud.google.com/migrate/compute-engine/docs/5.0/reference/supported-os-versions. implemented
C1L-APP-2 Shift | Compute Engine VM Linux Application VirtIO Drivers 3 OS uses proprietary or customer built kernel which doesn't natively support or is missing required VirtIO drivers. Compute Engine requires the Linux kernel to include VirtIO drivers. Rebuild the kernel to include them. implemented
C1W-APP-1 Shift | Compute Engine VM Windows Application Operating system 3 OS version not supported by Migrate to VMs. Consider upgrading the operating system to one of the supported operating systems see list here: https://cloud.google.com/migrate/compute-engine/docs/5.0/reference/supported-os-versions. implemented
C1W-STO-1 Shift | Compute Engine VM Windows Storage BitLocker Encryption 3 System drive is encrypted using BitLocker. Decrypt the system drive before attempting migration. implemented
C2N-HRD-1 Shift | Google Cloud VMware Engine VM N/A Hardware ESX version 5 Found unsupported ESXi version. Supported ESXi versions are 6.5+. Use vMotion to move the VM to an ESX host running ESXi version 6.5 or higher. implemented
C2N-HRD-2 Shift | Google Cloud VMware Engine VM N/A Hardware vCenter version 5 Found unsupported vCenter version. Supported vCenter versions are 5.5 - 7.0. Upgrade to vCenter version 5.5 - 7.0. implemented
C2N-HRD-3 Shift | Google Cloud VMware Engine VM N/A Hardware CPU Architecture 5 ARM VMs are not supported. implemented
C2N-STO-1 Shift | Google Cloud VMware Engine VM N/A Storage RDM Disk 4 Found RDM drive with physical compatibility mode attached to the VM. RDM drives with physical compatibility mode enabled cannot be migrated since they do not support snapshot operations. Disable physical compatibility mode for RDM drives that have it enabled. You cannot back up these types of disks using snapshots. See this article: https://kb.vmware.com/s/article/1005241?lang=en_US&queryTerm=RDM+Disk+issue. implemented
C2N-STO-2 Shift | Google Cloud VMware Engine VM N/A Storage Shared volume 3 Found a shared VMDK attached to the VM. Shared drives cannot be migrated since they do not support snapshot operations. Update the shared VMDK drive. You cannot back up shared drives using snapshots. implemented
C2N-STO-3 Shift | Google Cloud VMware Engine VM N/A Storage Independent disks 3 Found an Independent Disk attached to the VM. Independent Disks cannot be migrated since they do not support snapshot operations. Update independent disks attached to the VM. You cannot back up independent disks using snapshots. See this article: https://kb.vmware.com/s/article/1004094. implemented
C2N-STO-4 Shift | Google Cloud VMware Engine VM N/A Storage CBT support 4 Disk CBT (Change Block Tracking) support is required. Reconfigure your VM storage to meet requirements for Changed Block Tracking (CBT). See this article: https://kb.vmware.com/s/article/1020128. implemented
D1N-APP-2 Shift | Google Distributed Cloud N/A Application CPU Usage 1 The number of CPU cores exceeds the limit of supported cores and high CPU usage has been detected over the last 7 days. Consult the vCPU limits of GDC before migrating. Migrating VMs that exceed the limit may cause degradation in application health. implemented
D1N-APP-3 Shift | Google Distributed Cloud N/A Application RAM Usage 1 The amount of RAM exceeds the limit of supported memory and high RAM usage has been detected over the last 7 days. Consult the RAM limits of GDC before migrating. Migrating VMs that exceed the limit may cause degradation in application health. implemented
D1N-HRD-1 Shift | Google Distributed Cloud N/A Hardware Hypervisor 5 Migration is only supported from vSphere. implemented
D1N-HRD-2 Shift | Google Distributed Cloud N/A Hardware vCenter version 5 vCenter version not supported. Update vCenter to version 6.0 or later. implemented
D1N-HRD-3 Shift | Google Distributed Cloud N/A Hardware ESX version 5 ESX version not supported. Consider using vMotion to move the VM to an ESX host running version 6.0 or later. implemented
D1N-HRD-4 Shift | Google Distributed Cloud N/A Hardware Attached disks 5 Found a non-SCSI disk. Consider changing disk type. implemented
D1N-HRD-5 Shift | Google Distributed Cloud N/A Hardware CPU Architecture 5 ARM VMs are not supported. implemented
D1N-HRD-6 Shift | Google Distributed Cloud N/A Hardware Non-uniform Memory Access (NUMA) settings 2 NUMA is not supported. Consider disabling NUMA settings. implemented
D1N-HRD-7 Shift | Google Distributed Cloud N/A Hardware Media devices 1 Found CDROM or floppy disks. Migrate to VMs automatically removes CDROM or floppy disks. Remove all CD-ROM and floppy disks. If needed, migrate the data before removing the disks. implemented
D1N-NET-1 Shift | Google Distributed Cloud N/A Networking Network interface cards (NICs) 4 Multiple NICs are not supported. Consider removing irrelevant network interfaces. implemented
D1N-STO-1 Shift | Google Distributed Cloud N/A Storage Disk Size 3 Found a large disk (>108TiB). GDC supports up to 128TiB for a single VM disk. Consider reducing disk size. implemented
D1L-APP-1 Shift | Google Distributed Cloud Linux Application Operating system 5 The VM's OS is not supported. See https://cloud.google.com/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/vms/create-custom-images/import-virtual-disk#supported_operating_systems for a list of supported operating systems. It may be possible to upgrade your VM to a supported OS. Unsupported operating systems may still work so consider trying to migrate with caution. implemented
D1L-APP-2 Shift | Google Distributed Cloud Linux Application Operating system 1 The VM's OS has an unsupported minor version. See https://cloud.google.com/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/vms/create-custom-images/import-virtual-disk#supported_operating_systems for a list of supported operating systems. An OS with the same major version but a higher minor version is supported. Migration should still work but consider upgrading the OS to a supported minor version. implemented
D1L-APP-3 Shift | Google Distributed Cloud Linux Application VirtIO Drivers 3 OS uses proprietary or customer built kernel which doesn't natively support or is missing required VirtIO drivers. GDC requires the Linux kernel to include VirtIO drivers. Rebuild the kernel to include them. implemented
D1W-APP-1 Shift | Google Distributed Cloud Windows Application Operating system 5 The VM's OS is not supported. See https://cloud.google.com/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/vms/create-custom-images/import-virtual-disk#supported_operating_systems for a list of supported operating systems. It may be possible to upgrade your VM to a supported OS. Unsupported operating systems may still work so consider trying to migrate with caution. implemented
D1W-STO-1 Shift | Google Distributed Cloud Windows Storage BitLocker Encryption 3 System drive is encrypted using BitLocker. Decrypt the system drive before attempting migration. implemented