Build Update for libvirt/libvirt
-------------------------------------
Build: #50
Status: Passed
Duration: 26 minutes and 56 seconds
Commit: 42faf31 (v3.3.0-rc2)
Author: Jiri Denemark
Message: client: Report proper close reason
When we get a POLLHUP or VIR_EVENT_HANDLE_HANGUP event for a client, we
still want to read from the socket to process any accumulated data. But
doing so inevitably results in an error and a call to
virNetClientMarkClose before we get to processing the hangup event (and
another call to virNetClientMarkClose). However the close reason passed
to the second virNetClientMarkClose call is ignored because another one
was already set. We need to pass the correct close reason when marking
the socket to be closed for the first time.
https://bugzilla.redhat.com/show_bug.cgi?id=1373859
Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/v3.3.0-rc2
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/228376192?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: #44
Status: Passed
Duration: 20 minutes and 12 seconds
Commit: 2fdfe0c (v3.3.0-rc1)
Author: Jim Fehlig
Message: news: Document libxl nested HVM support
Nested HVM support in the libxl driver is a news-worthy
improvement for libvirt 3.3.0.
Reviewed-by: Pavel Hrdina <phrdina(a)redhat.com>
Signed-off-by: Jim Fehlig <jfehlig(a)suse.com>
View the changeset: https://github.com/libvirt/libvirt/compare/v3.3.0-rc1
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/226954950?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: #22
Status: Fixed
Duration: 18 minutes and 0 seconds
Commit: 1acce5c (master)
Author: Daniel P. Berrange
Message: Update keycodemapdb submodule for python2 compat fixes
There were a few bugs in keycodemap tool that broke it
when run on python circa 2.7.5 or older, which affected
RHEL builds.
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/e6c3b59c193e...1acce5c853b9
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/225960521
--
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: #4
Status: Passed
Duration: 18 minutes and 26 seconds
Commit: 6b3fb86 (master)
Author: Jim Fehlig
Message: Increase default task limit for libvirtd
libvirtd can spawn threads/tasks when creating new domains for
some hypervisors such as Xen's libxl driver, quickly reaching
the cgroups pids controller default TasksMax setting of 512. When
the limit is reached, attempting to create additional domains
results in an error from the cgroups pids controller, e.g.
kernel: [71282.213347] cgroup: fork rejected by pids controller in
/system.slice/libvirtd.service
Depending on domain type and configuration, anywhere from 4-7
threads/tasks may be created by libxl when starting a domain.
In order to support 4096 domains, similar to commit 27cd763500,
increase the TasksMax setting in libvirtd.service to
4096 * 8 = 32768 tasks.
View the changeset: https://github.com/libvirt/libvirt/compare/234ac4e18db3...6b3fb86b391d
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/224004191
--
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: #3
Status: Errored
Duration: 10 minutes and 39 seconds
Commit: 234ac4e (master)
Author: Daniel P. Berrange
Message: Fix error reporting when poll returns POLLHUP/POLLERR
In the RPC client event loop code, if poll() returns only a POLLHUP
or POLLERR status, then we end up reporting a bogus error message:
error: failed to connect to the hypervisor
error: An error occurred, but the cause is unknown
We do actually report an error, but we virNetClientMarkClose method
has already captured the error status before we report it, so the
real error gets thrown away. The key fix is to report the error
before calling virNetClientMarkClose(). In changing this, we also
split out reporting of POLLHUP vs POLLERR to make any future bugs
easier to diagnose.
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/355f5ab99899...234ac4e18db3
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/223886495
--
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: #2
Status: Errored
Duration: 12 minutes and 30 seconds
Commit: 355f5ab (master)
Author: Peter Krempa
Message: qemu: hotplug: Don't save status XML when monitor is closed
In the vcpu hotplug code if exit from the monitor failed we would still
attempt to save the status XML. When the daemon is terminated the
monitor socket is closed. In such case, the written status XML would not
contain the monitor path and thus be invalid.
Avoid this issue by only saving status XML on success of the monitor
command.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1439452
View the changeset: https://github.com/libvirt/libvirt/compare/90acbc76ece8...355f5ab99899
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/223877821
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
