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
Build Update for libvirt/libvirt
-------------------------------------
Build: #187
Status: Errored
Duration: 34 minutes and 54 seconds
Commit: adf846d (master)
Author: Marc Hartmayer
Message: Use ATTRIBUTE_FALLTHROUGH
Use ATTRIBUTE_FALLTHROUGH, introduced by commit
5d84f5961b8e28e802f600bb2d2c6903e219092e, instead of comments to
indicate that the fall through is an intentional behavior.
Signed-off-by: Marc Hartmayer <mhartmay(a)linux.vnet.ibm.com>
Reviewed-by: Boris Fiuczynski <fiuczy(a)linux.vnet.ibm.com>
Reviewed-by: Bjoern Walk <bwalk(a)linux.vnet.ibm.com>
View the changeset: https://github.com/libvirt/libvirt/compare/ebe8139536af...adf846d3c96c
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242223710?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: #185
Status: Errored
Duration: 22 minutes and 20 seconds
Commit: 3ea7eb4 (master)
Author: Shivaprasad G Bhat
Message: qemu: Release address for redirected device hotplug attach failure
The virDomainUSBAddressEnsure returns 0 or -1, so commit id 'de325472'
checking for 1 like qemuDomainAttachChrDeviceAssignAddr was wrong.
Signed-off-by: Shivaprasad G Bhat <sbhat(a)linux.vnet.ibm.com>
View the changeset: https://github.com/libvirt/libvirt/compare/9fd816ed330c...3ea7eb40ba5a
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242033142?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: #177
Status: Passed
Duration: 49 minutes and 57 seconds
Commit: 1a4b21f (master)
Author: Michal Privoznik
Message: virNetClientStreamQueuePacket: Set st->incomingEOF on the end of stream
While reworking client side of streams, I had to postpone payload
decoding so that stream holes and stream data can be
distinguished in virNetClientStreamRecvPacket. That's merely what
18944b7aea46d does. However, I accidentally removed one important
bit: when server sends us an empty STREAM packet (with no
payload) - meaning end of stream - st->incomingEOF flag needs to
be set. It used to be before I touched the code. After I removed
it, virNetClientStreamRecvPacket will try to fetch more data from
the stream, but it will never come.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
Reviewed-by: Jim Fehlig <jfehlig(a)suse.com>
View the changeset: https://github.com/libvirt/libvirt/compare/836f85d13f36...1a4b21f1c67a
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/240438896?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
