linux/meta-virtualization.git/recipes-extended/libvirt, branch thud

libvirt: 9 Security fixes plus

2019-09-09T17:27:09+00:00

Source: libvirt.org MR: 98352, 99240, 99137, 99245, 99132 Type: Security Fix Disposition: Backport from https://libvirt.org/git/?p=libvirt.git;a=log;h=refs/heads/v4.7-maint ChangeID: 95f822542723d4bf910c1b4159e1431d7d46c969 Description: Update to 4.7 maint tip all bug fixes. Includes: CVE-2018-12126 CVE-2018-12127 CVE-2018-12130 CVE-2019-11091 CVE-2019-10132 CVE-2019-10161 CVE-2019-10166 CVE-2019-10167 CVE-2019-10168 Signed-off-by: Armin Kuster Signed-off-by: Bruce Ashfield

libvirt: Security fix CVE-2019-3840

2019-06-03T20:06:09+00:00

Source: https://libvirt.org MR: 97512 Type: Security Fix Disposition: Backport from https://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=9ed175fbc2deecfdaeabca7bc77c7e7ae33a3377 ChangeID: 6c662c67dd3cf6e0eba493b7b619db35f2e07d93 Description: Fixes CVE-2019-3840 Signed-off-by: Armin Kuster Signed-off-by: Bruce Ashfield

libvirt: remove qemu from PACKAGECONFIG for mips n32 and n64

2018-10-18T15:37:55+00:00

PACKAGECONFIG 'qemu' causes libvirt depends on package qemu. But qemu is not compatible with mips n32 and n64. So remove 'qemu' from PACKAGECONFIG for mips n32 and n64. Signed-off-by: Kai Kang Signed-off-by: Mark Hatle Signed-off-by: Bruce Ashfield

libvirt: do not defer postinstall to first boot when not necessary

2018-10-16T14:25:36+00:00

The postinstall invokes `/etc/init.d/populate-volatile.sh update'. This is only useful for an on-target package upgrade. For now, this postinstall in libvirt has already got a check against $D to tell whether it's running on target or not, we do not need to use pkg_postinstall_ontarget. Otherwise, we get unnecessary postinstall deferred to first boot, which is not what we want. Note that the postinstall was originally written as 'pkg_postinstall_${PN}', but was incorrectly modified to be 'pkg_postinstall_ontarget_${PN}' by the following commit. """ commit 1e67a44db7ec87617455b3228ee5237ceb037173 Author: He Zhe Date: Tue Jul 24 05:50:01 2018 -0700 libvirt: Remove unsupported configure options and fix warning [snip] """ I think the warning about deferred postinstall was caused by some bbappend file instead of the main recipe in this layer. Signed-off-by: Chen Qi Signed-off-by: Bruce Ashfield

libvirt: backport LXC AB / BA deadlock fix

2018-10-01T01:31:14+00:00

This fix will most likely be part of libvirt 4.8.0 but since we took the time to investigate and fix this issue we are including it now to prevent others from hitting this issue. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

libvirt: uprev to v4.7.0

2018-10-01T01:31:14+00:00

A straight-forward uprev to the latest stable release. As usual basic runtime sanity tests have been run along with the ptests. The following is the results of the ptests: ==================================== Testsuite summary for libvirt 4.7.0 ==================================== # TOTAL: 120 # PASS: 117 # SKIP: 0 # XFAIL: 0 # FAIL: 3 # XPASS: 0 # ERROR: 0 Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

libvirt: uprev to v4.5.0

2018-08-20T15:35:48+00:00

Although v4.6.0 was just recently released we do not want to jump to it due to: https://bugzilla.redhat.com/show_bug.cgi?id=1614569 Unfortunately the mess around the above defect basically renders that release useless. We will need to keep an eye for either a v4.7.0 or grab updates off of the 'v4.5-maint' over the coming weeks. As usual I have tested using qemu and lxc usecases (define, boot and 'virsh console' onto a guest). The ptests results match those of v4.3.0: ====================================== Testsuite summary for libvirt 4.5.0 ====================================== # TOTAL: 119 # PASS: 114 # SKIP: 0 # XFAIL: 0 # FAIL: 5 # XPASS: 0 # ERROR: 0 Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

libvirt: fixup ptest to prevent attempts to build tests on the target

2018-08-20T15:35:48+00:00

Oddly something seems to have changed since I did the uprev of libvirt to v4.3.0. Previously using the 'run-ptests' script would only run the tests and not attempt to build them first. In preparation for the uprev to v4.5.0 I attempted to run the tests and found that they would fail to run and instead the tests were attempting to be built. I suspect this change is caused by an uprev of autotools and the handling of the 'TESTS' built-in. To prevent this we are explicitly using the '--with-test-suite' configure option and this return the previously observed behavior, where the tests are simply run and not built. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

libvirt: use relative path to local .m4 files

2018-08-03T02:57:14+00:00

If our project is in a directory with a pathname of longer than about 125 characters, configuration will fail with an "Argument list too long" error. This patch uses the technique that was applied to the coreutils recipe. Signed-off-by: Joe Slater Signed-off-by: Bruce Ashfield

libvirt: Remove unsupported configure options and fix warning

2018-07-26T14:42:06+00:00

xen and xen-inotify have been removed from upstream. We change PACKAGECONFIG accordingly. pkg_postinst has been deprecated, use pkg_postinst_ontarget instead. WARNING: do_rootfs: Intentionally failing postinstall scriptlets of ['libvirt'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ontarget_${PN} (). Signed-off-by: He Zhe Signed-off-by: Bruce Ashfield