From: Jesse J. Cook jesse.j.c...@member.fsf.org
In the domain-events example C code virEventRegisterDefaultImpl was being
called before virConnectOpen without first calling virInitialize. While this
code worked, it is incorrect. Adding a call to g_string_new prior to the call
From: Jesse J. Cook jc...@camber.com
The example program makes a call to virEventRegisterDefaultImpl before calling
virConnectOpen without a call to virInitialize. Interestingly enough, the
example code works. However, once you introduce a call to g_string_new it
breaks. This can result
From: Jesse J. Cook jesse.j.c...@member.fsf.org
Added error checking to virEventRegisterDefaultImpl call for consistency.
---
examples/domain-events/events-c/event-test.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/examples/domain-events/events-c/event-test.c
b
256 (8 bits) is insufficient for large scale deployments. 65536 (16 bits) is a
more appropriate limit and should be sufficient. You are more likely to run
into other system limitations first, such as the 31998 inode link limit on
ext3.
---
src/remote/remote_protocol.x |2 +-
1 files changed,
I am using libvirt for large scale deployment of virtual machines. I ran into
an issue where virConnectListStoragePools and virConnectListDefinedStoragePools
return an error if there are more than 256 pools. The following patch increases
this limitation. Currently, I am only using in the
On Mon, 2011-04-04 at 16:39 -0600, Eric Blake wrote:
On 03/27/2011 07:30 PM, Jesse Cook wrote:
This patch enables the relative backing file path support provided by
qemu-img create.
If a relative path is specified for the backing file, it is converted
to an absolute path using the
On Tue, 2011-04-05 at 11:00 -0600, Eric Blake wrote:
On 04/05/2011 10:55 AM, Jesse J Cook wrote:
+if ('/' != *(vol-backingStore.path)) {
+virAsprintf(absolutePath, %s/%s, pool-def-target.path,
+vol-backingStore.path);
+
+} else
On Wed, 2011-03-09 at 09:23 -0700, Eric Blake wrote:
On 03/03/2011 08:06 PM, Jesse Cook wrote:
This patch enables the relative backing file path support provided by
qemu-img create.
If the storage pool is not found with the specified path, check if the
file exists relative to the pool
On Wed, 2011-03-09 at 16:07 +, Daniel P. Berrange wrote:
On Thu, Mar 03, 2011 at 09:06:25PM -0600, Jesse Cook wrote:
This patch enables the relative backing file path support provided by
qemu-img create.
If the storage pool is not found with the specified path, check if the
file
