Troubleshooting sole-tenancy

Linux Windows

This page describes how to troubleshoot some potential issues that might occurwhile usingsole-tenant nodes.

Node group size limitation

  • Problem: Size of a node group is limited to 100.

    • Solution: Create multiple node groups and use the same affinity labelfor each node group. Then, when scheduling VMs on these node groups, use theaffinity label you assigned to the node groups.

VM scheduling failures

  • Problem: Can't schedule a VM on a sole-tenant node.

    • Solution:

      • You can't schedule a sole-tenant VM if there's no node in the zonethat matches the VM'saffinity or anti-affinityspecification. Check that you have specified the correct affinitylabels. Also, check that you have not specified any conflicting affinitylabels.

      • If you are using the restart in place maintenance policy, check thatthe VM'sOnHostMaintenance setting is set toterminate.

      • If you are using the migrate within node group maintenance policy,check that you are scheduling VMs on a node group, not a specific nodeor by using an affinity label.

      • Check that the specified node name matches the name of a node in thezone.

      • Check that the specified node group name matches the name of a nodegroup in the zone.

      • You can't schedule a sole-tenant VM if the VM's minimum CPU platform(--min-cpu-platform) is set to any value other thanAUTOMATIC.

VM tenancy

Autoscaling node groups

  • Problem: Can't enable the node group autoscaler.

    • Solution: You can only enable the node group autoscaler when you setthe node group maintenance policy to theDefault maintenance policy.

  • Problem: Want to retain already reserved nodes with the migrate withinnode group maintenance policy.

    • Solution: When using theMigrate within node group maintenancepolicy, set the node group autoscaler to only scale out, which adds nodes tothe node group when it needs extra capacity.

  • Problem: No remaining CPU quota in the region.

    • Solution: Autoscaling might fail if you have no remaining CPU quota inthe region, the number of nodes in a group is at the maximum number allowed,or there was a billing issue. Depending on the error, you might need torequest an increase in CPU quota or create a new sole-tenant node group.

Bringing your own licenses (BYOL)

  • Problem: Configuring the restart in-place maintenance policy.

    • Solution: If using the restart in-place maintenance policy, set theVM'sOnHostMaintenanceSetting toterminate.

  • Problem: Scheduling VMs on node groups with the migrate within node groupmaintenance policy.

    • Solution:

      • Schedule VMs onto a node group, not on a specific node or by using acustomized affinity label.

      • Create 2 nodes and enable the autoscaler; otherwise, if you create anode group of size 1, the node is reserved for holdback.

Capacity issues

  • Problem: Not enough capacity on a node or in a node group.

    • Solution:

      • If you reschedule a VM onto a node that is scheduling VMs in parallel,in rare situations there might not be capacity.

      • If you reschedule a VM onto a node in a node group on which youhaven't enabledautoscaling,there might not be capacity.

      • If you reschedule a VM onto a node in a node group on which you haveenabled autoscaling but have exceeded your CPU quota, there might not becapacity.

CPU overcommit

  • Problem: An error indicating that no sole-tenant node group was specifiedwhen you set the value for the minimum number of CPUs:

    Invalid value for field 'resource.scheduling.minNodeCpus': '2'. Node virtualCPU count may only be specified for sole-tenant instances.
    • Solution: Specify a sole-tenant node group when setting the value forthe minimum number of CPUs

  • Problem: An error indicating that the total of the minimum number of CPUsfor all sole-tenant VMs on a node is greater than the CPU capacity of the nodetype.

    Node virtual CPU count must not be greater than the guest virtual CPU count.
    No feasible nodes found for the instance given its node affinities and otherconstraints.
    • Solution: Specify values for the minimum number of CPUs for each VM sothat the total for all VMs does not exceed the number of CPUs specified bythe sole-tenant node type.

  • Problem: An error indicating that the total number of CPUs specified bythe machine types for all VMs on a node is more than twice the minimum number ofCPUs specified for all VMs on a node.

    Guest virtual CPU count must not be greater than [~2.0] times the nodevirtual CPU count.
    • Solution: Increase the value for the minimum number of CPUs for VMs onthis node until the total minimum number of CPUs is greater than or equal tohalf the value for the total number of CPUs determined by the machine types.

  • Problem: An error indicating that the value for the minimum number of CPUsis not an even number greater than or equal to 2.

    Invalid value for field 'resource.scheduling.minNodeCpus': '3'. Node virtualCPU count must be even.
    • Solution: Specify a value for the minimum number of CPUs that is aneven number greater than or equal to 2.

GPUs

  • Problem: An error indicating that instance creation failed because ofnode property incompatibility.

    Instance could not be scheduled due to no matching node with property compatibility.
    • Solution: GPU-enabled sole-tenant nodes only support VMs that have GPUsattached. To resolve this issue,Provision a sole-tenant VMwith GPUs.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-15 UTC.