This repository has been archived by the owner on May 6, 2020. It is now read-only.
Document why "unrestricted_guest" is checked for #421
Assignees
Labels
Comments
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Aug 14, 2017
The `cc-check` command requires the "unrestricted_guest" KVM feature. This is used as a heuristic to determine if the system is new enough to run a Clear Container. Fixes clearcontainers#421. Signed-off-by: James O. D. Hunt <[email protected]>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 4, 2017
The `cc-check` command requires the "unrestricted_guest" KVM feature. This is used as a heuristic to determine if the system is new enough to run a Clear Container. Fixes clearcontainers#421. Signed-off-by: James O. D. Hunt <[email protected]>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Jan 30, 2018
The `cc-check` command requires the "unrestricted_guest" KVM feature. This is used as a heuristic to determine if the system is new enough to run a Clear Container. Fixes clearcontainers#421. Signed-off-by: James O. D. Hunt <[email protected]>
mcastelino
pushed a commit
to mcastelino/runtime
that referenced
this issue
Dec 6, 2018
versions: Update kernel to version 4.14.51
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
cc-checkrequires the KVM featureunrestricted_guest. This is a heuristic used to ensure the host system is "new enough" to run a Clear Container.See: intel/cc-oci-runtime#950 (comment)
The text was updated successfully, but these errors were encountered: