Summary: | app-emulation/libvirt should not require several kernel configuration options | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jan Matějka (RETIRED) <yac> |
Component: | Current packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | virtualization |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jan Matějka (RETIRED)
![]() please attach kernel configuration You're building with a number of USE flags that do in fact require those options. Firstly you are building with LXC support, which heavily uses cgroups so the following options are required by that: * CONFIG_CGROUP_DEVICE: is not set when it should be. * CONFIG_BLK_CGROUP: is not set when it should be. * CONFIG_DEVPTS_MULTIPLE_INSTANCES: is not set when it should be. * CONFIG_VETH: is not set when it should be. * CONFIG_MEMCG: is not set when it should be. * CONFIG_MEMCG: is not set when it should be. (While virtual ethernet devices aren't cgroup related it is how LXC containers get ethernet adapters and each LXC instance needs its own /dev/pts so that's why you've got that.) You are also building with libvirt managed networking, which allows it to do a number of things with network traffic, which requires: * CONFIG_BRIDGE_NF_EBTABLES: is not set when it should be. * CONFIG_NETFILTER_XT_TARGET_CHECKSUM: is not set when it should be. Now you might argue "But I made a VM without needing those" and you might be correct but in the course of using those APIs from libvirt, they will need these kernel features so we can't really no-op one function and not the whole API. |