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

Thu Jan 10 05:39:53 PST 2013

On Thu, Jan 10, 2013 at 2:32 AM, Lei Yang <lei.yang at windriver.com> wrote:

>  On 01/10/2013 03:43 AM, Prica, Mihai wrote:
>
>   On Tue, Jan 8, 2013 at 1:45 PM, Prica, Mihai <mihai.prica at intel.com>
> 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.****
>
> ** **
>
> ** **
>
> You are presumably going to enable the in tree fragments by appending to
> KERNEL_FEATURES****
>
> in the linux-yocto_3.4.bbappend. Which to me, seems like the right place
> to also add the****
>
> RRECOMMENDS. Or had you tried this and it didn't work for some reason I'm
> missing at the****
>
> moment (it's late here, and I've spent all day hunting autobuilderbreakage) :)
> ****
>
> ** **
>
> It doesn’t work in the kernel recipe. I’ve talked with Richard and he said
> PACKAGE_INSTALL_ATTEMPTONLY can ****
>
> be used for this in the image recipe. He said he will add a new
> IMAGE_INSTALL_RECOMMEND option for this. ****
>
> ** **
>
> There is however one more thing. Which is the best way to configure the
> modules to be loaded at boot-time? I****
>
> saw some discussion on the mailing list about update-modules becoming
> obsolete.****
>
> ** **
>
>
> I think "module_autoload_iwlwifi = "iwlwifi" " is your choice
>

That's the method that use as well, but it is tied into update-modules. I
remember the
other thread as well, I'll follow up there.

Cheers,

Bruce

>
> Lei
>
>
>
>
>    Thanks,****
>
> Mihai****
>
> ** **
>
> Cheers,****
>
> ** **
>
> Bruce****
>
>  ****
>
>   ****
>
> 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>
> 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>
> ---
>   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.sccb/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
> https://lists.yoctoproject.org/listinfo/meta-virtualization****
>
>
>
> ****
>
>  ****
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end" ****
>
>  ****
>
>
>
> ****
>
> ** **
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end" ****
>
>
> _______________________________________________
> meta-virtualization mailing listmeta-virtualization at yoctoproject.orghttps://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/20130110/247767cc/attachment.html>