O seguinte problema ocorre quando a imagem usada para criar a VM não tem tags para usar a gVNIC.
ERROR: (gcloud.compute.instances.create) Could not fetch resource:
- Invalid value for field 'resource.networkInterfaces[0].nicType': 'GVNIC'.
NetworkInterface NicType can only be set to GVNIC on instances with
GVNIC GuestOsFeature.
Para resolver esse problema, use uma imagem com tag para usar a gVNIC.
Para mais informações, consulte Criar uma imagem personalizada.
Outros problemas
Esta seção contém outros erros que podem ocorrer ao usar o
driver gVNIC com a instância do Compute Engine.
A instância de VM não foi inicializada
Causa: a gVNIC não está ativada na imagem.
Diagnóstico: verifique se o gVNIC está ativado na imagem.
Execute o seguinte comando para isso:
gcloud compute images describe IMAGE_NAME
Substitua IMAGE_NAME pelo nome da imagem.
A saída do comando deve exibir GVNIC em guestOsFeatures.
Também é possível verificar se a VM foi criada com o nic-type definido como
gVNIC. Para isso, execute este comando:
Se o driver estiver instalado, você verá o texto Original File Name : gvnic.inf na saída.
Caso contrário, nenhuma mensagem será retornada.
Resolução: se o gVNIC não estiver
disponível, verifique se você está usando uma
imagem com suporte ou se
está usando
configure o gVNIC
na imagem personalizada.
O valor de MTU definido na VPC não está sendo usado pela instância de computação
Depois de seguir as instruções para
mudar o valor de MTU, a configuração de MTU
na instância não usa o mesmo valor de MTU. Por exemplo,
é possível executar o comando /sbin/ifconfig | grep mtu na sua instância para verificar
a configuração de MTU. Você reiniciou a instância, mas a configuração
dela não foi atualizada.
Causa:a versão do driver da gVNIC é muito antiga.
Resolução:
Se a instância usar uma imagem pública, consulte a guia Recursos de rede
da versão do SO na página
Detalhes do sistema operacional. Verifique se ele mostra que os frames Jumbo têm suporte total.
Se a imagem pública não tiver suporte total a frames jumbo ou se você estiver usando
uma imagem do SO personalizada, a versão instalada do driver da gVNIC será
muito antiga e não terá suporte aos valores de MTU mais altos. Siga as
instruções na seção
Usar em sistemas operacionais não compatíveis
para atualizar o driver da gVNIC para sua instância de computação.
Depois de atualizar o driver gVNIC, reinicie a instância e verifique novamente a configuração
MTU.
Capacidade de processamento de rede ruim para VMs do Windows Server 2022 e Windows 11
É possível ter uma capacidade de processamento de rede ruim ao usar a
NIC virtual do Google (gVNIC) com
VMs do Windows Server 2022 e Windows 11 que usam a versão 1.0.0@44
do pacote GooGet do driver gVNIC ou anterior.
Para resolver esse problema, atualize o pacote GooGet do driver da gVNIC para a versão
1.0.0@45 ou mais recente fazendo o seguinte:
Verifique qual versão do driver está instalada na VM. Para isso, execute o comando
a seguir em um prompt de comando ou sessão do PowerShell como administrador:
Se a versão do driver google-compute-engine-driver-gvnic.x86_64 for
1.0.0@44 ou anterior, atualize o
repositório de pacotes GooGet
executando o seguinte comando em um prompt de comando ou
sessão do PowerShell como administrador:
[[["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-03 UTC."],[[["\u003cp\u003eTo resolve errors related to gVNIC, ensure the VM image is tagged to use gVNIC and verify this by using the \u003ccode\u003egcloud compute images describe IMAGE_NAME\u003c/code\u003e command and checking for \u003ccode\u003eGVNIC\u003c/code\u003e under \u003ccode\u003eguestOsFeatures\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIf a VM instance doesn't boot, confirm that gVNIC is enabled on the image and that the \u003ccode\u003enic-type\u003c/code\u003e is set to \u003ccode\u003egVNIC\u003c/code\u003e during VM creation, which can be verified using the \u003ccode\u003egcloud compute instances describe VM_NAME\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIf a VM instance boots but is not reachable over the network, check if the gVNIC driver is installed and loaded using \u003ccode\u003emodinfo gve\u003c/code\u003e and \u003ccode\u003elsmod | grep gve\u003c/code\u003e for Linux, or \u003ccode\u003edism /online /get-drivers | findstr gvnic\u003c/code\u003e for Windows.\u003c/p\u003e\n"],["\u003cp\u003eIf the MTU value set in VPC isn't used by the compute instance, update the gVNIC driver to the latest version by checking the OS support for Jumbo Frames and, if necessary, manually updating the driver using the provided instructions, then restart the instance.\u003c/p\u003e\n"],["\u003cp\u003eFor Windows Server 2022 and Windows 11 VMs experiencing poor networking throughput with gVNIC, update the gVNIC driver GooGet package to version \u003ccode\u003e1.0.0@45\u003c/code\u003e or later by using the \u003ccode\u003egooget installed\u003c/code\u003e and update commands.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting Google Virtual NIC\n\n*** ** * ** ***\n\nHere are some tips to help troubleshoot [Google Virtual NIC (gVNIC)](/compute/docs/networking/using-gvnic).\n\nCommon errors\n-------------\n\nThe following issue occurs when the image used to create the VM\nis not tagged to use gVNIC. \n\n```\nERROR: (gcloud.compute.instances.create) Could not fetch resource:\n - Invalid value for field 'resource.networkInterfaces[0].nicType': 'GVNIC'.\nNetworkInterface NicType can only be set to GVNIC on instances with\nGVNIC GuestOsFeature.\n```\n\nTo resolve this issue, ensure that you are using an image that is tagged to use gVNIC.\nFor more information, see [Create a custom image](/compute/docs/networking/using-gvnic#create-custom-image).\n\nOther issues\n------------\n\nThis section contains other errors that you might encounter when using the\ngVNIC driver with your Compute Engine instance.\n\n### VM instance didn't boot\n\n- **Cause:** gVNIC is not enabled on the image.\n\n- **Diagnosis:** Check that the image has `gVNIC` enabled.\n To verify, run the following command:\n\n ```\n gcloud compute images describe IMAGE_NAME\n ```\n\n Replace \u003cvar translate=\"no\"\u003eIMAGE_NAME\u003c/var\u003e with the name of your image.\n\n The output of the command should show `GVNIC` under `guestOsFeatures`.\n\n You can also check if the VM was created with the `nic-type` set to\n `gVNIC`. To do this run the following command: \n\n ```\n gcloud compute instances describe VM_NAME\n ```\n\n Replace \u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e with the name of your VM.\n- **Resolution:** Ensure that you are using a\n [supported image](/compute/docs/networking/using-gvnic#os-support) or that you have properly\n [set up the gVNIC driver](/compute/docs/networking/using-gvnic#manual-gvnic-setup) on your custom image.\n\n### VM instance booted but is not reachable over the network\n\n- **Cause:** gVNIC was not successfully installed and loaded.\n\n- **Diagnosis:** To check if the driver was installed and loaded, complete the\n following steps:\n\n ### Linux\n\n 1. Check that the driver is installed.\n\n ```\n modinfo gve\n ```\n\n The output should resemble the following: \n\n ```\n filename: /lib/modules/4.15.0-1036-gcp/updates/dkms/gve.ko\n version: 1.1.0\n license: Dual MIT/GPL\n description: gVNIC Driver\n author: Google, XXX.\n srcversion: 5FEFB9DD945EB2DEC94EE09\n alias: pci:v00001AE0d00000042sv*sd*bc*sc*i*\n depends:\n retpoline: Y\n name: gve\n vermagic: 4.15.0-1036-gcp SMP mod_unload\n ```\n 2. Check that the driver is loaded.\n\n ```\n lsmod | grep gve\n ```\n\n The output should resemble the following: \n\n ```\n gve 49152 0\n ```\n\n ### Windows\n\n 1. Connect to instance through [SAC](/compute/docs/instances/connecting-to-windows#windows_cli).\n 2. Login with your username and password.\n 3. From the command prompt, run the following command:\n\n ```\n dism /online /get-drivers | findstr gvnic\n ```\n 4. Review the result.\n\n - If the driver is installed, you should see the text `Original File Name : gvnic.inf` in the output.\n - If the driver is not installed, no message is returned.\n | **Note:** You can also review the [interactive serial console](/compute/docs/instances/interacting-with-serial-console) when debugging issues with your connection.\n- **Resolution:** If gVNIC is not\n available, ensure that you are using a\n [supported image](/compute/docs/networking/using-gvnic#os-support) or that\n you have properly\n [set up gVNIC](/compute/docs/networking/using-gvnic#manual-gvnic-setup)\n on your custom image.\n\n### MTU value set in VPC not being used by compute instance\n\nAfter following the instructions to\n[change the MTU value](/vpc/docs/change-mtu-vpc-network), the MTU\nconfiguration on the instance isn't using the same MTU value. For example,\nyou might run the `/sbin/ifconfig | grep mtu` command on your instance to check\nthe MTU setting. You have restarted the instance, but the instance\nconfiguration isn't updated.\n\n**Cause:** The gVNIC driver version is too old\n\n**Resolution:**\n\n1. If your instance uses a public image, review the **Networking features** tab for your OS version on the [Operating system details](/compute/docs/images/os-details#network-features) page. Make sure it shows that Jumbo Frames are completely supported.\n2. If the public image doesn't fully support Jumbo Frames, or if you are using a custom OS image, then the installed version of the gVNIC driver is too old, and doesn't support the higher MTU values. Follow the instructions in the section \"[Use on non-supported operating systems](/compute/docs/networking/using-gvnic#manual-gvnic-setup)\" to update the gVNIC driver for your compute instance.\n3. After updating the gVNIC driver, restart the instance and recheck the MTU configuration.\n\n### Poor networking throughput for Windows Server 2022 and Windows 11 VMs\n\nYou might experience poor networking throughput when using\n[Google Virtual NIC (gVNIC)](/compute/docs/networking/using-gvnic) with\nWindows Server 2022 and Windows 11 VMs that use gVNIC driver GooGet package\nversion `1.0.0@44` or earlier.\n\nTo resolve this issue, update the gVNIC driver GooGet package to version\n`1.0.0@45` or later by doing the following:\n\n1. Check which driver version is installed on your VM by running the following\n command from an administrator Command Prompt or Powershell session:\n\n ```\n googet installed\n ```\n\n The output looks similar to the following: \n\n ```\n Installed packages:\n ...\n google-compute-engine-driver-gvnic.x86_64 VERSION_NUMBER\n ...\n ```\n2. If the `google-compute-engine-driver-gvnic.x86_64` driver version is\n `1.0.0@44` or earlier, update the update the\n [GooGet package repository](https://github.com/google/googet)\n by running the following command from an administrator Command Prompt or\n Powershell session:\n\n ```\n google-compute-engine-driver-gvnic.x86_64\n ```"]]
