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

[Lei Yang]

On 01/09/2013 02:45 AM, Prica, Mihai wrote:
>
> I didn't know about the configuration fragments from the kernel tree. 
> I'll redo the patch to use those.
>
> I see that the .cfg from the kernel tree enables kvm as modules. In 
> this situation, I think I need to add an extra RRECOMMENDS with the 
> necessary kernel-module-kvm to bring the necessary modules to the 
> sysroot.  Where would be the best places to add this, considering 
> there is no specific recipe for kvm? I tried to add them to the image 
> recipe but it didn't worked.
>

It often to add below line in conf/machine/**.conf, I don't see it in 
meta-virt, Bruce may give some better comments

MACHINE_EXTRA_RRECOMMENDS = "kernel-module-kvm"

and need to make sure the kvm moudles built with "M" first

Lei



> Thanks,
>
> Mihai
>
> *From:*meta-virtualization-bounces at yoctoproject.org 
> [mailto:meta-virtualization-bounces at yoctoproject.org] *On Behalf Of 
> *Raymond Danks
> *Sent:* Monday, January 07, 2013 8:32 PM
> *To:* Bruce Ashfield
> *Cc:* meta-virtualization at yoctoproject.org
> *Subject:* Re: [meta-virtualization] [PATCH 1/2] linux-yocto: added 
> kernel configuration for KVM
>
> 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:///%5C%5Cxt-checksum.scc> \
>     file://ebtables.scc <file:///%5C%5Cebtables.scc> \
>     file://vswitch.scc <file:///%5C%5Cvswitch.scc> \
>     file://lxc.scc <file:///%5C%5Clxc.scc> \
>     + file://kvm-enable.scc <file:///%5C%5Ckvm-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"
>
>
>
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-virtualization/attachments/20130109/193a4c1a/attachment.html>