Meta tags:
description=Learn about reservations of Compute Engine VM instances.;

Headings (most frequently used words):

reservations, additional, for, requirements, restrictions, shared, with, and, how, work, billing, attached, to, commitments, compact, placement, policies, about, stay, organized, collections, save, categorize, content, based, on, your, preferences, what, next, created, from, an, instance, template, quota, information, products, pricing, support, resources, engage,

Text of the page (most frequently used words):
the (239), vms (143), create (139), for (138), and (134), #reservation (129), #reservations (110), with (97), you (79), project (63), about (62), that (62), troubleshoot (62), instance (60), shared (58), can (57), resources (49), manage (47), disk (46), use (41), using (40), disks (39), server (39), compute (38), view (38), windows (33), mig (33), overview (32), configure (32), engine (31), google (30), cloud (30), placement (30), performance (30), from (29), machine (29), policy (27), set (27), compact (26), type (26), any (26), delete (26), only (25), policies (22), monitor (22), attached (22), projects (21), consume (21), network (21), gpu (21), hyperdisk (21), sql (21), are (20), images (20), access (19), consumed (18), following (18), based (18), custom (18), instances (18), when (17), resource (17), your (17), reserved (17), apply (17), must (17), commitments (17), image (17), linux (17), properties (16), quota (16), configuration (16), this (15), same (15), specify (15), requirements (15), capacity (15), virtual (15), snapshots (15), groups (15), ssh (15), recommendations (15), template (14), workload (14), creation (14), host (14), load (14), connect (14), more (13), single (13), then (13), best (13), time (13), regional (13), availability (13), management (13), bulk (13), microsoft (13), cluster (13), see (12), default (12), managed (12), commitment (12), practices (12), migrate (12), automatically (12), zone (12), multiple (12), storage (12), sole (12), persistent (12), all (11), demand (11), owner (11), additional (11), have (11), new (11), organization (11), existing (11), workloads (11), stateful (11), consumption (10), service (10), each (10), created (10), creating (10), update (10), high (10), consumes (10), choose (10), available (10), metadata (10), migs (10), machines (10), add (10), logs (10), zones (10), other (9), information (9), consumer (9), number (9), share (9), restrictions (9), specific (9), enable (9), modify (9), types (9), gpus (9), h4d (9), cpu (9), disaster (9), recovery (9), application (9), licenses (9), tenant (9), openshift (9), shutdown (9), start (9), hpc (9), license (8), how (8), cuds (8), billed (8), additionally (8), consuming (8), running (8), snapshot (8), work (8), specifies (8), templates (8), zonal (8), local (8), ssd (8), remove (8), import (8), login (8), optimize (8), internal (8), install (8), agent (8), guest (8), boot (8), keys (8), flexibility (8), dns (8), optimized (8), tpu (8), thumb (7), billing (7), different (7), specifically (7), schedules (7), across (7), within (7), region (7), stop (7), change (7), networking (7), startup (7), balancing (7), benchmark (7), manually (7), idle (7), addresses (7), request (7), scale (7), deploy (7), back (7), mysql (7), maintenance (7), backup (7), events (6), support (6), details (6), its (6), send (6), price (6), discounts (6), charges (6), not (6), those (6), these (6), attach (6), reserve (6), specified (6), suspend (6), between (6), control (6), usage (6), security (6), migration (6), data (6), updates (6), instant (6), files (6), nested (6), applications (6), group (6), mode (6), pools (6), run (6), failover (6), extension (6), transfer (6), customized (6), spot (6), code (5), samples (5), understand (5), apache (5), uses (5), but (5), reduce (5), targeted (5), want (5), were (5), deleted (5), list (5), auto (5), resize (5), affinity (5), locations (5), series (5), location (5), count (5), monitoring (5), databases (5), accounts (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), operations (5), node (5), highly (5), build (5), multi (5), audit (5), symphony (5), options (5), email (5), scripts (5), manager (5), operating (5), systems (5), enhanced (5), capabilities (5), tenancy (5), restore (5), regions (5), workstation (5), faq (5), flex (5), português (4), español (4), pricing (4), products (4), down (4), learn (4), account (4), vcpu (4), central1 (4), move (4), document (4), specifying (4), lifecycle (4), one (4), name (4), where (4), located (4), close (4), latency (4), them (4), migrated (4), after (4), jobs (4), utilization (4), automatic (4), tools (4), distributed (4), authentication (4), issues (4), ubuntu (4), console (4), bandwidth (4), tcp (4), pmu (4), get (4), upgrade (4), live (4), autoscaling (4), cross (4), requests (4), calendar (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), graceful (4), plans (4), replication (4), review (4), bound (4), terms (3), training (3), need (3), otherwise (3), content (3), receive (3), being (3), used (3), instead (3), follows (3), they (3), changes (3), costs (3), unused (3), committed (3), example (3), spark (3), dataflow (3), note (3), minimum (3), supported (3), creates (3), setting (3), property (3), than (3), vertex (3), kubernetes (3), make (3), target (3), without (3), both (3), exactly (3), option (3), family (3), optionally (3), which (3), possible (3), match (3), constraints (3), constraint (3), has (3), keep (3), memory (3), sharing (3), improve (3), useful (3), user (3), guides (3), infrastructure (3), observability (3), analytics (3), troubleshooting (3), encryption (3), pro (3), serial (3), configurations (3), patterns (3), higher (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), testing (3), ibm (3), spectrum (3), perform (3), deploying (3), plan (3), during (3), prepare (3), deployment (3), rhel (3), environment (3), protect (3), certificates (3), query (3), state (3), disable (3), increase (3), schedule (3), design (3), size (3), non (3), pool (3), workstations (3), tpus (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), site (2), youtube (2), center (2), started (2), system (2), release (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), feedback (2), next (2), either (2), there (2), might (2), unnecessary (2), long (2), exists (2), regardless (2), while (2), duplicate (2), cost (2), vcpus (2), scenario (2), accelerators (2), rate (2), their (2), including (2), also (2), sustained (2), such (2), some (2), previous (2), 100 (2), combination (2), however (2), require (2), matching (2), a4x (2), bare (2), metal (2), ultra (2), per (2), maximum (2), sure (2), total (2), settings (2), similar (2), directly (2), restrict (2), doesn (2), purchase (2), immediately (2), include (2), field (2), locationhint (2), should (2), vary (2), platform (2), stops (2), hold (2), until (2), affected (2), organizational (2), sharedreservationsownerprojects (2), reserves (2), restart (2), resume (2), optional (2), cpus (2), prediction (2), aren (2), help (2), before (2), random (2), date (2), define (2), enabled (2), documentation (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), standard (2), full (2), registration (2), sles (2), export (2), port (2), collecting (2), nodes (2), report (2), arm (2), core (2), api (2), rdp (2), general (2), app (2), analyze (2), visible (2), cores (2), generation (2), underutilized (2), insights (2), globally (2), web (2), autohealing (2), iis (2), external (2), autoscaler (2), autoscalers (2), activity (2), provider (2), place (2), directory (2), services (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), file (2), volumes (2), authenticate (2), method (2), synchronization (2), global (2), switch (2), byol (2), payg (2), byos (2), families (2), guide (2), securing (2), event (2), simulate (2), topology (2), together (2), repairs (2), repair (2), check (2), failures (2), suspended (2), stopped (2), distribution (2), physical (2), cancel (2), once (2), limit (2), interfaces (2), ipv6 (2), static (2), decrease (2), basic (2), consistent (2), scoped (2), copy (2), appliances (2), asynchronous (2), throughput (2), encrypt (2), names (2), format (2), mount (2), extreme (2), balanced (2), credentials (2), through (2), advanced (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), accelerator (2), apis (2), reference (2), technology (2), areas (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, certification, architecture, getting, github, status, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, page, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, what, eligible, associated, discounted, qualify, trends, wasted, incurs, whether, does, incur, since, already, discount, covered, bills, suppose, prices, unreserved, would, suds, minute, isn, separate, mitigate, limitations, was, don, users, means, listed, unique, expire, throughout, replace, ones, purchasing, no_reservation, any_reservation, max, less, 000, batch, exceed, supports, distance, value, assume, shares, upon, didn, implications, contains, exist, requirement, titanium, c4a, c4d, attaching, numbers, disabled, reserving, successfully, rest, recommend, hint, indicate, among, experience, effects, attempts, cannot, due, continues, attempt, replenish, replenished, removed, caution, added, allowlist, behavior, simultaneously, stopping, suspending, incurring, consider, longer, counts, toward, becomes, again, indicates, describe, hardware, allowed, targets, makes, easier, track, allows, lots, whenever, order, helps, ensuring, designated, widely, fully, two, hours, deleting, avoid, provides, level, assurance, growth, migrations, charged, applicable, remain, verifies, requested, gives, save, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, common, pay, viewing, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, resiliency, communication, idpf, interface, irdma, driver, nic, customize, threads, merge, split, extend, renew, savings, dynamic, overcommit, floating, reliable, udp, backends, routing, https, scaling, combine, cud, allow, decisions, signals, serving, predictions, organize, labels, replica, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, deployed, transition, test, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, address, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, net, interactive, mongodb, flask, terraform, servers, over, mtls, generator, virtio, rng, accurate, protocol, ntp, append, els, packages, deprecate, versions, trusted, red, hat, knowledgebase, functionality, risks, command, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, process, faulty, unmanaged, affect, preserved, turn, off, alternate, fails, repairing, maintain, click, upgrades, override, selectively, applying, accelerate, out, outage, rebalance, reenable, proactive, redistribution, shape, distribute, info, accidental, deletion, spread, edit, rename, reset, referrers, source, uuid, recover, corrupted, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, consistency, failback, replicate, provisioned, iops, limits, evaluate, kms, customer, supplied, symbolic, links, practice, device, ram, exapools, verify, identity, ptr, record, failure, rates, tags, automate, password, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, browser, connections, networks, iso, imported, prerequisites, importing, exporting, bring, own, path, detach, reattach, accounting, provision, examples, slurm, team, slice, slices, adds, scenarios, deterministic, base, ready, aci, configured, preempted, historical, alternative, displays, ops, logging, subnet, public, gpudirect, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, platforms, scores, purpose, discover, free, skip, main,

Text of the page (random words):
on of your reservations and reduce the number of reservations that you need to create and manage for more information see how shared reservations work in this document sharing policy the sharing policy specifies if a reservation of gpu vms can be consumed by custom training jobs or prediction jobs in vertex ai by default custom training jobs or prediction jobs aren t allowed to consume reservations of gpu vms to change this see how to create or update reservations to be consumed in vertex ai vm count the vm count is the number of vms with matching properties and zone that you want to reserve when creating a reservation after you create the reservation you can modify the vm count vm properties the vm properties describe the hardware requirements memory and cpus and optional resources local ssd disks and gpus for the vms that you want to reserve when creating a reservation you can specify these properties directly specify the properties based on an existing vm or specify the properties by using an instance template a vm can consume a reservation only if both the vm s properties and reservation s vm properties exactly match for more information see requirements in this document optional resource placement policy compact a compact placement policy indicates that the reserved vms should be located as close to each other as possible to reduce network latency between them when you stop suspend or delete a vm that consumes a reservation the vm no longer counts toward the reservation the reserved capacity becomes available again if you want to delete a reservation to release the reserved capacity but keep any vms that consume the reservation then consider the following you can delete an automatically consumed reservation without stopping or suspending vms after you delete the reservation any vms that were consuming it keep running you keep incurring charges for them you can only delete a specifically targeted reservation if no vms consume it if you stop or suspend vms then after you delete the reservation you can only restart or resume the vms if you create a new specifically targeted reservation with a name zone and properties that match the deleted reservation how shared reservations work each vm in a shared reservation can be consumed by a vm in either the project that created the reservation owner project or any of the projects the reservation is shared with consumer projects when a vm stops consuming a shared reservation the shared reservation can be consumed by a different vm in any of the projects that the reservation is shared with if a shared reservation reserves multiple vms vms from multiple projects can consume the same shared reservation simultaneously by default projects can t create and modify shared reservations to create and modify a shared reservation in a project the project must be added to the allowlist of the shared reservations owner projects compute sharedreservationsownerprojects organizational policy constraint if you share a reservation then it is affected by additional quota requirements and has different consumption behavior than single project reservations caution if you migrate a project that created or consumed shared reservations to a different organization its shared reservations experience the following effects any shared reservations created in the migrated project any shared reservations where the migrated project is specified as the owner project are deleted running vms are not affected the project is not automatically removed from the shared reservations owner projects compute sharedreservationsownerprojects organizational policy constraint but you can optionally remove it the migrated project stops consuming resources from any reservations in the previous organization that were shared with it any shared reservations where the migrated project is specified as a consumer project the shared reservation attempts to hold on to the capacity for these resources if the reservation cannot hold on to the capacity immediately due to capacity constraints compute engine continues to attempt to replenish this capacity until all of the capacity is replenished you are only billed for the reserved capacity requirements all reservations have the following requirements a vm can consume a reservation only if all of the following properties for both the vm and the reservation exactly match project project requirements vary based on the reservation s share type zone machine type minimum cpu platform gpu type and count if any local ssd disk type and count if any reservation affinity reservation affinity requirements vary based on the reservation s consumption type compact placement policy if any a reservation can optionally include a compact placement policy to indicate that its reserved vms should be located as close to each other as possible to reduce network latency among them if a reservation specifies a compact placement policy then it can only be consumed by vms that specify the same compact placement policy location hint if any a reservation can optionally include the locationhint field which you can only specify when creating reservations or vms using rest google doesn t recommend specifying the locationhint field when creating reservations you must have unused quota available in your project for the resources that you re reserving if the reservation is created successfully then quota for those resources is consumed immediately additional requirements for reservations attached to commitments additionally reservations that are attached to commitments have the following requirements the reservations must be for the same project and region as the commitment the reservations must be for the same machine family series as the commitment however you can choose any machine type within that machine family series the reservations must have the auto delete option disabled if the commitment specifies any gpus local ssd disks or both then the attached reservation or combination of attached reservations must specify exactly the same numbers and types of those resources as the commitment note this requirement doesn t apply to local titanium ssd disks for use with c4 c4a c4d h4d or z3 machine types you can purchase commitments for these disks without attaching reservations to learn more see attach reservations to resource based commitments additional requirements for reservations created from an instance template additionally if you create a reservation by specifying an instance template make sure of the following you must create your reservation in the same region zone and project as the resources within the template specifically any regional or zonal resources that are specified in an instance template such as a machine type or a disk restrict the use of the template to the locations where those resources exist for example if your instance template specifies an existing disk in the us central1 a zone then you must create your reservation in the same zone an instance template contains project specific settings so you can only access and use an instance template within the same project for the projects a shared reservation is shared with you must create similar templates in those projects or create vms by specifying properties directly if the instance template specifies a compact placement policy you must create a specific reservation then when you create the vms to consume the reservation you must specifically target the reservation by name otherwise the vms can t consume the reservation additional quota requirements for shared reservations additionally there are the following quota implications for the owner and consumer projects of a shared reservation owner project the owner project consumes quota as follows when creating the shared reservation the owner project consumes quota for the total reserved resources when consuming reserved resources the owner project consumes quota for the resources that it consumes consumer projects the consumer projects consume quota only when consuming the reserved resources and only for the resources that they consume for example assume that project a the owner project creates a shared reservation for 10 resources and shares the reservation with project b and c the consumer projects upon creating the shared reservation project a consumes quota for 10 resources then if project a and b consume 2 reserved resources each project a and b each consume quota for 2 resources in total project a consumes quota for 12 resources project b consumes quota for 2 resources and project c consumes quota for 0 resources as it didn t consume the reservation additional requirements for reservations with compact placement policies additionally to specify a compact placement policy for a reservation make sure of the following requirements the compact placement policy must support reservations the compact placement policy can t specify a maximum distance value of 1 the compact placement policy can t be specified by more than one reservation at a time the reservation must support compact placement policies you can only specify a compact placement policy for an on demand single project specifically targeted reservation that is not attached to a commitment the vms reserved by the reservation must be supported by the compact placement policy the reservation s zone must be within the region of the compact placement policy the reservation s number of vms can t exceed the maximum number of vms that the compact placement policy supports the reservation s machine type must be supported by compact placement policies restrictions all reservations have the following restrictions you can only use reservations with the following google cloud products batch compute engine dataflow managed service for apache spark google kubernetes engine vertex ai you can reserve up to 1 000 vms per reservation you can t reserve a4x max bare metal instances or a4x a4 a3 ultra or a3 high with less than 8 gpus vms you can only update the reservation affinity property of vms to automatically consume any matching reservation any_reservation or no reservations no_reservation additional restrictions for reservations attached to commitments additionally reservations that are attached to commitments have the following restrictions you can attach reservations only to resource based commitments you can attach reservations only while you re purchasing your commitment you can attach a specific reservation to only one single commitment if the commitment specifies any resource types that require attached reservations then you can t do the following delete resize or modify the attached reservations throughout the commitment s lifecycle however you can replace existing attached reservations with new ones enable the auto delete setting on those attached reservations when commitments that specify these resource type expire any attached reservations are automatically deleted to learn more see attach reservations to resource based commitments additional restrictions for shared reservations additionally shared reservations have the following restrictions you can only share reservations with projects in the same organization as the project that creates the reservation each shared reservation can be shared with 1 to 100 consumer projects for each organization you can create up to 100 shared reservations for each unique combination of vm properties you can only list the reservations created by a specific project this means that each shared reservation is only listed in the project that created it you can t list all of the shared reservations in an organization or all of the reservations that are shared with a specific project if you create a shared reservation by specifying an instance template only the users within your project can access the same instance template and use it to create vms or other reservations you can t specify a compact placement policy when creating a shared reservation if you move a project that was using shared reservations to a new organization its shared reservations don t migrate to the new organization any shared reservations that were created in this project are deleted and any reservations from the previous organization that were shared with this project can t be consumed in the new organization for more information see how shared reservations work in this document you can mitigate the limitations of some of these requirements by following the best practices for shared reservations additional restrictions for reservations with compact placement policies additionally reservations that specify a compact placement policy have the following restrictions you can t share a compact placement policy across reservations instead you must use a separate compact placement policy for each reservation that you want to apply a compact placement policy to you can only specify compact placement policies any other type of resource policies such as instance schedules or snapshot schedules isn t supported billing reservations are billed at the same rate as their reserved resources including the same on demand prices and 1 minute minimum charges as unreserved running vms sustained use discounts suds cuds and custom pricing also apply as they would for running vms note when you use reservations with managed service for apache spark you can t receive resource based cuds for those resources if you use reservations with dataflow then you can receive cuds only for specifically targeted reservations that specify accelerators for more information see use compute engine reservations with dataflow for example suppose that you have the following scenario you have a 3 vcpu commitment in us central1 you re running 5 vcpus in us central1 a you have a 10 vcpu reservation in us central1 a in this scenario google cloud bills you as follows covered by number of vcpus committed use discount price 3 on demand price 2 vcpu used reservations 5 vcpu unused reservations 7 a reservation incurs charges for its reserved resources for as long as the reservation exists regardless of whether or not its resources are being used while consuming a reservation a vm does not incur duplicate resources charges since the reservation is already billed for the cost of the reserved resources for details see vms pricing additionally you can monitor the consumption trends of your reservations to reduce unnecessary costs from wasted or unused resources for more information see monitor reservations consumption additional billing information for shared reservations there are no additional charges for using shared reservations they are billed at the same price as single project compute engine reservations but the project that is billed for shared reservations changes with consumption as different projects might qualify for different cuds the billing project and price for shared reservations are managed as follows billing project by default the owner project is billed for the shared reservatio...