Forum Discussion
Will LCOW count as Hyper-V containers for the licensing model?
- Nov 16, 2017
The document you originally linked to is a licensing guide for Windows Server 2016, not the version 1709 release - as such, it's no longer accurate.
In terms of whether LCOW containers count... no, they don't. That rule is in place because Standard edition only includes the rights to virtualize two instances of the OS on top of the physical host, for every time you license the cores on the host. Since LCOW isn't using virtualized Windows Server underneath it, there's no applicability, and no hard limit as there was when Hyper-V Containers first shipped and could only run Windows. (But that limit still applies if you're using Hyper-V Containers on Windows).
Thanks for your answer. It comes down though to whether LCOW containers are seen as Hyper-V containers or not, since they're a kind of special implementation using LinuxKit as a small linux kernel to run linux based payloads through Hyper-V. No real VM gets spun up in the background, so I'm not sure if this is equivalent to "running as much Linux VM's through Hyper-V" as you'd like. I guess so?
The document you originally linked to is a licensing guide for Windows Server 2016, not the version 1709 release - as such, it's no longer accurate.
In terms of whether LCOW containers count... no, they don't. That rule is in place because Standard edition only includes the rights to virtualize two instances of the OS on top of the physical host, for every time you license the cores on the host. Since LCOW isn't using virtualized Windows Server underneath it, there's no applicability, and no hard limit as there was when Hyper-V Containers first shipped and could only run Windows. (But that limit still applies if you're using Hyper-V Containers on Windows).