It means their memory isolation is using hardware accelerated extensions. I would imagine it's still shared kernel and thus not "virtual machines". It makes se

It means their memory isolation is using hardware accelerated extensions. I would imagine it's still shared kernel and thus not "virtual machines". It makes sense for their container solution to make use of existing Hyper-V components like the virtual switch etc. But for that to be possible it's likely they needed to make use of VT-x and VT-d (if using stuff like hardware accelerated network device isolation like SRIOV). If anything this is closer to Bromium [1] than anything else. Will be interesting to see if this requires Hyper-V to be running in Type-1 mode (or if this will be the default in upcoming Windows versions) or if they are able to make use of the virtualisation extensions without actually running the host as a Hyper-V partition. So much cool stuff to hear about at BUILD. [1] http://www.bromium.com/ http://www.bromium.com/