←back to thread

343 points cvallejo | 1 comments | | HN request time: 0.203s | source
Show context
boulos ◴[] No.22357462[source]
Disclosure: I work on Google Cloud.

cvallejo is the PM, so ask her anything!

replies(3): >>22357543 #>>22359291 #>>22360897 #
JoshTriplett ◴[] No.22357543[source]
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?

replies(2): >>22357620 #>>22357757 #
boulos ◴[] No.22357620[source]
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/

replies(2): >>22357723 #>>22357725 #
QUFB ◴[] No.22357723[source]
Speaking of nested virtualization, are there any plans to support this on E2, or will we have to use other instance types?
replies(1): >>22359201 #
1. boulos ◴[] No.22359201[source]
The blocker here would be the need for supporting nested on AMD parts (as E2 can choose between Intel and AMD parts).