Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Nesta página, descrevemos quais propriedades de máquina virtual (VM) podem ser atualizadas em uma
VM atual e como fazer essa atualização.
Antes de começar
Para usar os comandos da interface de linha de comando (CLI) gdcloud, verifique se você baixou, instalou
e configurou a CLI gdcloud.
Todos os comandos do Distributed Cloud usam a CLI gdcloud ou kubectl e exigem um ambiente de sistema operacional (SO).
Extrair o caminho do arquivo kubeconfig
Para executar comandos no servidor da API Management, verifique se você tem os seguintes
recursos:
Faça login e gere o arquivo
kubeconfig para o servidor da API Management se você não tiver um.
Use o caminho para o arquivo kubeconfig do servidor da API Management para substituir
MANAGEMENT_API_SERVER nestas instruções.
Solicitar permissões e acesso
Para executar as tarefas listadas nesta página, você precisa ter o papel de administrador de máquina virtual do projeto. Siga as etapas para
verificar
se você tem o papel de administrador de máquina virtual do projeto (project-vm-admin) no namespace
do projeto em que a VM reside.
Para operações de VM usando o console do GDC ou a CLI gdcloud,
peça ao administrador do IAM do projeto para atribuir a você os papéis de
administrador de máquina virtual do projeto e leitor do projeto (project-viewer).
Propriedades atualizáveis
Só é possível mudar as propriedades que estão no spec da VM.
Ver propriedades atualizáveis
Encontre as propriedades que você quer mudar usando o console do GDC ou
kubectl.
Console
No menu de navegação, clique em Virtual Machines > Instâncias.
Na lista de VMs, clique no nome de uma delas para conferir as propriedades.
As propriedades editáveis têm um ícone editEditar.
kubectl
Confira a lista de propriedades da VM spec e os valores válidos correspondentes a cada propriedade:
KIND: VirtualMachine
VERSION: virtualmachine.gdc.goog/v1
RESOURCE: spec <Object>
DESCRIPTION:
Defines the specification of the Virtual Machine.
FIELDS:
compute <Object>
Specifies the CPU and Memory of the VM. CPU and Memory can be defined
directly or through the VirtualMachineType. Changes to Compute require a
reboot to take effect. Compute is immutable when the VM is in `Unknown`
state.
disks <[]Object> -required-
Specifies the list of disks attached to this vm. There must be exactly one
boot disk. Changes to disk attachments require a reboot to take effect.
...
Confira recursivamente as subpropriedades de cada propriedade. Estes exemplos mostram o retorno das subpropriedades compute e vcpus:
Este comando de exemplo retorna os campos da subpropriedade compute:
KIND: VirtualMachine
VERSION: virtualmachine.gdc.goog/v1
RESOURCE: compute <Object>
DESCRIPTION:
Specifies the CPU and Memory of the VM. CPU and Memory can be defined
directly or through the VirtualMachineType. Changes to Compute require a
reboot to take effect. Compute is immutable when the VM is in `Unknown`
state.
FIELDS:
memory <>
Specifies the amount of physical memory available to the instance. memory
must have a minimum value of `1G`, and can be up to (including) `400G`.
vcpus <integer>
Specifies the number of VCPUs that are available to the instance. Specify
`vcpus` as an integer. This value must be a multiple of 2, with 2 as the
minimum and 128 as the maximum allowed.
...
Este comando de exemplo retorna os campos da subpropriedade vcpus:
KIND: VirtualMachine
VERSION: virtualmachine.gdc.goog/v1
FIELD: vcpus <integer>
DESCRIPTION:
Specifies the number of VCPUs that are available to the instance. Specify
`vcpus` as an integer. This value must be a multiple of 2, with 2 as the
minimum and 128 as the maximum allowed.
Todas as propriedades podem ser atualizadas em uma VM em execução, mas geralmente exigem que a VM seja reiniciada para entrar em vigor.
Essas atualizações de propriedade exigem que a VM seja reiniciada para que as mudanças entrem em vigor:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[[["\u003cp\u003eThis guide details how to update specific properties of an existing virtual machine (VM), focusing on changes within the VM's \u003ccode\u003espec\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo make changes, ensure you have the Project VirtualMachine Admin role, access to the \u003ccode\u003egdcloud\u003c/code\u003e or \u003ccode\u003ekubectl\u003c/code\u003e CLI, and the Management API server kubeconfig file.\u003c/p\u003e\n"],["\u003cp\u003eUpdatable properties can be viewed through the GDC console or by using \u003ccode\u003ekubectl\u003c/code\u003e to explore the \u003ccode\u003evirtualmachines.virtualmachine.gdc.goog.spec\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eCertain property updates, such as \u003ccode\u003ecompute\u003c/code\u003e and \u003ccode\u003edisks\u003c/code\u003e, require a VM restart to take effect, while others like \u003ccode\u003eguestEnvironment\u003c/code\u003e and \u003ccode\u003erunningState\u003c/code\u003e are applied immediately.\u003c/p\u003e\n"],["\u003cp\u003eUpdating VM properties involves using either the GDC console's edit features or \u003ccode\u003ekubectl\u003c/code\u003e commands to modify the VM's \u003ccode\u003espec\u003c/code\u003e, and may require a VM restart to fully implement the changes.\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/gdch/resources/gdcloud-overview).\nAll commands for Distributed Cloud 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. [Sign in and generate](/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/iam/sign-in#cli) the\n kubeconfig file for the Management API server if you don't have one.\n\n2. Use the path to the kubeconfig file of the Management API server to replace\n \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\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\n[verify](/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/vms/preparation#verify-user-access)\nthat you have 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/gdch/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/gdch/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/gdch/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/gdch/application/ao-user/vms/manage-vms/operations-and-lifecycle/start-and-stop-vm#restart-a-vm)\n instructions to restart the VM."]]