Go to file
Bruce Ashfield 0257d67a89 qemu: change packaging when vmsep is enabled
When hosts are using VM separation features, they need qemu
on the target to launch guests (and for other purposes) .. but
they do not want *all* of the build qemu targets. To allow a
more fine grained installation off qemu components, this patch
splits packaging into:

  - qemu-<arch>
  - qemu-support
  - qemu-keymaps

Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com>
2019-12-17 18:07:33 -08:00
classes containers: introduce image-oci 2019-02-27 11:46:25 -05:00
conf conf: add warrior to layer compat 2019-04-02 02:45:25 -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 templates/lxc-download.in: Use curl instead of wget 2019-09-20 00:43:26 -04:00
recipes-core libxycrypt: build static libraries if 'vmsep' is in distro_features 2019-12-17 17:36:17 -08:00
recipes-devtools qemu: change packaging when vmsep is enabled 2019-12-17 18:07:33 -08:00
recipes-extended libvirt: Five security fixes 2019-09-09 13:26:51 -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: drop 4.18 bbappend 2019-04-09 11:43:43 -04:00
recipes-networking netns: Upgrade to v0.5.3 2019-05-01 15:39:29 -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: update mailing list address 2019-11-22 08:02:58 -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@lists.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@lists.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.