On Mon, Feb 06, 2012 at 03:59:19PM +0100, Michal Privoznik wrote:
On 06.02.2012 10:08, Guannan Ren wrote:
Hi,
The Makefile.am in python forget to add probes.o if WITH_DTRACE
but after I added it and tried to connect, using
libvirt.open(qemu:///system)
On 02/07/2012 05:35 PM, Daniel P. Berrange wrote:
On Mon, Feb 06, 2012 at 03:59:19PM +0100, Michal Privoznik wrote:
On 06.02.2012 10:08, Guannan Ren wrote:
Hi,
The Makefile.am in python forget to add probes.o if WITH_DTRACE
but after I added it and tried to connect,
On 06.02.2012 15:59, Michal Privoznik wrote:
On 06.02.2012 10:08, Guannan Ren wrote:
Hi,
The Makefile.am in python forget to add probes.o if WITH_DTRACE
but after I added it and tried to connect, using
libvirt.open(qemu:///system)
in python , it reported:
On Mon, Feb 06, 2012 at 03:59:19PM +0100, Michal Privoznik wrote:
On 06.02.2012 10:08, Guannan Ren wrote:
Hi,
The Makefile.am in python forget to add probes.o if WITH_DTRACE
but after I added it and tried to connect, using
libvirt.open(qemu:///system)
Hi,
The Makefile.am in python forget to add probes.o if WITH_DTRACE
but after I added it and tried to connect, using
libvirt.open(qemu:///system)
in python , it reported: segment fault
I tried to figure out, but failed. If anyone can help this, thanks.
On 06.02.2012 10:08, Guannan Ren wrote:
Hi,
The Makefile.am in python forget to add probes.o if WITH_DTRACE
but after I added it and tried to connect, using
libvirt.open(qemu:///system)
in python , it reported: segment fault
I tried to figure out,
On 02/06/2012 07:59 AM, Michal Privoznik wrote:
Running git bisect showed it was caused by
c700613b8d463212d142c97108b7a2352e23e559. However, I think it only
exposed the design problem we are facing here.
IMHO problem is when an application tries to call virConnectOpen() (or
