Build Update for libvirt/libvirt
-------------------------------------
Build: #204
Status: Passed
Duration: 24 minutes and 27 seconds
Commit: ba326c8 (master)
Author: Serge Hallyn
Message: apparmor, libvirt-qemu: Allow access to certificates used by libvirt-vnc
When setting up VncTLS according to the official Libvirt documentation,
only one certificate for libvirt/libvirt-vnc is used. The document
indicates to use the following directories :
/etc/pki/CA
/etc/pki/libvirt
/etc/pki/libvirt/private
in order to manage the certificates used by libvirt-vnc.
Bug-Ubuntu: https://bugs.launchpad.net/bugs/901272
Signed-off-by: Christian Ehrhardt <christian.ehrhardt(a)canonical.com>
Signed-off-by: Stefan Bader <stefan.bader(a)canonical.com>
View the changeset: https://github.com/libvirt/libvirt/compare/307a205e25ad...ba326c869948
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243584971?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #202
Status: Errored
Duration: 50 minutes and 21 seconds
Commit: f1acc41 (master)
Author: Daniel P. Berrange
Message: Temporarily disable format truncation warnings
GCC 7.1 introduces a new -Wformat-truncation warning
flag that reports if it thinks the maximum possible
size of the formatted output will exceed the provided
fixed buffer. This is enabled automatically by the
-Wformat warning flag. There are quite a few places
hit by this in libvirt which need rewriting. This is
non-trivial work in some places, so temporarily
disable the new warning until those fixes can be
implemented.
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/1ba693994a0e...f1acc4130c4d
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243329412?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #201
Status: Passed
Duration: 23 minutes and 4 seconds
Commit: 1ba6939 (master)
Author: Daniel P. Berrange
Message: Disable the -Wduplicated-branches warning
Depending on the platform/architecture, a number of conditionals
in libvirt code expand the same on both branches. This is expected
behaviour and harmless, so disable the warning to avoid creating
unexpected build failures
Two examples, mingw32:
../../src/util/vircommand.c: In function 'virCommandWait':
../../src/util/vircommand.c:2562:51: error: this condition has identical branches [-Werror=duplicated-branches]
*exitstatus = cmd->rawStatus ? status : WEXITSTATUS(status);
^
and gcc7.1
In file included from util/virobject.c:28:0:
util/virobject.c: In function 'virClassNew':
util/viratomic.h:176:46: error: this condition has identical branches [-Werror=duplicated-branches]
(void)(0 ? *(atomic) ^ *(atomic) : 0); \
^
util/virobject.c:144:20: note: in expansion of macro 'virAtomicIntInc'
klass->magic = virAtomicIntInc(&magicCounter);
^~~~~~~~~~~~~~~
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/f0a3fe1b0a29...1ba693994a0e
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243244113?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #200
Status: Errored
Duration: 59 minutes and 40 seconds
Commit: f0a3fe1 (master)
Author: Jiri Denemark
Message: qemu: Use qemuDomainCheckABIStability where needed
Most places which want to check ABI stability for an active domain need
to call this API rather than the original
qemuDomainDefCheckABIStability. The only exception is in snapshots where
we need to decide what to do depending on the saved image data.
https://bugzilla.redhat.com/show_bug.cgi?id=1460952
Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com>
Reviewed-by: Pavel Hrdina <phrdina(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/1e8d6c6ef07a...f0a3fe1b0a29
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242875006?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #196
Status: Errored
Duration: 27 minutes and 16 seconds
Commit: bb12db1 (master)
Author: Erik Skultety
Message: qemu: monitor: Fix a memory leak in qemuMonitorJSONAttachCharDevCommand
With the current logic, we only free @tlsalias as part of the error
label and would have to free it explicitly earlier in the code. Convert
the error label to cleanup, so that we have only one sink, where we
handle all frees. Since JSON object append operation consumes pointers,
make sure @backend is cleared before we hit the cleanup label.
Signed-off-by: Erik Skultety <eskultet(a)redhat.com>
Reviewed-by: Pavel Hrdina <phrdina(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/992bf863fccf...bb12db16b410
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242746313?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #195
Status: Passed
Duration: 59 minutes and 37 seconds
Commit: 992bf86 (master)
Author: Michal Privoznik
Message: qemu: Prefer hugepages over mem source='file'
https://bugzilla.redhat.com/show_bug.cgi?id=1214369
Consider the following XML:
<memoryBacking>
<hugepages>
<page size='2048' unit='KiB' nodeset='1'/>
</hugepages>
<source type='file'/>
<access mode='shared'/>
</memoryBacking>
<numa>
<cell id='0' cpus='0-3' memory='512000' unit='KiB'/>
<cell id='1' cpus='4-7' memory='512000' unit='KiB'/>
</numa>
The following cmd line is generated:
-object
memory-backend-file,id=ram-node0,mem-path=/var/lib/libvirt/qemu/ram,
share=yes,size=524288000 -numa node,nodeid=0,cpus=0-3,memdev=ram-node0
-object
memory-backend-file,id=ram-node1,mem-path=/var/lib/libvirt/qemu/ram,
share=yes,size=524288000 -numa node,nodeid=1,cpus=4-7,memdev=ram-node1
This is obviously wrong as for node 1 hugepages should have been
used. The hugepages configuration is more specific than <source
type='file'/>.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/5b24d250629a...992bf863fccf
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242482790?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #194
Status: Errored
Duration: 36 minutes and 25 seconds
Commit: 5b24d25 (master)
Author: Michal Privoznik
Message: qemuDomainAttachMemory: Crate hugepage dir if needed
https://bugzilla.redhat.com/show_bug.cgi?id=1455819
It may happen that a domain is started without any huge pages.
However, user might try to attach a DIMM module later. DIMM
backed by huge pages (why would somebody want to mix regular and
huge pages is beyond me). Therefore we have to create the dir if
we haven't done so far.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
Reviewed-by: John Ferlan <jferlan(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/ba81c4ee4f6c...5b24d250629a
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242451162?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
