When a member of a business group requests a virtual machine, resources must be allocated on one of the group's reservations to provision the machine.
The reservation on which a machine is provisioned must satisfy the following criteria:
The reservation must be of the same platform type as the blueprint from which the machine was requested.
A generic virtual blueprint can be provisioned on any type of virtual reservation.
The reservation must be enabled.
The compute resource must be accessible and not in maintenance mode.
The reservation must have capacity remaining in its machine quota or have an unlimited quota.
The allocated machine quota includes only machines that are powered on. For example, if a reservation has a quota of 50, and 40 machines have been provisioned but only 20 of them are powered on, the reservation’s quota is 40 percent allocated, not 80 percent.
The reservation must have sufficient unallocated memory and storage resources to provision the machine.
When a virtual reservation’s machine quota, memory, or storage is fully allocated, no further virtual machines can be provisioned from it. Resources may be reserved beyond the physical capacity of a virtualization compute resource (overcommitted), but when the physical capacity of a compute resource is 100% allocated, no further machines can be provisioned on any reservations with that compute resource until the resources are reclaimed.
If the blueprint has specific network settings, the reservation must have the same networks.
If the blueprint or reservation specifies a network profile for static IP address assignment, an IP address must be available to assign to the new machine.
If the blueprint or request specifies a location, the compute resource must be associated with that location.
If the value of the custom property VRM.Datacenter.Policy is Exact and there is no reservation for a compute resource associated with that location that satisfies all the other criteria, then provisioning fails.
If the value of VRM.Datacenter.Policy is NotExact and there is no reservation for a compute resource associated with that location that satisfies all the other criteria, provisioning can proceed on another reservation regardless of location. This option is the default.
If the blueprint or request specifies the custom property VirtualMachine.Host.TpmEnabled, trusted hardware must be installed on the compute resource for the reservation.
If the blueprint specifies a reservation policy, the reservation must belong to that reservation policy.
Reservation policies are a way to guarantee that the selected reservation satisfies any additional requirements for provisioning machines from a specific blueprint. For example, you can use reservation policies to limit provisioning to compute resources with a specific template for cloning.
If no reservation is available that meets all of the selection criteria, provisioning fails.
If multiple reservations meet all of the criteria, the reservation from which to provision a requested machine is determined by the following logic:
Reservations with higher priority are selected over reservations with lower priority.
If multiple reservations have the same priority, the reservation with the lowest percentage of its machine quota allocated is selected.
If multiple reservations have the same priority and quota usage, machines are distributed among reservations in round-robin fashion.
If multiple storage paths are available on a reservation with sufficient capacity to provision the machine volumes, storage paths are selected according to the following logic:
If the blueprint or request specifies a storage reservation policy, the storage path must belong to that storage reservation policy.
If the value of the custom property VirtualMachine.DiskN.StorageReservationPolicyMode is NotExact and there is no storage path with sufficient capacity within the storage reservation policy, then provisioning can proceed with a storage path outside the specified storage reservation policy. The default value of VirtualMachine.DiskN.StorageReservationPolicyMode is Exact.
Storage paths with higher priority are selected over storage paths with lower priority.
If multiple storage paths have the same priority, machines are distributed among storage paths in round-robin fashion.