Meta tags:
description= The different states a Compute Engine instance can go through during its lifecycle.;
Headings (most frequently used words):
state, compute, instance, and, pricing, engine, lifecycle, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, states, what, next, pending, provisioning, staging, running, pending_stop, stopping, terminated, repairing, suspending, suspended, products, support, resources, engage,
Text of the page (most frequently used words):
the (168), compute (128), #instance (123), create (120), and (107), vms (103), for (84), with (72), state (63), troubleshoot (63), about (61), manage (47), engine (46), view (43), disk (43), server (40), disks (36), mig (35), using (35), configure (33), windows (33), you (31), overview (31), performance (30), use (29), resources (28), set (28), cloud (27), reservation (27), google (26), instances (26), from (26), machine (22), delete (21), hyperdisk (21), sql (21), monitor (20), images (20), host (19), network (19), time (18), gpu (18), access (17), image (17), linux (17), policies (16), running (16), shutdown (16), configuration (16), reservations (16), can (15), that (15), start (15), creation (15), virtual (15), snapshots (15), groups (15), ssh (15), recommendations (15), operation (14), workload (14), load (14), apply (14), custom (14), connect (14), request (13), management (13), bulk (13), microsoft (13), cluster (13), attached (12), stop (12), type (12), storage (12), sole (12), availability (12), persistent (12), best (12), regional (12), following (11), your (11), provisioning (11), guest (11), tpu (11), based (11), practices (11), workloads (11), stateful (11), suspended (10), changes (10), managed (10), metadata (10), migs (10), machines (10), migrate (10), add (10), logs (10), zones (10), events (9), this (9), when (9), cpu (9), terminated (9), service (9), internal (9), boot (9), application (9), licenses (9), tenant (9), multiple (9), openshift (9), hpc (9), license (8), addresses (8), usage (8), states (8), lifecycle (8), suspend (8), repair (8), restart (8), maintenance (8), manually (8), flex (8), import (8), resource (8), login (8), optimize (8), choose (8), install (8), disaster (8), recovery (8), high (8), agent (8), existing (8), update (8), keys (8), h4d (8), flexibility (8), dns (8), optimized (8), thumb (7), down (7), more (7), details (7), suspending (7), stopping (7), after (7), resume (7), then (7), graceful (7), group (7), networking (7), commitments (7), startup (7), balancing (7), benchmark (7), enable (7), idle (7), scale (7), deploy (7), back (7), mysql (7), zonal (7), remove (7), templates (7), snapshot (7), backup (7), understand (6), its (6), send (6), single (6), pending_stop (6), starts (6), staging (6), control (6), operations (6), security (6), migration (6), data (6), updates (6), instant (6), files (6), nested (6), gpus (6), across (6), applications (6), mode (6), demand (6), pools (6), run (6), failover (6), extension (6), change (6), new (6), transfer (6), customized (6), spot (6), code (5), samples (5), all (5), otherwise (5), list (5), one (5), during (5), completes (5), automatically (5), repairing (5), enters (5), scheduled (5), pending (5), issues (5), monitoring (5), databases (5), default (5), accounts (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), placement (5), node (5), highly (5), available (5), build (5), multi (5), modify (5), capacity (5), schedules (5), audit (5), symphony (5), options (5), email (5), scripts (5), manager (5), between (5), operating (5), systems (5), enhanced (5), capabilities (5), tenancy (5), restore (5), regions (5), types (5), workstation (5), faq (5), português (4), español (4), support (4), pricing (4), see (4), information (4), learn (4), how (4), incur (4), charges (4), until (4), repairs (4), process (4), error (4), happens (4), creating (4), wait (4), move (4), plan (4), tools (4), distributed (4), authentication (4), ubuntu (4), console (4), bandwidth (4), tcp (4), pmu (4), number (4), local (4), ssd (4), get (4), share (4), projects (4), upgrade (4), live (4), autoscaling (4), cross (4), region (4), requests (4), calendar (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), uses (4), postgresql (4), extensions (4), work (4), zone (4), location (4), resize (4), locations (4), plans (4), replication (4), review (4), bound (4), action (3), terms (3), system (3), other (3), need (3), content (3), are (3), apache (3), external (3), memory (3), fails (3), remains (3), only (3), specific (3), due (3), ends (3), transitions (3), quota (3), different (3), models (3), check (3), through (3), costs (3), guides (3), infrastructure (3), observability (3), analytics (3), automatic (3), troubleshooting (3), encryption (3), pro (3), serial (3), configurations (3), patterns (3), higher (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), project (3), policy (3), testing (3), ibm (3), spectrum (3), perform (3), deploying (3), prepare (3), deployment (3), rhel (3), environment (3), protect (3), certificates (3), query (3), disable (3), properties (3), account (3), increase (3), schedule (3), design (3), size (3), non (3), pool (3), workstations (3), series (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), products (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), feedback (2), doing (2), next (2), follows (2), but (2), allocate (2), requested (2), succeeds (2), before (2), configured (2), optionally (2), deletes (2), unless (2), however (2), stops (2), skip (2), scenarios (2), out (2), still (2), enabled (2), deletion (2), booting (2), transition (2), allocating (2), within (2), longer (2), has (2), requestvalidforduration (2), diagram (2), instead (2), help (2), documentation (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), commitment (2), consumption (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), latency (2), analyze (2), visible (2), cores (2), committed (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), web (2), autohealing (2), iis (2), shared (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), provider (2), place (2), directory (2), setting (2), services (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), name (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), failures (2), template (2), stopped (2), target (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), organization (2), user (2), advanced (2), rdma (2), created (2), preemptible (2), rtx (2), vws (2), constraints (2), accelerator (2), apis (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, github, status, release, 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, resetting, what, like, exist, regardless, remain, days, successfully, returns, original, began, prevents, restarting, leaving, automaticrestart, doesn, cover, level, agreement, sla, encounters, unavailable, while, permanently, depends, might, differ, expected, length, shuts, ongoing, occurs, shutting, period, times, any, tasks, forcefully, them, end, gracefully, shut, depending, taken, isn, yet, does, configuring, prepares, first, reasons, sets, finishes, attempts, acquire, necessary, acquires, have, sufficient, those, encounter, part, retries, disabled, standalone, seconds, directly, shown, preceding, described, sections, shows, also, trigger, important, moves, current, document, explains, migrations, save, categorize, preferences, stay, organized, collections, home, concurrent, 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, improve, resiliency, communication, reduce, compact, idpf, interface, irdma, driver, nic, customize, threads, per, sustained, merge, split, extend, renew, without, purchase, cost, savings, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, https, scaling, consuming, consume, combine, cud, allow, sharing, decisions, signals, serving, predictions, organize, labels, replica, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, were, deployed, 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, random, generator, virtio, rng, accurate, protocol, ntp, append, els, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, functionality, risks, command, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, faulty, unmanaged, affect, preserved, turn, off, alternate, maintain, click, upgrades, override, selectively, applying, accelerate, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, info, accidental, spread, edit, rename, reset, referrers, source, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, consistency, failback, replicate, make, provisioned, iops, limits, evaluate, settings, kms, customer, supplied, symbolic, links, practice, device, ram, attach, additional, exapools, verify, identity, ptr, record, failure, rates, tags, restrict, automate, password, require, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, browser, connections, networks, iso, imported, prerequisites, importing, exporting, bring, own, path, detach, reattach, constraint, accounting, provision, examples, slurm, reserved, team, slice, slices, adds, deterministic, base, requirements, ready, aci, preempted, historical, alternative, similar, displays, ops, logging, subnet, public, gpudirect, ultra, specify, minimum, platform, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, free, main,
Text of the page (random words):
create an on demand reservation for a single project for multiple projects combine an on demand reservation with a cud modify an on demand reservation delete an on demand reservation future reservations about future reservations create a reservation request for a single project for multiple projects modify a reservation request delete a reservation request future reservations in calendar mode about future reservations in calendar mode create a reservation request in calendar mode delete a reservation request in calendar mode view reservations or reservation requests consume a reservation prevent vms from consuming reservations load balancing about load balancing and scaling add an instance group to a load balancer request routing to a multi region external https load balancer cross region load balancing for microsoft iis backends set up internal tcp udp load balancing build reliable and scalable applications use autohealing for highly available applications use load balancing for highly available applications use autoscaling for highly scalable applications globally autoscale a web service on compute engine patterns for scalable and resilient applications patterns for using floating ip addresses on compute engine optimize resource utilization use recommendations to manage resources apply machine type recommendations to vms configure machine type recommendations apply machine type recommendations to migs view and apply idle resources recommendations view and understand vm insights view and understand mig insights manage idle vm recommendations idle vm recommendations overview view and apply idle vm recommendations configure idle vm recommendations manage reservation recommendations reservation recommendations overview view and apply idle reservation recommendations view and apply underutilized reservation recommendations configure idle reservation recommendations configure underutilized reservation recommendations overcommit cpus on sole tenant vms manual live migration about manual live migration manually live migrate vms share sole tenant node groups next generation dynamic resource management cost savings get discounts for committed usage about commitments and committed use discounts cuds resource based cuds purchase resource based commitments without attached reservations with attached reservations for os licenses manage resource based commitments renew commitments automatically extend commitment terms merge and split commitments upgrade commitments share resource based cuds across projects get discounts for sustained usage disk performance optimize hyperdisk performance optimize persistent disk performance optimize local ssd performance workload performance set the number of threads per core customize the number of visible cpu cores analyze the cpu performance using the pmu pmu overview enable the pmu in vms manage the pmu in vms network performance network bandwidth use google virtual nic use irdma network driver use idpf network interface configure a vm with higher bandwidth reduce latency by using compact placement policies optimize tcp network communication optimize tcp network performance optimize tcp network resiliency benchmark higher bandwidth vms optimize app latency with load balancing use dpdk to improve network performance network performance and gpu vms networking and gpu machines use higher network bandwidth patterns for using multiple host nics troubleshoot general tips troubleshoot connectivity troubleshoot rdp troubleshoot ssh troubleshoot os login troubleshoot vms troubleshoot vm operations troubleshoot vm creation troubleshoot resource availability errors troubleshoot bulk api vm creation troubleshoot vm reboots and shutdowns troubleshoot vm suspension troubleshoot vm updates troubleshoot unresponsive vms troubleshoot vm startup troubleshoot fstab errors troubleshoot kernel panic collecting core dumps rescue an inaccessible vm troubleshoot cpu bus locks troubleshoot cpu soft lockups troubleshoot vm configurations troubleshoot arm vms troubleshoot gpu vms troubleshoot nvidia gpu errors generate a nvidia bug report for blackwell gpus troubleshoot nested virtualization troubleshoot using vm screenshots troubleshoot sole tenant nodes troubleshoot vm performance issues troubleshoot sudoers files troubleshoot windows vms troubleshoot windows vms collecting diagnostic information troubleshoot using the serial console troubleshoot using the serial console viewing serial port output troubleshoot instance groups troubleshoot managed instance groups migs troubleshoot os management troubleshoot licenses troubleshoot image import and export troubleshooting sles pay as you go registration troubleshooting ubuntu pro registration troubleshoot metadata server troubleshoot metadata server troubleshoot networking issues troubleshoot common networking issues troubleshoot network drivers troubleshoot vm performance issues troubleshoot storage troubleshoot disk creation troubleshoot full disks and disk resizing troubleshoot disk encryption troubleshoot nvme disks troubleshoot instant snapshots troubleshoot standard snapshots troubleshoot reservations and commitments troubleshoot reservation creation troubleshoot reservation consumption troubleshooting reservation monitoring troubleshoot reservation updates troubleshoot future reservation creation and updates troubleshoot automatic commitment renewal troubleshoot quota errors troubleshoot concurrent operation quota errors troubleshoot workload authentication troubleshoot default service accounts troubleshoot workload to workload authentication ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation compute compute engine guides send feedback compute engine instance lifecycle stay organized with collections save and categorize content based on your preferences a compute engine instance transitions through different states from the time you create it until you delete it this document explains the compute instance lifecycle to help you troubleshoot issues manage resources plan migrations and understand costs to check the current state of your compute instances see instead the following view a list of compute instances view the details of a single compute instance compute instance states when you create a compute instance it starts in the provisioning state moves to staging and then enters the running state flex start virtual machine vm instances with a wait time requestvalidforduration and tpu instances start instead in the pending state from the running state you can move a compute instance to the suspended or terminated states or you can delete it important you control the lifecycle of your compute instances however scheduled operations provisioning models or host events can also trigger state changes the following diagram shows the different states that compute engine can set a compute instance to the states shown in the preceding diagram are described in the following sections pending state provisioning state staging state running state pending_stop state stopping state terminated state repairing state suspending state suspended state pending state after you create a compute instance it enters the pending state if it s one of the following otherwise the compute instance directly transitions to the provisioning state a flex start vm with a wait time requestvalidforduration that is 90 seconds or longer a standalone tpu instance a flex start vm or tpu instance that is part of a managed instance group mig unless the mig has creation retries disabled in the pending state compute engine attempts to acquire the necessary resources to start your compute instance until its wait time ends if compute engine acquires the resources within this time and you have sufficient quota for those resources then the compute instance state changes to provisioning otherwise you encounter an error and compute engine deletes the compute instance you can optionally delete the compute instance before the wait time ends if you no longer need it provisioning state after you create restart or resume a compute instance compute engine starts allocating resources for the compute instance and sets its state to provisioning when compute engine finishes allocating resources the compute instance transitions to the staging state staging state in the staging state compute engine prepares the compute instance for first boot due to one of the following reasons compute engine is still creating and configuring the compute instance you or a scheduled operation restart or resume the compute instance in this state the compute instance isn t running yet when it does start running or starts booting up the compute instance enters the running state running state in the running state compute engine is booting up the compute instance or the compute instance is running from the running state a compute instance can transition to pending_stop stopping suspending or repairing depending on the action taken system events or compute instance configuration pending_stop state in the pending_stop state the compute instance starts to gracefully shut down this shutdown process happens only if you ve enabled graceful shutdown the compute instance enters this state if you stop or delete the compute instance or compute engine is doing so automatically for a scheduled stop or deletion the compute instance state changes to stopping when one of the following happens you manually end the graceful shutdown the graceful shutdown period times out if any tasks are still running then compute engine forcefully stops them stopping state in the stopping state the compute instance is shutting down its guest os this process happens in the following scenarios you or a scheduled operation stop or delete the compute instance a host error occurs unless you configure the compute instance to skip the guest os shutdown the shutdown time depends on the compute instance type however if the compute instance stops due to a host error the shutdown time might differ from the expected length after the guest os shuts down the ongoing stop or delete operation ends as follows stop operation the compute instance state changes to terminated delete operation compute engine permanently deletes the compute instance and all its attached resources terminated state when a compute instance enters the terminated state compute engine completes the stop operation the compute instance remains in the terminated state until you or a scheduled operation restart or delete it if you request to restart the compute instance but compute engine can t allocate your requested resources then the restart request fails and the compute instance remains in the terminated state otherwise the restart request succeeds and the compute instance state changes to provisioning repairing state in the repairing state compute engine starts a repair operation on the compute instance compute engine repairs a compute instance if it encounters an internal error or the compute instance s host server is unavailable due to maintenance while a compute instance is in repair the following happens you can t use the compute instance the service level agreement sla doesn t cover the compute instance if compute engine successfully repairs the compute instance then it returns the compute instance state to its original state before the repair operation began this state can be staging running suspending or stopping if your compute instance is configured to automatically restart automaticrestart after the repair operation completes then you can optionally stop the compute instance during the repair process this action prevents the compute instance from automatically restarting after the repair completes leaving the compute instance in the terminated state suspending state in the suspending state compute engine starts the suspend operation for the compute instance you can only suspend specific compute instances when the suspend operation completes the compute instance state changes to suspended suspended state in the suspended state compute engine completes the suspend operation you can resume or delete the compute instance if you request to resume the compute instance but compute engine can t allocate your requested resources then the resume request fails and the compute instance remains in the suspended state otherwise the resume request succeeds and the compute instance state changes to provisioning a compute instance can remain in the suspended state for up to 60 days after that time compute engine changes the compute instance state to terminated compute instance pricing during a compute instance lifecycle you incur charges for the compute instance as follows for cpu usage you incur charges when the compute instance is in the following states running pending_stop for memory usage you incur charges when the compute instance is in the following states running pending_stop suspending suspended for attached resources like disks or external ip addresses you incur charges until the resources exist regardless of the compute instance state for more information see the pricing for compute instances what s next learn how to view the state of one or more compute instances by doing the following view a list of compute instances view the details of a single compute instance learn more about suspending stopping or resetting compute instances learn more about host events learn how to delete a compute instance send feedback except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 license and code samples are licensed under the apache 2 0 license for details see the google developers site policies java is a registered trademark of oracle and or its affiliates last updated 2026 07 14 utc need to tell us more easy to understand easytounderstand thumb up solved my problem solvedmyproblem thumb up other otherup thumb up hard to understand hardtounderstand thumb down incorrect information or sample code incorrectinformationorsamplecode thumb down missing the information samples i need missingtheinformationsamplesineed thumb down other otherdown thumb down last updated 2026 07 14 utc products and pricing see all products google cloud pricing google cloud marketplace contact sales support community forums support release notes system status resources github getting started with google cloud code samples cloud architecture center training and certification engage blog events x twitter google cloud on youtube google cloud tech on youtube about google privacy site terms google cloud terms manage cookies our third decade of climate action join us sign up for the google cloud newsletter subscribe ...
|
