Meta tags:
Headings (most frequently used words):
the, image, and, import, your, requirements, gcloud, boot, disk, for, console, on, prepare, file, to, configure, manually, disks, stay, organized, with, collections, save, categorize, content, based, preferences, overview, limitations, costs, plan, path, create, compress, custom, images, list, test, imported, ensure, it, works, what, next, project, bootloader, ssh, or, user, login, access, generic, virtualbox, storage, products, pricing, support, resources, engage,
Text of the page (most frequently used words):
the (346), and (160), #create (155), image (138), disk (128), you (113), for (109), vms (109), your (88), with (83), boot (76), compute (72), that (70), troubleshoot (65), instance (63), engine (62), import (61), about (60), can (58), cloud (52), disks (52), system (49), file (49), using (48), use (48), manage (47), configure (47), from (43), images (43), server (40), view (39), google (34), storage (34), windows (33), mig (33), overview (32), set (31), performance (30), custom (28), access (28), reservation (27), this (26), ssh (26), network (26), configuration (25), machine (24), connect (23), instances (22), must (21), hyperdisk (21), sql (21), process (20), virtual (20), monitor (20), console (19), tar (19), linux (19), operating (18), gpu (18), resources (17), after (17), files (17), policies (16), upload (16), existing (16), persistent (16), reservations (16), click (15), compressed (15), guest (15), host (15), snapshots (15), groups (15), recommendations (15), environment (14), imported (14), best (14), login (14), management (14), migrate (14), workload (14), creation (14), load (14), apply (14), page (13), following (13), gcloud (13), name (13), where (13), type (13), bootloader (13), new (13), install (13), raw (13), machines (13), bulk (13), microsoft (13), cluster (13), serial (12), have (12), bucket (12), data (12), remove (12), run (12), sole (12), availability (12), regional (12), license (11), logs (11), format (11), compress (11), not (11), add (11), multiple (11), metadata (11), based (11), delete (11), practices (11), workloads (11), stateful (11), are (10), list (10), manually (10), licenses (10), plan (10), step (10), startup (10), start (10), requirements (10), time (10), migs (10), attached (10), zones (10), more (9), size (9), project (9), complete (9), local (9), update (9), keys (9), service (9), external (9), addresses (9), optimize (9), application (9), managed (9), tenant (9), openshift (9), shutdown (9), hpc (9), enable (8), zone (8), select (8), change (8), workstation (8), want (8), running (8), systems (8), user (8), prepare (8), transfer (8), networking (8), cpu (8), resource (8), internal (8), choose (8), disaster (8), recovery (8), high (8), agent (8), h4d (8), flexibility (8), dns (8), optimized (8), tpu (8), code (7), support (7), all (7), understand (7), thumb (7), other (7), information (7), need (7), details (7), issues (7), one (7), options (7), path (7), available (7), grub (7), configurations (7), across (7), cost (7), build (7), updates (7), migration (7), commitments (7), balancing (7), benchmark (7), idle (7), request (7), scale (7), deploy (7), back (7), mysql (7), zonal (7), maintenance (7), templates (7), snapshot (7), backup (7), events (6), see (6), down (6), send (6), through (6), get (6), port (6), uses (6), standard (6), there (6), source (6), copy (6), encryption (6), location (6), tmp (6), command (6), apps (6), stop (6), kernel (6), default (6), single (6), manager (6), work (6), usage (6), security (6), instant (6), nested (6), gpus (6), applications (6), group (6), mode (6), demand (6), pools (6), failover (6), extension (6), customized (6), spot (6), sign (5), samples (5), within (5), stopped (5), created (5), check (5), image_name (5), ensure (5), configured (5), bucket_name (5), another (5), depending (5), tools (5), during (5), vboxmanage (5), directory (5), importing (5), platform (5), before (5), than (5), ubuntu (5), how (5), boots (5), only (5), costs (5), networks (5), meet (5), tcp (5), manual (5), public (5), guide (5), monitoring (5), databases (5), accounts (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), operations (5), placement (5), node (5), highly (5), multi (5), modify (5), capacity (5), schedules (5), audit (5), symphony (5), email (5), scripts (5), between (5), enhanced (5), capabilities (5), tenancy (5), restore (5), regions (5), types (5), control (5), faq (5), flex (5), português (4), español (4), some (4), troubleshooting (4), ready (4), family (4), take (4), output (4), unique (4), when (4), cli (4), specify (4), specific (4), top (4), connection (4), browser (4), either (4), encrypt (4), sudo (4), guest_name (4), virtualbox (4), dev (4), sda (4), identify (4), space (4), has (4), rhel (4), line (4), does (4), make (4), non (4), them (4), own (4), creating (4), app (4), move (4), infrastructure (4), export (4), perform (4), distributed (4), authentication (4), bandwidth (4), pmu (4), number (4), ssd (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), postgresql (4), extensions (4), suspend (4), resize (4), graceful (4), locations (4), plans (4), replication (4), review (4), bound (4), terms (3), center (3), hard (3), updated (3), content (3), apache (3), might (3), without (3), password (3), functional (3), address (3), test (3), vm_name (3), section (3), confirm (3), properly (3), then (3), failure (3), verify (3), which (3), instead (3), several (3), into (3), oldgnu (3), utility (3), tool (3), part (3), example (3), quiet (3), any (3), edit (3), itself (3), etc (3), fstab (3), distribution (3), arguments (3), changes (3), config (3), volumes (3), each (3), those (3), method (3), provider (3), steps (3), don (3), allow (3), additional (3), premises (3), static (3), repository (3), these (3), partition (3), mbr (3), hybrid (3), already (3), advanced (3), services (3), basic (3), physical (3), guides (3), observability (3), analytics (3), automatic (3), pro (3), patterns (3), higher (3), discounts (3), cuds (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), policy (3), testing (3), ibm (3), spectrum (3), deploying (3), deployment (3), protect (3), certificates (3), query (3), state (3), disable (3), properties (3), account (3), increase (3), schedule (3), lifecycle (3), design (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), site (2), youtube (2), started (2), status (2), pricing (2), products (2), last (2), 2026 (2), utc (2), licensed (2), under (2), feedback (2), versions (2), features (2), what (2), next (2), directly (2), username (2), private (2), connecting (2), reconfigure (2), original (2), repeat (2), booting (2), replace (2), tab (2), works (2), now (2), included (2), correctly (2), buckets (2), optionally (2), settings (2), hours (2), speed (2), store (2), sczf (2), compresses (2), quickly (2), osx (2), gtar (2), convert (2), replacing (2), supplied (2), qcow2 (2), vdi (2), shut (2), interface (2), sdb (2), lsblk (2), large (2), secondary (2), terminal (2), attach (2), enough (2), temporarily (2), hold (2), different (2), way (2), partitions (2), cause (2), grub2 (2), cfg (2), rhgb (2), splash (2), screens (2), splashimage (2), but (2), distributions (2), outside (2), practice (2), function (2), software (2), trusted (2), array (2), raid (2), spread (2), device (2), able (2), interactive (2), current (2), outbound (2), platforms (2), however (2), bastion (2), vpn (2), iap (2), forwarding (2), consistency (2), table (2), built (2), recommend (2), going (2), required (2), require (2), scenarios (2), feature (2), documentation (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), multicloud (2), pipelines (2), hosting (2), development (2), quota (2), commitment (2), consumption (2), full (2), registration (2), sles (2), collecting (2), nodes (2), report (2), arm (2), core (2), api (2), rdp (2), general (2), latency (2), analyze (2), visible (2), cores (2), automatically (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), place (2), setting (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), authenticate (2), synchronization (2), global (2), switch (2), byol (2), payg (2), byos (2), families (2), securing (2), event (2), simulate (2), topology (2), together (2), repairs (2), repair (2), failures (2), template (2), suspended (2), target (2), cancel (2), once (2), limit (2), interfaces (2), ipv6 (2), decrease (2), consistent (2), scoped (2), appliances (2), asynchronous (2), throughput (2), names (2), mount (2), memory (2), extreme (2), balanced (2), credentials (2), organization (2), rdma (2), preemptible (2), provisioning (2), models (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, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, github, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, java, registered, trademark, oracle, its, affiliates, developers, creative, commons, attribution, imports, fail, because, production, include, final, version, advantage, had, key, find, also, appropriate, expand, opens, booted, standalone, open, contains, expected, deprecated, project_id, stored, uri, right, codes, applicable, flag, note, initialize, minutes, enter, uploaded, menu, field, dialog, downloaded, uploads, navigates, class, clonemedium, controlvm, acpipowerbutton, prepared, wrote, conv, sparse, maj, min, mountpoint, 100g, sda1, 96g, sda2, sda3, swap, 500g, sr0, 1024m, rom, sufficient, write, mounted, although, still, actively, processing, almost, takes, generic, operate, references, invalid, entries, centos, suse, opensuse, mkconfig, debian, regenerate, commands, interact, ttys0, 38400n8d, usually, earlier, located, unbootable, isolated, encrypts, contents, level, decrypt, cannot, read, they, encrypted, let, provide, module, structure, act, logical, volume, entire, rather, eliminate, individually, typically, times, much, length, days, later, optimally, direct, requires, working, anywhere, responsibility, lose, disrupt, business, while, depends, well, consider, items, potential, transfers, very, even, copying, could, incur, significant, charges, finish, storing, temporary, begin, inbound, limitations, used, accessed, vendor, hosts, repositories, package, option, gzip, compression, increment, filename, supported, vmdk, qemu, img, acpi, values, primary, like, long, gpt, larger, 2048, most, stock, requirement, users, who, their, hardware, communicate, successfully, issue, attaching, reconfiguring, sure, alternatively, assistance, partner, migrating, greater, provided, unable, having, worry, focuses, prefer, automated, follow, instructions, recommended, datacenters, automates, being, moved, save, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, common, pay, viewing, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, panic, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, improve, resiliency, communication, reduce, compact, idpf, irdma, driver, nic, customize, threads, per, sustained, merge, split, extend, renew, purchase, savings, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, https, scaling, consuming, consume, combine, cud, sharing, decisions, signals, serving, predictions, organize, labels, replica, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, integrations, validation, were, deployed, transition, hammerdb, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, net, mongodb, flask, terraform, servers, over, mtls, random, generator, virtio, rng, accurate, protocol, ntp, append, els, restrictions, packages, deprecate, red, hat, knowledgebase, functionality, risks, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, faulty, unmanaged, affect, preserved, turn, off, alternate, fails, repairing, maintain, upgrades, override, selectively, applying, accelerate, out, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, info, accidental, deletion, rename, reset, resume, restart, referrers, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, failback, replicate, provisioned, iops, limits, evaluate, help, kms, customer, symbolic, links, ram, exapools, identity, ptr, record, rates, tags, restrict, automate, powershell, sac, securely, root, connections, iso, prerequisites, exporting, bring, detach, reattach, constraint, accounting, provision, examples, slurm, reserved, team, slice, slices, adds, deterministic, base, aci, preempted, historical, alternative, similar, displays, ops, logging, subnet, gpudirect, enabled, ultra, minimum, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, bare, metal, accelerators, scores, purpose, discover, free, skip, main,
Text of the page (random words):
to compute engine the boot disks must meet the following requirements we recommend that you install all available updates in your source vm if you built a custom operating system kernel it must meet the hardware and kernel configuration requirements most stock linux distributions already meet these requirements so this requirement is only for advanced users who build their own custom operating systems to run on compute engine the boot disk must be no larger than 2048 gb 2 tb the boot disk that you import must have a functional mbr partition table or a hybrid configuration of a gpt partition table with an mbr bootloader the primary partition on the boot disk can be in any format that you like as long as it boots properly from the mbr bootloader the bootloader on the boot disk must not have quiet rhgb or splashimage kernel command line arguments compute engine does not support splash screens on startup you can remove these values from the grub config during the bootloader configuration step the operating system on the boot disk must support acpi requirements for the image file the image file that you import must meet the following requirements perform a consistency check on the disk image by using the qemu img check command on the disk to export the virtual disk use the export function of your vm management software don t copy the vmdk file from your vm manager s file system the image file must be of a supported image the disk image filename must be disk raw the raw image file must have a size in an increment of 1 gb for example the file must be either 10 gb or 11 gb but not 10 5 gb the compressed file must be a tar gz file that uses gzip compression and the format oldgnu option for the tar utility manual requirements for your project when you create a vm instance from an imported image the instance must be able to access the external package repository for the operating system that is configured on the boot disk this repository can be accessed directly from the operating system vendor or through a network connection to your on premises infrastructure that hosts these repositories to set up access to the external repository complete one of the following steps in your project configure a static external ip address for your vm to connect to your local on premises network or other external networks set up a bastion host vpn or iap tcp forwarding that can be used to connect to your local on premises network or other external networks limitations to import disks using networks that don t allow external ip addresses you need to meet additional networking requirements for more information see importing disks using networks that don t allow external ip addresses image import costs before you begin understand the costs for the import process there is no cost for the inbound network data transfer to upload your boot disk image file to cloud storage and there is no cost to import that image as a compute engine custom image however there are costs for some specific steps in the import process the cost to temporarily store your compressed image files in a cloud storage standard bucket you must use a temporary cloud storage bucket to hold your files before you can import them as custom compute engine images you can remove the bucket after you complete the import process the cost for storing custom images after you finish importing them to compute engine the potential cost for outbound data transfers on your existing data center network provider or your current cloud service image files can be very large even after you compress them so copying those files to compute engine could incur significant outbound data transfer charges on some platforms the cost for compute engine persistent disks and vm instances where you can configure your image after you import it to compute engine plan and prepare your import path your method for importing your disk depends on the current configuration of the system that you want to move to compute engine you need a system where you can create and compress the boot disk image file as well as a system where you can upload the image file to cloud storage consider the following items when you plan your import path the image import path requires you to configure your boot disk in a working operating system environment this process can cause the boot disk to not boot anywhere outside of a compute engine environment it is your responsibility to ensure that you do not lose data on your disks or disrupt your functional business apps while you import your system to compute engine identify what your existing system access configuration is and plan how you want to access the system after you import it to compute engine if your system has existing user login or ssh configurations you can configure only the bootloader and then later configure the image to run optimally on compute engine you can access the instance through your existing ssh configuration or through a direct user login in the interactive serial console if your system does not have existing user login or ssh configurations you must configure the boot disk so that you are able to access it after it boots on compute engine the length of the import process can take several hours or days depending on the size of your boot disk and the speed of your network connection the system where you create and compress your boot disk image must have enough storage space to create the image files on a storage device other than the boot disk itself typically your image and tar gz files use 2 3 times as much space as the boot disk itself understand the file system structure for the existing system that you want to import if your operating system and app files are spread across multiple disks import each of those disks individually and use each image to create a unique persistent disk for your compute engine vm instance if your systems have boot volumes in a raid configuration where multiple disks act as a single logical volume create a single image from the entire array rather than creating one image for each disk in the array compute engine persistent disks eliminate the need for raid configurations if your system encrypts the contents of your boot disk with a trusted platform module or with software level encryption decrypt your boot disk before you create the boot disk image file google cannot read your images if they are encrypted we encrypt your images for you after you upload them and let you provide your own encryption keys for your persistent disks and cloud storage buckets after you identify or create a system where you can complete the import process connect to that system and configure the bootloader prepare the boot disk image on a running system prepare the boot disk image so that it can function in a compute engine environment configure the bootloader on the boot disk so that the image can boot on compute engine configure ssh or user login access on the boot disk so that you can access it after you import it to compute engine and start it as a vm instance this process can make the system unbootable outside of compute engine so the best practice is to complete this step on an isolated system using a copy of the boot disk that you want to import configure the bootloader configure the bootloader on the system so that it can boot on compute engine connect to the terminal on the system with the boot disk that you plan to import edit the grub config file usually this file is at etc default grub but on some earlier distributions it might be located in a non standard directory make the following changes to the grub config file remove any line that has splashimage compute engine does not support splash screens on startup remove the rhgb and quiet kernel command line arguments add console ttys0 38400n8d to the kernel command line arguments so that the instance can interact with the serial console regenerate the grub cfg file use one of the following commands depending on your distribution debian and ubuntu sudo update grub rhel centos suse opensuse sudo grub2 mkconfig o boot grub2 grub cfg edit the etc fstab file and remove references to all disks and partitions other than the boot disk itself and partitions on that boot disk invalid entries in etc fstab can cause your system startup process to stop after you configure the bootloader create and compress the disk image file configure ssh or user login access on the image after your image is running in compute engine as a vm instance you must have a way to access that instance you can either connect to the instance using an existing ssh configuration or you can sign in using a username and password by connecting to the serial console complete the ssh or user login configuration before you create and compress the disk image file create and compress the disk image file create and compress the boot disk image file for the system that you want to import to compute engine the process to create and compress the image file is different depending on the platform where your systems operate generic on almost any system you can use this process to create a raw image file that you can import to compute engine you can complete this process on the running system that you are importing or you can attach your boot disk as a secondary disk on another system and create the boot disk image from the stopped disk ensure that you have enough available storage space to temporarily hold the disk image files this example takes an image from a running system connect to the terminal on the system that has the boot disk that you plan to import use the lsblk command to identify the source boot disk from which you want to create an image and the location where you have sufficient space to write the image files for this example dev sda is the source boot disk and dev sdb is a large secondary disk mounted at the tmp directory although dev sda is running you can still create an image from it it is best to do this on a quiet system that is not actively processing data or running apps lsblk name maj min rm size ro type mountpoint sda 8 0 0 100g 0 disk sda1 8 1 0 96g 0 part sda2 8 2 0 1k 0 part sda3 8 5 0 4g 0 part swap sdb 8 16 0 500g 0 disk tmp sr0 11 0 1 1024m 0 rom create the image file from your boot disk sudo dd if dev sda of tmp disk raw bs 4m conv sparse change to the directory where you wrote the disk raw file cd tmp compress the raw disk into tar gz format this step compresses the image file so that you can more quickly upload it to cloud storage on osx install gtar and use it for this step instead of tar tar format oldgnu sczf tmp compressed image tar gz disk raw virtualbox if you prepared your system in a virtualbox environment you can use the vboxmanage tool to convert a vdi or qcow2 disk image to disk raw format shut down the virtualbox guest machine that you want to import replacing guest_name with the name of your guest machine you can shut down the guest machine with the virtualbox interface or by using the vboxmanage utility vboxmanage controlvm guest_name acpipowerbutton convert the guest image to raw format by using the vboxmanage utility replacing guest_name with the path to your guest image this guest image can be supplied as either a vdi or qcow2 file vboxmanage clonemedium guest_name disk raw format raw compress the raw disk into tar gz format this step compresses the image file so that you can more quickly upload it to cloud storage on osx install gtar and use it for this step instead of tar sudo tar format oldgnu sczf tmp compressed image tar gz disk raw the image file is compressed and ready to upload to cloud storage import the image to your custom images list upload the file to cloud storage and import the image into your custom images list optionally you can encrypt the image during the image import step import the image with either the console or the google cloud cli tools console copy the compressed image tar gz file to your local workstation and use the google cloud console to create a bucket and upload the file in the google cloud console go to the cloud storage browser page go to browser at the top of the page click create bucket specify a unique bucket name the standard storage class and a location where you want to store your image files click create to create the bucket the browser page navigates to the new bucket at the top of the page click upload files in the file dialog select the compressed image tar gz file that you downloaded from your system the file uploads from your local workstation this step can take several hours depending on the size of your compressed image file and the speed of your network connection after you upload the image to cloud storage import the image file to your custom images list in the google cloud console go to the images page go to images at the top of the page click create image in the name field specify a unique name for the image optionally specify an image family for your new image or configure specific encryption settings for the image click the source menu and select cloud storage file enter the path to the compressed image tar gz file that you uploaded to cloud storage bucket_name compressed image tar gz click create to import the image the process can take several minutes depending on the size of the boot disk image the image is now included on the images page you can create a vm using this imported image if there is a boot failure verify and ensure that you have configured the bootloader correctly gcloud and gcloud storage use the gcloud cli to upload the compressed boot disk image file you can complete this process on the system where you created the boot disk image or you can copy that file to another system and complete the upload process there instead install and initialize the gcloud cli on the system from which you plan to upload the compressed image tar gz use the gcloud cli to create a new cloud storage bucket gcloud storage buckets create gs bucket_name upload the compressed image tar gz file to the new bucket gcloud storage cp compressed image tar gz gs bucket_name import the image file as a new custom image note when you manually import an image you must set the right license code for your operating system using the licenses flag for more information on license codes in the operating system details page see the license tab in the section applicable to your operating system gcloud compute images create image_name source uri gs bucket_name compressed image tar gz replace the following image_name the name of the image that you imported bucket_name the name of the bucket that the imported image is stored in the image is now included in the list of custom images you can create a vm using this imported image if there is a boot failure verify and ensure that you have configured the bootloader correctly gcloud compute images list no standard images name project family deprecated status image_name project_id ready test the imported image to ensure it works confirm that...
|
