4 ms·
A sample for it: https://github.com/microsoft/dotnet-computevirtualization https://github.com/microsoft/dotnet-computevirtualization The docs (which are a bit
by my123 5y ago
A sample for it: https://github.com/microsoft/dotnet-computevirtualization https://github.com/microsoft/dotnet-computevirtualization
The docs (which are a bit useful): https://docs.microsoft.com/en-us/virtualization/api/hcs/overview https://docs.microsoft.com/en-us/virtualization/api/hcs/over...
- anaisbetts 5y agoI'm sure that now that OP has found out he is wrong, he'll update his tired anti-MS rhetoric, right? Right? (cue Star Wars Padme meme)
- niea_11 5y agoHe may be partly right. The sample code is 4 years old. But the documentation is recent (at least the url linked by gp) : After 2021 june 27 : https://web.archive.org/web/20210627204757/https://docs.microsoft.com/en-us/virtualization/api/ https://web.archive.org/web/20210627204757/https://docs.micr... Before 2021 june 27 : https://web.archive.org/web/20210414223813/https://docs.microsoft.com/en-us/virtualization/api/ https://web.archive.org/web/20210414223813/https://docs.micr...
- muststopmyths 5y agoHave you actually looked at the samples ? You have no information about what is actually required on the guest OS side to make it launchable by HCS. It launches an OS (Windows) that already knows how to interface with HCS. As I said, the docker hcs shim might help one figure everything out, but that's not documentation. Edit: removed unnecessary flaming
- muststopmyths 5y agoAs far as I could divine a few years ago from the code in this repo, a deep dive into the OCI (Open Container Initiative) spec and the docker hcs shim should make it possible to figure this stuff out. I ran out of patience though and wish it was better documented.