[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] "virsh list" hangs



I think what happened to me is
https://bugzilla.redhat.com/show_bug.cgi?id=757382 which is a dead
lock issue between libvirtd process and its child process.
It looks this issue has been fixed for Fedora 16, any plan for RHEL 6.2?


Regards,
Qian

> Here is a similar issues, please see Jiri's comment:
> https://bugzilla.redhat.com/show_bug.cgi?id=797835#c5
>
> Regards,
> Alex
>
>
> ----- Original Message -----
> From: "Michal Privoznik" <mprivozn redhat com>
> To: "Qian Zhang" <zhq527725 gmail com>
> Cc: libvir-list redhat com
> Sent: Thursday, April 12, 2012 8:49:21 PM
> Subject: Re: [libvirt] "virsh list" hangs
>
> On 12.04.2012 10:40, Qian Zhang wrote:
>> Hi,
>>
>> I am using RHEL 6.2 64bit, and the libvirt shipped in it is
>> "libvirt-0.9.4-23.el6.x86_64". I found sometimes the command "virsh
>> list" hangs forever, and same issue for virt-manager which is always
>> in "Connecting" status. But after restarting the libvirtd service,
>> this issue is gone.
>>
>> Is this a bug of libvirt? Any help will be appreciated.
>
> I think I saw a bug in recent history about this, but now I can't find
> it. Anyway, please file a bug: https://bugzilla.redhat.com/
> And attach debug logs. You can obtain them by editing
> /etc/libvirt/libvirtd.conf and setting:
>
> log_level=1
> log_filters=""
> log_outputs="1:file:/var/log/libvirtd.log"
>
> For more information follow up http://libvirt.org/logging.html;
>
> For client log (we refer to virsh, virt-manager, ... as clients) you can
> set environment variables:
>
> LIBVIRT_DEBUG=1 LIBVIRT_LOG_OUTPUTS="1:file:client.log" virt-manager
> --no-fork
>
> Then attach /var/log/libvirtd.log and client.log to the bugzilla.
>
> Michal
>
> --
> libvir-list mailing list
> libvir-list redhat com
> https://www.redhat.com/mailman/listinfo/libvir-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]