Troubleshooting gVNIC

Here are some tips to help troubleshoot the Compute Engine virtual network interface ( also known as gVNIC).

VM instance didn't boot

  • Cause: Compute Engine virtual network driver is not enabled on the image.

  • Diagnosis: Check that the image has Compute Engine virtual network interface enabled. To verify, run the following command:

    gcloud beta compute images describe image-name

    Replace image-name with the name of your image.

    The output of the command should show 'GVNIC' under guestOsFeatures.

  • Resolution: Ensure that you are using a supported image or that you have properly set up the gVNIC driver on your custom image.

VM instance booted but is not reachable over the network

  • Cause: The Compute Engine virtual network driver was not successfully installed and loaded.

  • Diagnosis: To check if the driver was installed and loaded, complete the following 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.ko
      version:        1.0.0
      license:        Dual MIT/GPL
      description:    gVNIC Driver
      author:         Google, XXX.
      srcversion:     5FEFB9DD945EB2DEC94EE09
      alias:          pci:v00001AE0d00000042sv*sd*bc*sc*i*
      depends:
      retpoline:      Y
      name:           gve
      vermagic:       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 through SAC.
    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 text Original File Name : gvnic.inf in the output.
      • If the driver is not installed, no message is returned.
  • Resolution: If the Compute Engine virtual network driver is not available, ensure that you are using a supported image or that you have properly set up the Compute Engine virtual network driver on your custom image.