Add esxVI_AnyType_Serialize routine to allow serialization
of objects containing variables of type "AnyType". The routine
attempts to determine the type of the object that covers:
boolean, long, int, string, short, byte.
If variables does not fall under any above mentioned types
then it is add
On 12/28/2012 01:31 PM, Scott Sullivan wrote:
On 12/28/2012 10:50 AM, Michal Privoznik wrote:
On 28.12.2012 14:24, Scott Sullivan wrote:
In case its useful, here's the 'bt' output from this session as well:
(gdb) bt
#0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740,
driver_locked=true,
On 12/28/2012 10:50 AM, Michal Privoznik wrote:
On 28.12.2012 14:24, Scott Sullivan wrote:
In case its useful, here's the 'bt' output from this session as well:
(gdb) bt
#0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740, driver_locked=true,
obj=0x7fff80001b00, job=QEMU_JOB_DESTROY,
On 26.12.2012 16:36, Bilal Ahmad wrote:
> Hi all,
>
> I am new to libvirt and started looking at the source code. While
> tracing back the virsh command "net-create", I got stuck into a loop and
> I would really like someone to explain how this works.
>
> In the virsh-network.c, from:
>
> netw
Since sanlock doesn't run under root:root, we have chown()'ed the
__LIBVIRT__DISKS__ lease file to the user:group defined in the
sanlock config. However, when writing the patch I've forgot about
lease files for each disk (this is the
/var/lib/libvirt/sanlock/) file.
---
src/locking/lock_driver_san
On 28.12.2012 14:24, Scott Sullivan wrote:
> In case its useful, here's the 'bt' output from this session as well:
>
> (gdb) bt
> #0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740, driver_locked=true,
> obj=0x7fff80001b00, job=QEMU_JOB_DESTROY, asyncJob=QEMU_ASYNC_JOB_NONE) at
> qemu/qemu
With our recent renames under src/util/* we forgot to adapt
python wrapper code generator. This results in some methods being
not exposed:
$ python examples/domain-events/events-python/event-test.py
Using uri:qemu:///system
Traceback (most recent call last):
File "examples/domain-events/events-p
In case its useful, here's the 'bt' output from this session as well:
(gdb) bt
#0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740,
driver_locked=true, obj=0x7fff80001b00, job=QEMU_JOB_DESTROY,
asyncJob=QEMU_ASYNC_JOB_NONE) at qemu/qemu_domain.c:768
#1 0x7fffeac2b223 in qemuDomainDest
* test download storage volumes using storage download API.
* test upload storage volumes using storage upload API.
For upload case, only raw volume format is supported, other
format will fail.
The offset and length value should be chosen from 0 and
1048576, because upload size is set as 1M