On Mon, Jan 25, 2010 at 06:13:08PM +0100, Luca Tettamanti wrote:
> More in details:
>
> (gdb)
> make_nonnull_node_device (server=, client= optimized out>, conn=0x714d60,
> hdr=, rerr=0x7fffef610e20, args= out>, ret=0x7fffef610e70) at remote.c:5401
> 5401dev_dst->name = strdup(dev_src->
On Mon, Jan 25, 2010 at 04:13:38PM +0100, Guido Günther wrote:
> On Fri, Jan 22, 2010 at 03:03:47PM +0100, Luca Tettamanti wrote:
> > #2 0x0041d1ff in remoteDispatchNodeDeviceLookupByName
> > (server=, client=,
> > conn=0x14ea030, hdr=, rerr=0x7f8115bb7e30,
> > args=, ret=0x7f8115bb7e8
Hi,
On Fri, Jan 22, 2010 at 03:03:47PM +0100, Luca Tettamanti wrote:
> On Fri, Jan 22, 2010 at 1:21 PM, Guido Günther wrote:
> >
> > - Ursprüngliche Mitteilung -
> >> On Thu, Jan 21, 2010 at 11:49:47PM +0100, Laurent Léonard wrote:
> >> > Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a
On Fri, Jan 22, 2010 at 1:21 PM, Guido Günther wrote:
>
> - Ursprüngliche Mitteilung -
>> On Thu, Jan 21, 2010 at 11:49:47PM +0100, Laurent Léonard wrote:
>> > Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a écrit :
>> > > I encountered the same problem on my machine. The bug appeared
- Ursprüngliche Mitteilung -
> On Thu, Jan 21, 2010 at 11:49:47PM +0100, Laurent Léonard wrote:
> > Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a écrit :
> > > I encountered the same problem on my machine. The bug appeared after a
> > > recent upgrade, I've downgraded to 0.7.5-4 and
On Thu, Jan 21, 2010 at 11:49:47PM +0100, Laurent Léonard wrote:
> Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a écrit :
> > I encountered the same problem on my machine. The bug appeared after a
> > recent upgrade, I've downgraded to 0.7.5-4 and I can connect with
> > virt-manager again.
>
On Fri, Jan 22, 2010 at 9:22 AM, Guido Günther wrote:
> On Thu, Jan 21, 2010 at 11:16:30PM +0100, Luca Tettamanti wrote:
>> Package: libvirt-bin
>> Version: 0.7.5-4
>> Followup-For: Bug #565983
>>
>> Hello,
>> I encountered the same problem on my machine. The bug appeared after a
>> recent upgrad
Le vendredi 22 janvier 2010 à 09:22, Guido Günther a écrit :
> On Thu, Jan 21, 2010 at 11:16:30PM +0100, Luca Tettamanti wrote:
> > Package: libvirt-bin
> > Version: 0.7.5-4
> > Followup-For: Bug #565983
> >
> > Hello,
> > I encountered the same problem on my machine. The bug appeared after a
> > r
On Thu, Jan 21, 2010 at 11:16:30PM +0100, Luca Tettamanti wrote:
> Package: libvirt-bin
> Version: 0.7.5-4
> Followup-For: Bug #565983
>
> Hello,
> I encountered the same problem on my machine. The bug appeared after a recent
> upgrade,
> I've downgraded to 0.7.5-4 and I can connect with virt-man
Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a écrit :
> I encountered the same problem on my machine. The bug appeared after a
> recent upgrade, I've downgraded to 0.7.5-4 and I can connect with
> virt-manager again.
I noticed libvirt only crashed at the first connection with Virt-manager. I
Package: libvirt-bin
Version: 0.7.5-4
Followup-For: Bug #565983
Hello,
I encountered the same problem on my machine. The bug appeared after a recent
upgrade,
I've downgraded to 0.7.5-4 and I can connect with virt-manager again.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
Package: libvirt-bin
Version: 0.7.5-5
Severity: important
libvirtd crashes (segfault) as soon as virt-manger tries to connect.
virsh works fine.
Here is a gdb output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7177c910 (LWP 8608)]
0x752727c1 in strlen
12 matches
Mail list logo
