aljaz/kata-containers
1
0
Fork 0
mirror of https://github.com/aljazceru/kata-containers.git synced 2026-01-03 14:34:21 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
7087d7ddc762fcc4f2c9c20d647a4eedac2a7ccd
kata-containers/kernel/configs
History
Archana Shinde e0a57b6a08 network: Enable ipv6 config CONFIG_IPV6_MULTIPLE_TABLES 
Although CONFIG_IPV6 is enabled, this additional config is
needed so that multiple route tables are used for ipv6.
Without this, the kernel adds routes for "fe80::/64"
with proto kernel in the main table instead of the
local routing table.
This makes the behaviour similar to regular containers.

Fixes #920

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
2020-01-24 16:14:22 -08:00
..
fragments
network: Enable ipv6 config CONFIG_IPV6_MULTIPLE_TABLES
2020-01-24 16:14:22 -08:00
arm64_kata_kvm_4.14.x
enable config CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE by default
2019-03-13 13:01:53 +08:00
arm64_kata_kvm_4.19.x
config: enable printk_time for arm64.
2019-12-12 23:33:28 +08:00
arm64_kata_kvm_5.4.x
kernel: Enable new LTS 5.4.3 on AArch64
2019-12-16 17:41:07 +08:00
powerpc_kata_kvm_4.14.x
ppc64le: enable kernel config options to enhance entropy
2019-06-19 18:53:19 +05:30
powerpc_kata_kvm_4.19.x
kernel: enable vsock on ppc64le
2019-08-21 14:50:37 +05:30
README.md
kernel: configs: update README
2019-07-25 18:13:03 +00:00
s390_kata_kvm_4.19.x
s390x: enable rnd hw generator option
2019-04-26 11:07:25 +02:00
x86_64_kata_kvm_4.14.x
enable config CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE by default
2019-03-13 13:01:53 +08:00
x86_64_kata_old_kernel_compat
kernel_config: add 4.1 kernel support
2018-08-25 09:00:05 +08:00

README.md

Kata Containers kernel config files

This directory contains Linux Kernel config files used to configure Kata Containers VM kernels.

Types of config files

This directory holds config files for the Kata Linux Kernel in two forms:

  • A tree of config file 'fragments' in the fragments sub-folder, that are constructed into a complete config file using the kernel scripts/kconfig/merge_config.sh script.
  • As complete config files that can be used as-is.

Kernel config fragments are the preferred method of constructing .config files to build Kata Containers kernels, due to their improved clarity and ease of maintenance over single file monolithic .configs.

How to use config files

The recommended way to set up a kernel tree, populate it with a relevant .config file, and build a kernel, is to use the build_kernel.sh script. For example:

$ ./build-kernel.sh setup

The build-kernel.sh script understands both full and fragment based config files.

Run ./build-kernel.sh help for more information.

How to modify config files

Complete config files can be modified either with an editor, or preferably using the kernel Kconfig configuration tools, for example:

$ cp x86_kata_kvm_4.14.x linux-4.14.22/.config
$ pushd linux-4.14.22
$ make menuconfig
$ popd
$ cp linux-4.14.22/.config x86_kata_kvm_4.14.x

Kernel fragments are best constructed using an editor. Tools such as grep and diff can help find the differences between two config files to be placed into a fragment.

If adding config entries for a new subsystem or feature, consider making a new fragment with an appropriately descriptive name.

The fragment gathering tool perfoms some basic sanity checks, and the build-kernel.sh will fail and report the error in the cases of:

  • A duplicate CONFIG symbol appearing.
  • A CONFIG symbol being in a fragment, but not appearing in the final .config
    • which indicates that CONFIG variable is not a part of the kernel Kconfig setup, which can indicate a typing mistake in the name of the symbol.
  • A CONFIG symbol appearing in the fragments with multiple different values.