5 ms·

Disclosure: I work on Google Cloud. cvallejo is the PM, so ask her anything!

by boulos 7y ago

JoshTriplett 7y ago
Does the new n2d machine type support nested virtualization? (Asking because Azure supports nested virtualization but only on some machine types. AWS doesn't support nested virtualization at all. Google Cloud seems to support nested virtualization on other machine types.) Also, why 224 rather than 256?
- boulos 7y ago
  We do not yet support AMD's nested implementation (we do on Intel). But cvallejo is also the PM for Nested :). As for 224, we've always reserved threads on each host for I/O and so on. Figure 2 from the Snap paper [1] is probably the best public reference. We also don't make it clear (on purpose) what size the underlying host processors are, though you can clearly guesstimate pretty easily. [1] https://research.google/pubs/pub48630/ https://research.google/pubs/pub48630/
  - QUFB 7y ago
    Speaking of nested virtualization, are there any plans to support this on E2, or will we have to use other instance types?
    - boulos 7y ago
      The blocker here would be the need for supporting nested on AMD parts (as E2 can choose between Intel and AMD parts).
  - JoshTriplett 7y ago
    > We do not yet support AMD's nested implementation (we do on Intel). Any particular reason for that limitation, or just "not implemented yet"? (Not asking for product roadmaps, just wondering if there's a specific technical issue that makes it more difficult to support.) > As for 224, we've always reserved threads on each host for I/O and so on. Figure 2 from the Snap paper [1] is probably the best public reference. That's helpful, thank you.
    - boulos 7y ago
      Not implemented yet. In the stack rank of “stuff needed to update our hypervisor for AMD again” it wasn’t at the top :). Note the again as well: GCE originally had it such that N in N1 meant iNtel, and A1 was for AMD (as Joe said publicly here: https://twitter.com/jbeda/status/1159891645531213824 https://twitter.com/jbeda/status/1159891645531213824). By the time I joined though, we didn’t see the point of the A1 parts, since the Sandybridge’s smoked them.
- deleted 7y ago
  [deleted]
outworlder 7y ago
Are those instances available to all customers yet? We don't see those in our console.
- boulos 7y ago
  See my other comment about the rollout proceeding now. You should see them sometime this week, in theory.
ksec 7y ago
I am pretty sure it is not Your / Google Cloud's fault given AWS and Azure are in similar situation here, but; ROME was announced in Later 2018, Released on Aug / September 2019. Why did it take another 6 months to roll out an new instance? When I assume you must have had samples since early 2019.

Disclosure: I work on Google Cloud. cvallejo is the PM, so ask her anything!

by boulos 7y ago

Disclosure: I work on Google Cloud. cvallejo is the PM, so ask her anything!

Does the new n2d machine type support nested virtualization? (Asking because Azure supports nested virtualization but only on some machine types. AWS doesn't support nested virtualization at all. Google Cloud seems to support nested virtualization on other machine types.) Also, why 224 rather than 256?

boulos 7y ago
We do not yet support AMD's nested implementation (we do on Intel). But cvallejo is also the PM for Nested :). As for 224, we've always reserved threads on each host for I/O and so on. Figure 2 from the Snap paper [1] is probably the best public reference. We also don't make it clear (on purpose) what size the underlying host processors are, though you can clearly guesstimate pretty easily. [1] https://research.google/pubs/pub48630/ https://research.google/pubs/pub48630/
- QUFB 7y ago
  Speaking of nested virtualization, are there any plans to support this on E2, or will we have to use other instance types?
  - boulos 7y ago
    The blocker here would be the need for supporting nested on AMD parts (as E2 can choose between Intel and AMD parts).
- JoshTriplett 7y ago
  > We do not yet support AMD's nested implementation (we do on Intel). Any particular reason for that limitation, or just "not implemented yet"? (Not asking for product roadmaps, just wondering if there's a specific technical issue that makes it more difficult to support.) > As for 224, we've always reserved threads on each host for I/O and so on. Figure 2 from the Snap paper [1] is probably the best public reference. That's helpful, thank you.
  - boulos 7y ago
    Not implemented yet. In the stack rank of “stuff needed to update our hypervisor for AMD again” it wasn’t at the top :). Note the again as well: GCE originally had it such that N in N1 meant iNtel, and A1 was for AMD (as Joe said publicly here: https://twitter.com/jbeda/status/1159891645531213824 https://twitter.com/jbeda/status/1159891645531213824). By the time I joined though, we didn’t see the point of the A1 parts, since the Sandybridge’s smoked them.
deleted 7y ago
[deleted]

outworlder 7y ago

Are those instances available to all customers yet? We don't see those in our console.

boulos 7y ago
See my other comment about the rollout proceeding now. You should see them sometime this week, in theory.

ksec 7y ago

I am pretty sure it is not Your / Google Cloud's fault given AWS and Azure are in similar situation here, but; ROME was announced in Later 2018, Released on Aug / September 2019. Why did it take another 6 months to roll out an new instance? When I assume you must have had samples since early 2019.