Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se describen las propiedades de la máquina virtual (VM) que puedes actualizar para una VM existente y cómo realizar dicha actualización.
Antes de comenzar
Para usar los comandos de la interfaz de línea de comandos (CLI) de gdcloud, asegúrate de haber descargado, instalado y configurado la CLI de gdcloud.
Todos los comandos para el dispositivo aislado de GDC usan la CLI de gdcloud o kubectl, y requieren un entorno de sistema operativo (SO).
Obtén la ruta de acceso del archivo kubeconfig
Para ejecutar comandos en el servidor de la API de Management, asegúrate de tener los siguientes recursos:
Ubica el nombre del servidor de la API de Management o pregúntale a tu administrador de la plataforma (PA) cuál es el nombre del servidor.
Accede y genera el archivo kubeconfig para el servidor de la API de Management si no tienes uno.
Usa la ruta de acceso para reemplazar MANAGEMENT_API_SERVER{"</var>"}} en estas instrucciones.
Solicita permisos y acceso
Para realizar las tareas que se indican en esta página, debes tener el rol de administrador de la VM del proyecto. Sigue los pasos para verificar o para que el administrador de IAM del proyecto te asigne el rol de administrador de máquinas virtuales del proyecto (project-vm-admin) en el espacio de nombres del proyecto en el que reside la VM.
Para las operaciones de VM con la consola de GDC o la CLI de gdcloud, solicita a tu administrador de IAM del proyecto que te asigne el rol de administrador de máquinas virtuales del proyecto y el rol de visualizador del proyecto (project-viewer).
Propiedades actualizables
Solo puedes cambiar las propiedades que se encuentran en el spec de la VM.
Cómo ver las propiedades que se pueden actualizar
Busca las propiedades que deseas cambiar con la consola de GDC o kubectl.
Console
En el menú de navegación, haz clic en Virtual Machines > Instances.
En la lista de VMs, haz clic en el nombre de una VM para ver sus propiedades.
Las propiedades editables tienen un ícono de editEditar.
kubectl
Consulta la lista de propiedades de la VM spec y los valores válidos correspondientes a cada propiedad:
Consulta de forma recursiva las subpropiedades de cada propiedad. En estos ejemplos, se muestra el valor de devolución de las subpropiedades compute y vcpus:
Este comando de ejemplo devuelve los campos de la subpropiedad compute:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis guide details how to update specific properties of existing virtual machines (VMs) using either the GDC console or the \u003ccode\u003ekubectl\u003c/code\u003e command-line interface.\u003c/p\u003e\n"],["\u003cp\u003eOnly properties within the \u003ccode\u003espec\u003c/code\u003e of the VM are modifiable, and users can identify these editable properties through the GDC console's "Edit" icon or by using the \u003ccode\u003ekubectl explain\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eUpdates to certain VM properties, such as \u003ccode\u003ecompute\u003c/code\u003e and \u003ccode\u003edisks\u003c/code\u003e, necessitate a VM restart for the changes to take effect, while others like \u003ccode\u003eguestEnvironment\u003c/code\u003e and \u003ccode\u003erunningState\u003c/code\u003e apply immediately.\u003c/p\u003e\n"],["\u003cp\u003eTo update VM properties via \u003ccode\u003ekubectl\u003c/code\u003e, users must edit the VM's \u003ccode\u003espec\u003c/code\u003e, save the changes, and, if necessary, restart the VM according to provided instructions.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egdcloud\u003c/code\u003e or \u003ccode\u003ekubectl\u003c/code\u003e CLI is required to make modifications to the VMs and requires the user to have signed into the system to receive the \u003ccode\u003ekubeconfig\u003c/code\u003e file.\u003c/p\u003e\n"]]],[],null,["# Update VM properties\n\nThis page describes which virtual machine (VM) properties you can update for an\nexisting VM and how to perform such an update.\n\nBefore you begin\n----------------\n\nTo use `gdcloud` command-line interface (CLI) commands, ensure that you have downloaded, installed,\nand configured the [`gdcloud` CLI](/distributed-cloud/hosted/docs/latest/appliance/resources/gdcloud-overview).\nAll commands for GDC air-gapped appliance use the `gdcloud` or\n`kubectl` CLI, and require an operating system (OS) environment.\n\n### Get the kubeconfig file path\n\nTo run commands against the Management API server, ensure you have the following\nresources:\n\n1. Locate the Management API server name, or ask your Platform Administrator (PA)\n what the server name is.\n\n2. [Sign in and generate](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/iam/sign-in#cli) the\n kubeconfig file for the Management API server if you don't have one.\n\n3. Use the path to replace \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER{\"</var>\"}}\u003c/var\u003e in these instructions.\n\n### Request permissions and access\n\nTo perform the tasks listed in this page, you must have the Project\nVirtualMachine Admin role. Follow the steps to either\n[verify](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/vms/preparation#verify-user-access)\nor have your Project IAM Admin\n[assign](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/vms/preparation#grant-user-access-vm-resources)\nyou the Project VirtualMachine Admin (`project-vm-admin`) role in the namespace\nof the project where the VM resides.\n\nFor VM operations using the GDC console or the gdcloud CLI,\nrequest your Project IAM Admin to assign you both the\nProject VirtualMachine Admin role and the Project Viewer (`project-viewer`)\nrole.\n\nUpdatable properties\n--------------------\n\nYou can only change the properties that are in the `spec` of the VM.\n\n### View updatable properties\n\nFind properties you want to change by using the GDC console or\n`kubectl`. \n\n### Console\n\n1. In the navigation menu, click **Virtual Machines \\\u003e Instances**.\n\n2. In the list of VMs, click a VM name to view its properties.\n\n3. Editable properties have an *edit* **Edit** icon.\n\n### kubectl\n\n1. View the list of properties for the VM `spec` and the valid values\n corresponding to each property:\n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e explain virtualmachines.virtualmachine.gdc.goog.spec\n\n The output is similar to the following: \n\n KIND: VirtualMachine\n VERSION: virtualmachine.gdc.goog/v1\n\n RESOURCE: spec \u003cObject\u003e\n\n DESCRIPTION:\n Defines the specification of the Virtual Machine.\n\n FIELDS:\n compute \u003cObject\u003e\n Specifies the CPU and Memory of the VM. CPU and Memory can be defined\n directly or through the VirtualMachineType. Changes to Compute require a\n reboot to take effect. Compute is immutable when the VM is in `Unknown`\n state.\n\n disks \u003c[]Object\u003e -required-\n Specifies the list of disks attached to this vm. There must be exactly one\n boot disk. Changes to disk attachments require a reboot to take effect.\n\n ...\n\n2. Recursively view the sub-properties for each property. These examples show\n the return for the `compute` and the `vcpus` sub-properties:\n\n - This example command returns the fields for the `compute` sub-property:\n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e explain virtualmachines.virtualmachine.gdc.goog.spec.compute\n\n The output is similar to the following: \n\n KIND: VirtualMachine\n VERSION: virtualmachine.gdc.goog/v1\n\n RESOURCE: compute \u003cObject\u003e\n\n DESCRIPTION:\n Specifies the CPU and Memory of the VM. CPU and Memory can be defined\n directly or through the VirtualMachineType. Changes to Compute require a\n reboot to take effect. Compute is immutable when the VM is in `Unknown`\n state.\n\n FIELDS:\n memory \u003c\u003e\n Specifies the amount of physical memory available to the instance. memory\n must have a minimum value of `1G`, and can be up to (including) `400G`.\n\n vcpus \u003cinteger\u003e\n Specifies the number of VCPUs that are available to the instance. Specify\n `vcpus` as an integer. This value must be a multiple of 2, with 2 as the\n minimum and 128 as the maximum allowed.\n\n ...\n\n - This example command returns the fields for the `vcpus` sub-property:\n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e explain virtualmachines.virtualmachine.gdc.goog.spec.compute.vcpus\n\n The output is similar to the following: \n\n KIND: VirtualMachine\n VERSION: virtualmachine.gdc.goog/v1\n\n FIELD: vcpus \u003cinteger\u003e\n\n DESCRIPTION:\n Specifies the number of VCPUs that are available to the instance. Specify\n `vcpus` as an integer. This value must be a multiple of 2, with 2 as the\n minimum and 128 as the maximum allowed.\n\nAll of the properties can be updated on a running VM, but often require the VM to be restarted to take\neffect.\n\nThese property updates require that the VM be restarted for the changes to\ntake effect:\n\n- compute\n- disks\n- firmware\n- [startupScripts](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/vms/manage-the-os/startup-script-vm-instance)\n\nThese property updates take effect immediately:\n\n- guestEnvironment\n- runningState\n\nUpdate VM properties\n--------------------\n\nUpdate VM properties by using the GDC console or `kubectl`. \n\n### Console\n\n1. In the navigation menu, click **Virtual Machines \\\u003e Instances**.\n\n2. In the list of VMs, click a VM name to view its properties.\n\n3. Click *edit* **Edit** next to the property that\n you want to edit and make your changes.\n\n4. If you want to replace the boot disk or add a new disk, see\n [Replace a boot disk](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/vms/manage-vm-boot-disks/replace-a-boot-disk)\n or [Add a disk to a VM](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/vms/manage-storage/add-a-vm-disk).\n\n5. Click **Save**.\n\n### kubectl\n\n1. Run the following command:\n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e \\\n edit virtualmachines.virtualmachine.gdc.goog \u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e \\\n -n \u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e\n\n Replace the variables as defined in the following table.\n\n2. Edit the `spec` to update the required fields and values for the updatable\n properties.\n\n3. Save the file.\n\n4. If the property update requires the VM to be restarted,\n use the [Restart a VM](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/vms/manage-vms/operations-and-lifecycle/start-and-stop-vm#restart-a-vm)\n instructions to restart the VM."]]
