Replies: 2 comments 5 replies
-
It appears so. I tried the following patch and could launch a GCP VM with gVNIC, as verified in the console: --- a/sky/skylet/providers/gcp/config.py
+++ b/sky/skylet/providers/gcp/config.py
@@ -693,6 +693,7 @@ def _configure_subnet(config, compute):
subnets = _list_subnets(config, compute, filter=f'(name="{usable_vpc_name}")')
default_subnet = subnets[0]
+ # https://cloud.google.com/compute/docs/reference/rest/v1/instances/insert#request-body
default_interfaces = [
{
"subnetwork": default_subnet["selfLink"],
@@ -702,6 +703,7 @@ def _configure_subnet(config, compute):
"type": "ONE_TO_ONE_NAT",
}
],
+ "nicType": "gVNIC",
}
] Could you verify if this gives the expected performance? If so, we could look into properly plumbing it through. |
Beta Was this translation helpful? Give feedback.
4 replies
-
Would love to see this feature as well! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In order to take advantage of distributed processing on GCP it looks you need to start the instance with GVNIC enabled. In the os I see that the modules are loaded and running but don't think it's working without this enabled. Is this possible.
https://cloud.google.com/compute/docs/gpus/optimize-gpus#high-bandwidth
Beta Was this translation helpful? Give feedback.
All reactions