Masalah berikut terjadi jika image yang digunakan untuk membuat VM
tidak diberi tag untuk menggunakan 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.
Untuk mengatasi masalah ini, pastikan Anda menggunakan image yang diberi tag untuk menggunakan gVNIC.
Untuk mengetahui informasi selengkapnya, lihat Membuat image kustom.
Masalah lainnya
Bagian ini berisi error lain yang mungkin Anda alami saat menggunakan driver gVNIC dengan instance Compute Engine.
Instance VM tidak dapat di-booting
Penyebab: gVNIC tidak diaktifkan pada image.
Diagnosis: Pastikan image telah mengaktifkan gVNIC.
Untuk memverifikasi, jalankan perintah berikut:
gcloud compute images describe IMAGE_NAME
Ganti IMAGE_NAME dengan nama image Anda.
Output perintah akan menampilkan GVNIC di bagian guestOsFeatures.
Anda juga dapat memeriksa apakah VM dibuat dengan nic-type yang disetel ke
gVNIC. Untuk melakukannya, jalankan perintah berikut:
Jika driver terinstal, Anda akan melihat teks
Original File Name : gvnic.inf di output.
Jika driver tidak diinstal, tidak ada pesan yang ditampilkan.
Resolusi: Jika gVNIC tidak
tersedia, pastikan Anda menggunakan
image yang didukung atau
Anda telah
menyiapkan gVNIC
dengan benar pada image kustom Anda.
Nilai MTU yang ditetapkan di VPC tidak digunakan oleh instance komputasi
Setelah mengikuti petunjuk untuk
mengubah nilai MTU, konfigurasi MTU
di instance tidak menggunakan nilai MTU yang sama. Misalnya,
Anda dapat menjalankan perintah /sbin/ifconfig | grep mtu di instance untuk memeriksa
setelan MTU. Anda telah memulai ulang instance, tetapi konfigurasi instance tidak diperbarui.
Penyebab: Versi driver gVNIC terlalu lama
Penyelesaian:
Jika instance Anda menggunakan image publik, tinjau tab Networking features
untuk versi OS Anda di
halaman Operating system details. Pastikan Jumbo Frames sepenuhnya didukung.
Jika image publik tidak sepenuhnya mendukung Jumbo Frames, atau jika Anda menggunakan
image OS kustom, versi driver gVNIC yang diinstal
terlalu lama, dan tidak mendukung nilai MTU yang lebih tinggi. Ikuti
petunjuk di bagian
"Penggunaan pada sistem operasi yang tidak didukung"
untuk mengupdate driver gVNIC untuk instance komputasi Anda.
Setelah mengupdate driver gVNIC, mulai ulang instance dan periksa kembali konfigurasi
MTU.
Throughput jaringan yang buruk untuk VM Windows Server 2022 dan Windows 11
Anda mungkin mengalami throughput jaringan yang buruk saat menggunakan
Google Virtual NIC (gVNIC) dengan
VM Windows Server 2022 dan Windows 11 yang menggunakan paket GooGet driver gVNIC
versi 1.0.0@44 atau sebelumnya.
Untuk mengatasi masalah ini, update paket GooGet driver gVNIC ke versi
1.0.0@45 atau yang lebih baru dengan melakukan hal berikut:
Periksa versi driver yang terinstal pada VM dengan menjalankan perintah
berikut dari sesi Command Prompt atau Powershell administrator:
Jika versi driver google-compute-engine-driver-gvnic.x86_64 adalah
1.0.0@44 atau yang lebih lama, update
repositori paket GooGet
dengan menjalankan perintah berikut dari sesi Command Prompt atau
Powershell administrator:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 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 ```"]]
