Go to file
Paul Barker ea4ea5fbc3 netns: Use correct go toolchain
If we don't explicitly set the GO variable as an argument to make then
the native go toolchain is invoked instead of the cross-toolchain we
actually want. This can result in a netns binary which is built for the
wrong architecture.

Signed-off-by: Paul Barker <paul@betafive.co.uk>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2019-01-10 13:08:44 -05: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: uprev from 3.0.3 to 3.1.0 2019-01-10 13:08:41 -05:00
recipes-core kata: WIP 2018-11-05 10:22:54 -05:00
recipes-devtools add the py2 version for python-docker and python-docker-pycreds packages 2018-12-21 08:46:14 -05:00
recipes-extended xen: Amend do_install for FHS 3.0. 2018-12-12 14:16:12 -05: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 linux-yocto: cleanup lxc.cfg kernel config fragment 2019-01-10 13:08:38 -05:00
recipes-networking netns: Use correct go toolchain 2019-01-10 13:08:44 -05: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: add optional dependency on meta-cloud-services 2018-12-04 18:15:20 -05: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

Required for Ceph: URI: git://git.yoctoproject.org/meta-cloud-services 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.