Go to file
Mark Hatle 2672520983 openvswitch: Make openvswitch a machine_arch package
Openvswitch recipe depends on the kernel source, which is machine specific.
It can then use this machine specific resource to configure and build the
recipe.  This mix causes the hash values of this package to change based on
the machine, so this package must also be a machine_arch package.

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-10-18 11:43:20 -04:00
classes sanity-meta-virt: Watch for SanityCheck event 2017-10-12 21:59:51 -04:00
conf layer: add thud to compatible releases 2018-09-30 21:27:54 -04:00
docs openvswitch: uprev to 1.10 and documentation update. 2013-06-03 18:07:39 -04:00
files fs-perms-nagios.txt: add perms conf file 2018-09-06 12:45:17 -04:00
recipes-containers lxc: make error report compatible with ptest 2018-10-16 10:25:40 -04:00
recipes-core lxc: Make named avoid listening on lxc network interface 2018-09-11 16:06:11 -04:00
recipes-devtools python-webob:1.7.3.bb->1.8.2 2018-09-05 16:40:00 -04:00
recipes-extended libvirt: remove qemu from PACKAGECONFIG for mips n32 and n64 2018-10-18 11:37:55 -04:00
recipes-graphics/xorg-xserver xen-guest-image-minimal: Fix non-x86. Select x11 via IMAGE_FEATURES. 2017-09-19 09:22:55 -04:00
recipes-kernel/linux kernel: forcedly load nf_conntrack_ipv6 to work around kernel module loading failure 2018-09-30 21:31:16 -04:00
recipes-networking openvswitch: Make openvswitch a machine_arch package 2018-10-18 11:43:20 -04:00
.gitignore Added .gitignore file 2012-12-07 15:32:31 +01:00
COPYING.MIT Initial meta-xen layer documentation. 2012-06-21 15:51:11 -06:00
README README: cleanup list of maintainers 2018-05-24 16:08:02 -04:00

meta-virtualization

This layer provides support for building Xen, KVM, Libvirt, and associated packages necessary for constructing OE-based virtualized solutions.

The bbappend files for some recipes (e.g. linux-yocto) in this layer need to have 'virtualization' in DISTRO_FEATURES to have effect. To enable them, add in configuration file the following line.

DISTRO_FEATURES_append = " virtualization"

If meta-virtualization is included, but virtualization is not enabled as a distro feature a warning is printed at parse time:

You have included the meta-virtualization layer, but
'virtualization' has not been enabled in your DISTRO_FEATURES. Some bbappend files
may not take effect. See the meta-virtualization README for details on enabling
virtualization support.

If you know what you are doing, this warning can be disabled by setting the following variable in your configuration:

SKIP_META_VIRT_SANITY_CHECK = 1

Depending on your use case, there are other distro features in meta-virtualization that may also be enabled:

  • xen: enables xen functionality in various packages (kernel, libvirt, etc)
  • kvm: enables KVM configurations in the kernel and autoloads modules
  • aufs: enables aufs support in docker and linux-yocto
  • x11: enable xen and libvirt functionality related to x11
  • selinux: enables functionality in libvirt and lxc
  • systemd: enable systemd services and unit files (for recipes for support)
  • sysvinit: enable sysvinit scripts (for recipes with support)

Dependencies

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: master revision: HEAD prio: default

URI: git://github.com/openembedded/meta-openembedded.git branch: master revision: HEAD layers: meta-oe meta-networking meta-filesystems meta-python

BBFILE_PRIORITY_openembedded-layer = "4"

Required for Xen XSM policy: URI: git://git.yoctoproject.org/meta-selinux branch: master revision: HEAD prio: default

Maintenance

Send pull requests, patches, comments or questions to meta-virtualization@yoctoproject.org

Maintainer: Bruce Ashfield bruce.ashfield@gmail.com

When sending single patches, please using something like: $ git send-email -1 -M --to meta-virtualization@yoctoproject.org --subject-prefix='meta-virtualization][PATCH'

License

All metadata is MIT licensed unless otherwise stated. Source code included in tree for individual recipes is under the LICENSE stated in each recipe (.bb file) unless otherwise stated.