On 02/04/2014 05:23 PM, Jiri Denemark wrote:
On Tue, Feb 04, 2014 at 17:02:41 +0100, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes for an hour, but after
On 02/04/2014 11:23 PM, Jiri Denemark wrote:
On Tue, Feb 04, 2014 at 17:02:41 +0100, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes for an hour, but after
On Tue, Feb 04, 2014 at 11:34:39AM -0700, Eric Blake wrote:
On 02/04/2014 11:28 AM, Franky Van Liedekerke wrote:
Are you in a position to bisect which libvirt patch introduced the
problem? It looks like our first use of qom-list was in 1.1.1, with
commit d76a897.
Errr ... I don't
On 02/04/2014 05:23 PM, Jiri Denemark wrote:
On Tue, Feb 04, 2014 at 17:02:41 +0100, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes for an hour, but
On Wed, Feb 05, 2014 at 07:02:38 -0500, John Ferlan wrote:
On 02/04/2014 05:23 PM, Jiri Denemark wrote:
On Tue, Feb 04, 2014 at 17:02:41 +0100, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see
On Tue, Feb 04, 2014 at 11:23:42PM +0100, Jiri Denemark wrote:
On Tue, Feb 04, 2014 at 17:02:41 +0100, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes
On 2014-02-04 17:02, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes for an hour, but after
that the result is always the same: segfault after some weird
On 02/04/2014 09:02 AM, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes for an hour, but after that
the result is always the same: segfault after some weird
On 02/04/2014 11:28 AM, Franky Van Liedekerke wrote:
Are you in a position to bisect which libvirt patch introduced the
problem? It looks like our first use of qom-list was in 1.1.1, with
commit d76a897.
Errr ... I don't really know what you mean with bisect ... but tell me
what to do,
On Tue, 04 Feb 2014 10:19:56 -0700
Eric Blake ebl...@redhat.com wrote:
On 02/04/2014 09:02 AM, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes for an
On Tue, Feb 04, 2014 at 17:02:41 +0100, Franky Van Liedekerke wrote:
Hi,
using libvirt 1.2.0 on a up-to-date Centos6.5 machine leads to
occasional segmentation faults (see below).
Sometimes it runs for 5 minutes, sometimes for an hour, but after that
the result is always the same:
11 matches
Mail list logo