[meta-virtualization] [PATCH 1/2] linux-yocto: added kernel configuration for KVM

Raymond Danks ray.danks at se-eng.com
Mon Jan 7 10:31:34 PST 2013


On 01/07/2013 11:10 AM, Bruce Ashfield wrote:
>
>
>
> On Mon, Jan 7, 2013 at 12:26 PM, Raymond Danks <ray.danks at se-eng.com 
> <mailto:ray.danks at se-eng.com>> wrote:
>
>     I'm going to show my lack of knowledge in this area, but I know
>     this is going to come up when I push a xen.cfg that I apparently
>     never added.
>
>     Is it possible to do something along the lines of PACKAGE_CONFIG
>     in the linux-yocto.bbappend?  For example, in the libvirt package
>     one can use PACKAGE_CONFIG to construct a "minimal" build of
>     libvirt.  What would be the method for one to do the same in this
>     package?
>
>
> kernel configuration fragment use are controlled via the 
> KERNEL_FEATURES variable, and
> for anything pre-yocto 1.4 that means an in-tree kernel configuration 
> fragment (I'm still pushing
> for the fragments to be maintained in tree, since that allows them to 
> be reused and maintained
> more easily).
>
> KERNEL_FEATURES is managed like any other variable in the system, 
> including updating
> it via optional/dynamic features as we see fit.

Thanks Bruce.  Yes, KERNEL_FEATURES is what I was looking for, I 
believe.  I'm seeing some references and examples for this now.

Ray

>
>
>     Yes, I imagine that worst case there can be a SRC_URI_distro
>     definition that includes only the .scc files required for that
>     "minimal" image build, but it seems like we want to keep away from
>     that as much as possible being that this isn't a distro layer.
>
>
> Typically we do this via a base KERNEL_FEATURES specification in the 
> relevant recipe(s), and
> distros, or other configurations can override/extend it as required.
>
> Cheers,
>
> Buce
>
>     Thanks,
>     Ray
>
>
>     On 01/07/2013 05:08 AM, Mihai Prica wrote:
>
>         Signed-off-by: Mihai Prica <mihai.prica at intel.com
>         <mailto:mihai.prica at intel.com>>
>         ---
>           recipes-kernel/linux/linux-yocto/kvm-enable.scc |    4 ++++
>           recipes-kernel/linux/linux-yocto/kvm.cfg        |    4 ++++
>           recipes-kernel/linux/linux-yocto_3.4.bbappend   |    1 +
>           3 files changed, 9 insertions(+)
>           create mode 100644
>         recipes-kernel/linux/linux-yocto/kvm-enable.scc
>           create mode 100644 recipes-kernel/linux/linux-yocto/kvm.cfg
>
>         diff --git a/recipes-kernel/linux/linux-yocto/kvm-enable.scc
>         b/recipes-kernel/linux/linux-yocto/kvm-enable.scc
>         new file mode 100644
>         index 0000000..0b5f4fc
>         --- /dev/null
>         +++ b/recipes-kernel/linux/linux-yocto/kvm-enable.scc
>         @@ -0,0 +1,4 @@
>         +define KFEATURE_DESCRIPTION "Enable KVM host support"
>         +define KFEATURE_COMPATIBILITY board
>         +
>         +kconf non-hardware kvm.cfg
>         diff --git a/recipes-kernel/linux/linux-yocto/kvm.cfg
>         b/recipes-kernel/linux/linux-yocto/kvm.cfg
>         new file mode 100644
>         index 0000000..0cfcf58
>         --- /dev/null
>         +++ b/recipes-kernel/linux/linux-yocto/kvm.cfg
>         @@ -0,0 +1,4 @@
>         +CONFIG_KVM=y
>         +CONFIG_KVM_INTEL=y
>         +CONFIG_KVM_AMD=y
>         +CONFIG_TUN=y
>         diff --git a/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         b/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         index 5b163ff..71bead2 100644
>         --- a/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         +++ b/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         @@ -4,5 +4,6 @@ SRC_URI += "file://xt-checksum.scc \
>                       file://ebtables.scc \
>                     file://vswitch.scc \
>                     file://lxc.scc \
>         +            file://kvm-enable.scc \
>                     "
>
>
>     _______________________________________________
>     meta-virtualization mailing list
>     meta-virtualization at yoctoproject.org
>     <mailto:meta-virtualization at yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
>
>
> -- 
> "Thou shalt not follow the NULL pointer, for chaos and madness await 
> thee at its end"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-virtualization/attachments/20130107/002d2eae/attachment.html>


More information about the meta-virtualization mailing list