On Thu, Jul 15, 2010 at 07:00:50PM +0200, Guido Winkelmann wrote:
> Am Donnerstag, 1. Juli 2010 schrieb Guido Winkelmann:
> > Am Dienstag, 29. Juni 2010 schrieb Daniel P. Berrange:
> > > Actually that patch wasn't very nice, so I've prepared a different one
> > > which should fix the problem in a b
Am Donnerstag, 1. Juli 2010 schrieb Guido Winkelmann:
> Am Dienstag, 29. Juni 2010 schrieb Daniel P. Berrange:
> > Actually that patch wasn't very nice, so I've prepared a different one
> > which should fix the problem in a better way. Separately, I'd like to
> > know what errors you get when QEMU
Am Dienstag, 29. Juni 2010 schrieb Daniel P. Berrange:
> Actually that patch wasn't very nice, so I've prepared a different one
> which should fix the problem in a better way. Separately, I'd like to
> know what errors you get when QEMU fails to start ?
I've filed a bug report about this:
https:
On Mon, Jun 28, 2010 at 07:29:43PM +0200, Guido Winkelmann wrote:
> Am Montag, 28. Juni 2010 schrieben Sie:
> > On Mon, Jun 28, 2010 at 06:06:00PM +0200, Guido Winkelmann wrote:
> > > Another segfault, again after calling list in virsh after a domain failed
> > > to start:
> >
> > I haven't reprod
Am Montag, 28. Juni 2010 schrieben Sie:
> On Mon, Jun 28, 2010 at 06:06:00PM +0200, Guido Winkelmann wrote:
> > Another segfault, again after calling list in virsh after a domain failed
> > to start:
>
> I haven't reproduced the crashes, but try this patch which I think might
> solve one possible
On Mon, Jun 28, 2010 at 06:06:00PM +0200, Guido Winkelmann wrote:
> Another segfault, again after calling list in virsh after a domain failed to
> start:
I haven't reproduced the crashes, but try this patch which I think might
solve one possible flaw.
diff --git a/src/qemu/qemu_driver.c b/src/qe
Another segfault, again after calling list in virsh after a domain failed to
start:
=
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffef5fe710 (LWP 30490)]
0x77cd5cfd in virDomainObjListCountActive (payload=0x7fffdc006ef0,
name=, data=0
I'm still seeing segfaults in virDomainObjListSearchName, expect now they're
no longer easily reproducible:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe710 (LWP 5446)]
0x77411746 in __strcmp_sse42 () from /lib64/libc.so.6
Missing separate debuginfo
Am Freitag, 25. Juni 2010 schrieb Daniel P. Berrange:
> On Fri, Jun 25, 2010 at 06:08:07PM +0200, Guido Winkelmann wrote:
> > This is the guest's XML config:
> > =
> >
> > testserver-a
> > ce57ebe0-ea37-0353-bbe0-e23dbbd17708
> > libvirt C-API Test
> > 262144
> > 2621
On Fri, Jun 25, 2010 at 06:08:07PM +0200, Guido Winkelmann wrote:
> This is the guest's XML config:
> =
>
> testserver-a
> ce57ebe0-ea37-0353-bbe0-e23dbbd17708
> libvirt C-API Test
> 262144
> 262144
> 1
>
> hvm
>
[snip]
> =
>
> (as
Am Freitag, 25. Juni 2010 schrieb Daniel P. Berrange:
> On Fri, Jun 25, 2010 at 05:34:56PM +0200, Guido Winkelmann wrote:
[...]
> >
> > This is with the newest version from git, pulled about 30 minutes ago.
> >
> > This happens when I try to start up one of the defined domains using
> > either libv
On Fri, Jun 25, 2010 at 05:34:56PM +0200, Guido Winkelmann wrote:
> Hi,
>
> I'm seeing a crash in libvirt when trying to list all domains using virsh.
> Here's the backtrace:
>
> =
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffeebfd710 (L
Hi,
I'm seeing a crash in libvirt when trying to list all domains using virsh.
Here's the backtrace:
=
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeebfd710 (LWP 1691)]
0x77411746 in __strcmp_sse42 () from /lib64/libc.so.6
Missing se
13 matches
Mail list logo
