Tweak the ptest build rule to look for artifacts in the build directory
instead of source, since build and source are split on the latest oe-core.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The installation of Google Protocol Buffers python header files
requires the ability to run the "protoc" compiler on the host to
generate the Python header files. This fix adds a native package
that builds Google Protocol Buffers for the host machine to provide
the compiler that is used to cross-compile the package for the target
machine.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Google Protocol Buffers includes some basic example applications to
show its functionality. This fix installs these examples to the
target system when the "test" feature is enabled in the configuration.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The recipe uses 4 spaces instead of tabs when indenting. The recipe
style guidelines indicate that tabs should be used instead. This
simple fix replaces the spaces with tabs where appropriate in the
recipe file.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The compiler generated by Google Protocol Buffers currently includes
support for Python bindings. However, currently the python files
required to use the generated files are not included on the system.
This fix installs the python header files using python setup-tools
after the compiler is built.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Upgrade Google Protocol Buffers to version 2.5.0. The previous
version 2.4.1 is getting quite old (released April 2011). The newer
version provides bug fixes and more functionality. This version adds
some speed optimization and the ability to allow multiple enum
symbols to have the same value.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The libvirt build would fail whenever x11 was in DISTRO_FEATURES and the host
didn't have polkit installed (either no polkit/policykit at all, or just old
policykit).
Ensure that libvirt uses polkit rather than policykit, whether the host has
pkcheck installed or not, and ensure the path is correct per our config.
Signed-off-by: Christopher Larson <kergoth@gmail.com>
Signed-off-by: Shrikant Bobade <Shrikant_Bobade@mentor.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Libvirt contains the functionality to run hooks when before and after
it performs specific operations. Hooks are useful in order to perform
actions on the host that occur outside of the VM. In order to enable
the hooks scripts must exist in a specific directory. This fix adds
the required directory to the file system.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Update lxc to latest available version: 1.0.5
Remove already upstreamed patches.
Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
meta-networking layer includes a newer version (0.2.3) of netcf recipe.
Since meta-virtualization layer depends on meta-oe/meta-networking layer,
we can avoid duplication by removing this recipe.
Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fix this warning:
WARNING: Function remove_packaging_data_files doesn't exist
The remove_packaging_data_files function is now handled automatically when
"package-management" is not in IMAGE_FEATURES. We should remove the lines,
as they are not needed and might interfere with correct operation of
postinstall scripts.
Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
libvirt can enable FUSE, which comes from meta-filesystems, so we should
add it as a layer in the README.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
libvirt will probe and dynamically add fuse support if detected. This
leads to build inconsistencies and errors due to race conditions.
Explicitly adding fuse as a packageconfig option to ensure that it
is consistently added (or removed).
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
In the updates to the new KERNEL_MODULE_AUTOLOAD format, openvswitch was
missed.
Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
commit kernel-module-split: Add support for KERNEL_MODULE_AUTOLOAD and KERNEL_MODULE_PROBECONF
in oe-core replaces module_autoload with KERNEL_MODULE_AUTOLOAD, so we must update
the linux-yocto bbappends.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The default PTEST_DIR only works for 32bit.
Signed-off-by: Mihaela Sendrea <mihaela.sendrea@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Updating to the latest OVS 2.x. Only minor patch refreshes required, and
no regressions were found during sanity testing.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
For now adding netcf to the list of "brokensep" packages. The install
phase fails when autotools split directories are used, so we inherit
brokensep to get things building again.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Updating the version of libvirt to 1.2.4. Only small changes are required
to the ptest and python chnages for this new version, but otherwise, all
packaging and build optinos are the same.
Sanity tests show no regressions from 1.2.2.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Poky commit 69b6eaca3d9b635e8a61a0fdbd814b558e91901d [autotools:
Enable separate builddir by default] enforced separate build
directories, which is supported by automake. Make some minor updates
to the recipes and upstream source to allow builds to work with
separated src and build directories.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Poky commit 69b6eaca3d9b635e8a61a0fdbd814b558e91901d [autotools:
Enable separate builddir by default] enforced separate build
directories, which is supported by automake. Unfortunately lxc had a
few make directives which didn't take into account VPATH builds so
fixing them up here to allow the lxc build to complete successfully.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
We add a PACKAGECONFIG[] to deterministically build with
or without libssh2 and add ssh2 to PACKAGECONFIG, so we will
always use it.
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
configure will check for numa support by default, resulting
in indeterminate configuration. We add a PACKAGECONFIG[]
to force behavior.
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Install lxc test suite and run it as ptest.
Signed-off-by: Mihaela Sendrea <mihaela.sendrea@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Now that the 3.14 kernel has been introduced and 3.8 dropped from oe-core,
we need to adjust our configuration fragments accordingly.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Adding a couple of upstream fixes for lxc:
- follow symlinks when determining if Busybox is statically linked
- don't fail for lxc.network.type = none
- don't fail if no default macvlan mode is specified
More details are available in the individual patches.
Signed-off-by: Bogdan Purcareata <bogdan.purcareata@freescale.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Install openvswitch test suite and run it as ptest.
Signed-off-by: Radu Patriu <radu.patriu@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Install libvirt test suite and run it as ptest.
Signed-off-by: Mihaela Sendrea <mihaela.sendrea@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
By default dnsmaqs binds to all interfaces, and this causes 2
small issues:
* At boot time, dnsmaqs daemon will start first and binds to virbr
interface, then libvirtd spawns a second dnsmaqs binds to virbr
(in dynamic mode) which binds to virbr:53 proto UDP (but not TCP)
* If some how, libvirtd daemon starts first then dnsmaqs daemon
will fail to start as libvirtd daemon already binds to virbr:53.
This patch tells dnsmasq daemon to leave virbr alone and let
libvirt uses it.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Currently when libvirt daemon is stared, the libvirt startup
script tries to kill the already running dnsmasq daemons
(e.g. from /etc/init.d/dnsmaqs). Also if
"/etc/init.d/libvirtd start" is invoked more than
one time then this will accidentally kills all the dnsmasq
daemon.
This patch makes sure libvirt startup script to kill only the
dnsmasq that spawned by itself. Also try to avoid killing
dnsmasq if "/etc/init.d/libvirtd start" runs second time.
Signed-off-by: Barton Wensley <Barton.Wensley@windriver.com>
Signed-off-by: Vu Tran <vu.tran@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
To avoid having the default build of libvirt depend on virtual/x11
through polkit and consolekit, check for x11 in DISTRO_FEATURES before
enabling the polkit support in the default PKG_CONFIG.
Signed-off-by: Jonas Eriksson <jonas.eriksson@enea.com>
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The Xen drivers in libvirt is needed when the build file system image
and kernel are running as dom0. The parts of the kernel needed to run as
dom0 are controlled by DISTRO_FEATURES, and thus there is no need for
the Xen drivers if DISTRO_FEATURES does not contain 'xen'.
Signed-off-by: Jonas Eriksson <jonas.eriksson@enea.com>
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
It seems that a $ was forgotten in the DISTRO_FEATURE check for selinux.
Signed-off-by: Jonas Eriksson <jonas.eriksson@enea.com>
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
libvirt is to a large extent licensed under LGPLv2.1 (or later) rather
than GPLv2. From my investigations, there are only some tests and a
couple of files under tools are licensed as GPL. Other than that, files
are generally licensed as LGPL. My recommendation is therefore to set
the default license to LGPLv2.1+, and to add a LICENSE_${PN}-ptest that
is set to LGPLv2.1+ & GPLv2+ if a ptest package is added. This is
preferred to avoid having to specify explicit licenses for every other
package, such as the auto generated libvirt-locale-XX packages.
Signed-off-by: Jonas Eriksson <jonas.eriksson@enea.com>
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
I can't explain the dependency on xen-scripts-block as the xendomains
script doesn't invoke any of these scripts directly. Still xendomains
hangs indefinitely without them.
Signed-off-by: Philip Tricca <flihp@twobit.us>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
oe-core fixed some overlap between the python-setuptools-native and
python-distribute-native recently. This made python-setuptools
obsolite. See: http://patchwork.openembedded.org/patch/66085/
The Xen recipe already DEPENDS on python-distribute-native by
inheriting setuptools so we only need to remove the dependency on
python-setuptools-native.
Signed-off-by: Philip Tricca <flihp@twobit.us>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The reason is that the generic code which handles reading lxc.rootfs.mount
always frees the old value if not NULL. So without this setting
lxc.rootfs.mount = /mnt causes segfault.
This is a backport for lxc-0.9.0 (dora) of the same fix found in
upstream's master, see commits 54c30e29 and 53f3f048.
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The tasks responsible for compiling and installing the python support
were racing against packaging. As a result, a clean build would not
have anything in libvirt-python, but subsequent builds would.
By moving to _appends, we control the order and always get properly
packaged.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The TARGET_PYTHON variable is used for script
substitutions to ensure the scripts will be able to properly execute
if the target system has a different path for the python.
Signed-off-by: Jim Somerville <Jim.Somerville@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
To work with oe-core master, we need to update the libvirt-python
FILES_* specification to properly pick up and package the support
libraries.
We can also follow the lead of distutils and use a common set of
install arguments for the configuration and install of our nested
libvirt-python support.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Since python support is separate from the main libvirt build, we
no longer need to trigger configuration options when python
packageconfig support is added, we simply need to add python to the
package depends.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
In 1.2.0, libvirt separated the python components into a separate package.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
autoconf-1.14 will fail to configure lxc with the following warning (and
hence error):
| automake: warnings are treated as errors
| src/lxc/Makefile.am:79: warning: source file '../include/openpty.c' is in a subdirectory,
| src/lxc/Makefile.am:79: but option 'subdir-objects' is disabled
So we tell autoconf that subdir objects are fine .. and the issue is solved.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
