Common errors

The following issue occurs when the image used to create the VMis not tagged to use 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 withGVNIC GuestOsFeature.

To resolve this issue, ensure that you are using an image that is tagged to use gVNIC.For more information, seeCreate a custom image.

Other issues

This section contains other errors that you might encounter when using thegVNIC driver with your Compute Engine instance.

VM instance didn't boot

• Cause: gVNIC is not enabled on the image.

• Diagnosis: Check that the image hasgVNIC enabled.To verify, run the following command:

  gcloud compute images describeIMAGE_NAME

  ReplaceIMAGE_NAME with the name of your image.

  The output of the command should showGVNIC underguestOsFeatures.

  You can also check if the VM was created with thenic-type set togVNIC. To do this run the following command:

  gcloud compute instances describeVM_NAME

  ReplaceVM_NAME with the name of your VM.

• Resolution: Ensure that you are using asupported image or that you have properlyset up the gVNIC driver on your custom image.

VM instance booted but is not reachable over the network

• Cause: gVNIC was not successfully installed and loaded.

• Diagnosis: To check if the driver was installed and loaded, complete thefollowing steps:

  Linux

  1. Check that the driver is installed.

     modinfo gve

     The output should resemble the following:

     filename:       /lib/modules/4.15.0-1036-gcp/updates/dkms/gve.koversion:        1.1.0license:        Dual MIT/GPLdescription:    gVNIC Driverauthor:         Google, XXX.srcversion:     5FEFB9DD945EB2DEC94EE09alias:          pci:v00001AE0d00000042sv*sd*bc*sc*i*depends:retpoline:      Yname:           gvevermagic:       4.15.0-1036-gcp SMP mod_unload

  2. Check that the driver is loaded.

     lsmod | grep gve

     The output should resemble the following:

     gve                    49152  0

  Windows

  1. Connect to instance throughSAC.
  2. Login with your username and password.

  3. From the command prompt, run the following command:

     dism /online /get-drivers | findstr gvnic

  4. Review the result.

     • If the driver is installed, you should see the textOriginal File Name : gvnic.inf in the output.
     • If the driver is not installed, no message is returned.
  Note: You can also review theinteractive serial consolewhen debugging issues with your connection.

• Resolution: If gVNIC is notavailable, ensure that you are using asupported image or thatyou have properlyset up gVNICon your custom image.

MTU value set in VPC not being used by compute instance

After following the instructions tochange the MTU value, the MTUconfiguration on the instance isn't using the same MTU value. For example,you might run the/sbin/ifconfig | grep mtu command on your instance to checkthe MTU setting. You have restarted the instance, but the instanceconfiguration isn't updated.

Cause: The gVNIC driver version is too old

Resolution:

1. If your instance uses a public image, review theNetworking features tabfor your OS version on theOperating system detailspage. Make sure it shows that Jumbo Frames are completely supported.
2. If the public image doesn't fully support Jumbo Frames, or if you are usinga custom OS image, then the installed version of the gVNIC driver istoo old, and doesn't support the higher MTU values. Follow theinstructions in the section"Use on non-supported operating systems"to update the gVNIC driver for your compute instance.
3. After updating the gVNIC driver, restart the instance and recheck the MTUconfiguration.

Poor networking throughput for Windows Server 2022 and Windows 11 VMs

You might experience poor networking throughput when usingGoogle Virtual NIC (gVNIC) withWindows Server 2022 and Windows 11 VMs that use gVNIC driver GooGet packageversion1.0.0@44 or earlier.

To resolve this issue, update the gVNIC driver GooGet package to version1.0.0@45 or later by doing the following:

1. Check which driver version is installed on your VM by running the followingcommand from an administrator Command Prompt or Powershell session:

   googet installed

   The output looks similar to the following:

   Installed packages:  ...  google-compute-engine-driver-gvnic.x86_64 VERSION_NUMBER  ...

2. If thegoogle-compute-engine-driver-gvnic.x86_64 driver version is1.0.0@44 or earlier, update the driver from theGooGet package repositoryby running the following command from an administrator Command Prompt orPowershell session:

   googet install google-compute-engine-driver-gvnic