Line 8: |
Line 8: |
| ** <code>CONFIG_UTS_NS=y</code> (Namespaces support -> UTS namespace) | | ** <code>CONFIG_UTS_NS=y</code> (Namespaces support -> UTS namespace) |
| ** <code>CONFIG_IPC_NS=y</code> (Namespaces support -> IPC namespace) | | ** <code>CONFIG_IPC_NS=y</code> (Namespaces support -> IPC namespace) |
| + | ** <code>CONFIG_SYSVIPC_SYSCTL=y</code> |
| ** <code>CONFIG_PID_NS=y</code> (Namespaces support -> PID namespaces) | | ** <code>CONFIG_PID_NS=y</code> (Namespaces support -> PID namespaces) |
| ** <code>CONFIG_NET_NS=y</code> (Namespaces support -> Network namespace) | | ** <code>CONFIG_NET_NS=y</code> (Namespaces support -> Network namespace) |
Line 20: |
Line 21: |
| ** <code>CONFIG_NETLINK_DIAG=y</code> (Netlink socket -> Netlink: sockets monitoring interface) | | ** <code>CONFIG_NETLINK_DIAG=y</code> (Netlink socket -> Netlink: sockets monitoring interface) |
| * <code>CONFIG_NETFILTER_XT_MARK=y</code> (Networking support -> Networking options -> Network packet filtering framework (Netfilter) -> Core Netfilter Configuration -> Netfilter Xtables support (required for ip_tables) -> nfmark target and match support) | | * <code>CONFIG_NETFILTER_XT_MARK=y</code> (Networking support -> Networking options -> Network packet filtering framework (Netfilter) -> Core Netfilter Configuration -> Netfilter Xtables support (required for ip_tables) -> nfmark target and match support) |
| + | * <code>CONFIG_TUN=y</code> (Networking support -> Universal TUN/TAP device driver support) |
| | | |
| | | |
Line 32: |
Line 34: |
| * <code>CONFIG_IA32_EMULATION=y</code> (x86 only) (Executable file formats -> Emulations -> IA32 Emulation) | | * <code>CONFIG_IA32_EMULATION=y</code> (x86 only) (Executable file formats -> Emulations -> IA32 Emulation) |
| | | |
− | For some [[usage scenarios]] there is an ability to track memory changes and produce [[incremental dumps]]. Need to enable the <code>CONFIG_MEM_SOFT_DIRTY=y</code> (optional) (Processor type and features -> Track memory changes). | + | For some [[usage scenarios]] there is an ability to track memory changes and produce [[incremental dumps]]. Need to enable the <code>CONFIG_MEM_SOFT_DIRTY=y</code> (optional) (Processor type and features -> Track memory changes). In order to enable [[lazy migration]], the [[userfaultfd]] system call is required <code>CONFIG_USERFAULTFD=y</code> (optional) (General setup -> Enable userfaultfd() system call). |
| | | |
| In the beginning of the project we had our [[custom kernel]], which contained some experimental CRIU related patches. Nowadays this is almost not used. | | In the beginning of the project we had our [[custom kernel]], which contained some experimental CRIU related patches. Nowadays this is almost not used. |
| | | |
| [[Category: Building]] | | [[Category: Building]] |