다음 문제는 VM을 만드는 데 사용된 이미지에 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.
이 문제를 해결하려면 gVNIC를 사용하도록 태그가 지정된 이미지를 사용하고 있는지 확인하세요.
자세한 내용은 커스텀 이미지 만들기를 참조하세요.
기타 문제
이 섹션에서는 Compute Engine 인스턴스에서 gVNIC 드라이버를 사용할 때 발생할 수 있는 다른 오류를 설명합니다.
VM 인스턴스가 부팅되지 않음
원인: 이미지에서 gVNIC가 사용 설정되어 있지 않습니다.
진단: 이미지에 gVNIC가 사용 설정되어 있는지 확인하세요.
확인하려면 다음 명령어를 실행하세요.
gcloud compute images describe IMAGE_NAME
IMAGE_NAME를 이미지 이름으로 바꿉니다.
명령어를 실행하면 guestOsFeatures 아래에 GVNIC가 표시됩니다.
또한 nic-type이 gVNIC로 설정된 VM이 생성되었는지 확인할 수도 있습니다. 이렇게 하려면 다음 명령어를 실행합니다.
드라이버가 설치되어 있는 경우 출력에서 텍스트 Original File Name : gvnic.inf가 표시됩니다.
드라이버가 설치되어 있지 않으면 메시지가 표시되지 않습니다.
해결 방법: gVNIC를 사용할 수 없는 경우 지원되는 이미지를 사용 중인지 또는 커스텀 이미지에 올바르게 gVNIC를 설정했는지 확인하세요.
컴퓨팅 인스턴스에서 VPC에 설정된 MTU 값을 사용하지 않음
안내에 따라 MTU 값을 8896으로 변경한 후에 인스턴스의 MTU 구성에서 같은 MTU 값을 사용하지 않습니다. 예를 들어 인스턴스에서 /sbin/ifconfig | grep mtu 명령어를 실행하여 MTU 설정을 확인할 수 있습니다. 인스턴스를 다시 시작했지만 인스턴스 구성이 업데이트되지 않았습니다.
원인: gVNIC 드라이버 버전이 너무 오래되었습니다.
해결 방법:
인스턴스에서 공개 이미지를 사용하는 경우 운영체제 세부정보 페이지에서 OS 버전의 네트워킹 기능 탭을 검토합니다. 점보 프레임이 완전히 지원된다고 표시되는지 확인합니다.
공개 이미지가 점보 프레임을 완전히 지원하지 않거나 커스텀 OS 이미지를 사용하는 경우 설치된 gVNIC 드라이버 버전이 너무 오래되어 더 높은 MTU 값을 지원하지 않습니다. '지원되지 않는 운영체제에서 사용' 섹션의 안내에 따라 컴퓨팅 인스턴스의 gVNIC 드라이버를 업데이트합니다.
gVNIC 드라이버를 업데이트한 후 인스턴스를 다시 시작하고 MTU 구성을 다시 확인합니다.
Windows Server 2022 및 Windows 11 VM의 네트워킹 처리량 저하
gVNIC 드라이버 GooGet 패키지 버전 1.0.0@44 이하를 사용하는 Windows Server 2022 및 Windows 11 VM에서 Google Virtual NIC(gVNIC)를 사용하는 경우 네트워킹 처리량이 저하될 수 있습니다.
이 문제를 해결하려면 다음을 수행하여 gVNIC 드라이버 GooGet 패키지를 1.0.0@45 버전 이상으로 업데이트합니다.
관리자 명령 프롬프트 또는 Powershell 세션에서 다음 명령어를 실행하여 VM에 설치된 드라이버 버전을 확인합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-06-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 ```"]]
