f63f0912c6
Fixed typo in LetsEncrypt example Removed duplicate Datanet entry from main index.rst Reworked Use Kubernetes CPU Manager Static Policy prerequisite block. Restored fault/index version of FM toctree in top-level index. Added merged doc entries to top level index.rst. Incorporated review comments. Also some generic formatting clean-up such as converting abbreviations to rST-style :abbr: markup. Moved url with embedded substitution out of code-block. Addressed patch 2 review comments. Some addtional rST tidying. See comment replies for open questions/issues. This patch fixes an issue with 'stx' in filenames that may differ downstream using-an-image-from-the-local-docker-registry-in-a-container-spec new substitution and changing code-blocks to parsed-literals as required. Initial submission for review. Note that a couple of references to WR persist in examples. These will be marked up with comments in the review. Signed-off-by: Stone <ronald.stone@windriver.com> Change-Id: I1efef569842caff5def9dc00395b594d91d7a5d0 Signed-off-by: Stone <ronald.stone@windriver.com>
1.4 KiB
1.4 KiB
Known Kata Container Limitations
This section describes the known limitations when using Kata containers.
SR-IOV Support
A minimal kernel and rootfs for
Kata containers are shipped with , and are present at
/usr/share/kata-containers/. To enable certain kernel features such as
IOMMU (I/O memory management unit), and desired
network kernel modules, a custom kernel image, and rootfs has to be
built. For more information, see https://katacontainers.io/.
CPU Manager Support
Kata containers currently occupy only the platform cores. There is no
CPU (Central Processing Unit) manager support.
Hugepages
- Similar to the SR-IOV limitation, hugepage support must be configured in a custom Kata kernel.
- The size and number of hugepages must be written using the
io.katacontainers.config.hypervisor.kernel\_paramsannotation. - Creating a hugetlbfs mount for hugepages in the Kata container is specific to the end user application.