As planned I tagged the release in git and pushed the tarball and
signed rpms to the usual place:
ftp://libvirt.org/libvirt/
I also generated those for python too even if the only change is a
spec file update, they are in the python subdir.
This is a smaller than average release, with most
On Sat, May 03, 2014 at 03:59:38PM -0400, Cole Robinson wrote:
---
src/util/virerror.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/util/virerror.h b/src/util/virerror.h
index 2de04f4..fe0e15e 100644
--- a/src/util/virerror.h
+++ b/src/util/virerror.h
@@ -99,7
Signed-off-by: John Ferlan jfer...@redhat.com
---
Pushed already just sending note.
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 12338d4..fef99af 100644
--- a/configure.ac
+++ b/configure.ac
@@ -16,7 +16,7 @@ dnl You should
On 04/30/2014 06:02 PM, Michal Privoznik wrote:
My ACK was premature ..
On 24.04.2014 15:19, Ján Tomko wrote:
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named real_device.vlan ID,
avoiding an error flood when virt-manager
On 05/01/2014 02:11 PM, Roman Bogorodskiy wrote:
Add a helper function virBhyveGetDomainTotalCpuStats() to
obtain process CPU time using kvm (kernel memory interface)
and use it to set cpuTime field of the virDomainInfo struct in
bhyveDomainGetInfo().
---
configure.ac | 7
Ján Tomko wrote:
On 05/01/2014 02:11 PM, Roman Bogorodskiy wrote:
Add a helper function virBhyveGetDomainTotalCpuStats() to
obtain process CPU time using kvm (kernel memory interface)
and use it to set cpuTime field of the virDomainInfo struct in
bhyveDomainGetInfo().
---
Daniel P. Berrange wrote:
On Mon, Apr 14, 2014 at 08:25:15PM +0400, Roman Bogorodskiy wrote:
The only accepted format for now is 'bhyve-argv' which
prints out a bhyve command corresponding to the given
domain definition.
---
src/bhyve/bhyve_command.h | 2 ++
On Sat, May 03, 2014 at 03:59:39PM -0400, Cole Robinson wrote:
RaiseErrorFull does not prepend the static error code string (like
INVALID_ARG yields invalid arg: %(msg)s). We should be using
ReportErrorHelper.
The generated error objects are slightly different, by not storing the
invalid