3:40 a.m.
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.
Thanks,
Qian
7:49 a.m.
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
10:28 a.m.
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(a)redhat.com>
To: "Qian Zhang" <zhq527725(a)gmail.com>
Cc: libvir-list(a)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(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
4:30 a.m.
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(a)redhat.com>
To: "Qian Zhang" <zhq527725(a)gmail.com>
Cc: libvir-list(a)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(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
2:47 p.m.
[please don't top-post on technical lists]
On 04/15/2012 03:30 AM, Qian Zhang wrote:
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?
If you'd like this to be backported to RHEL 6.2, perhaps the best thing
to do is to open a support ticket to Red Hat specifically requesting
that this Fedora BZ be cloned to RHEL.
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
1:09 a.m.
Thanks Eric.
I'd like to know if this issue will be resolved in later release of
RHEL (e.g., RHEL 6.3), if yes, I think I can wait.
Regards,
Qian
[please don't top-post on technical lists]
On 04/15/2012 03:30 AM, Qian Zhang wrote:
> 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?
If you'd like this to be backported to RHEL 6.2, perhaps the best thing
to do is to open a support ticket to Red Hat specifically requesting
that this Fedora BZ be cloned to RHEL.
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
9:37 a.m.
On 04/17/2012 12:09 AM, Qian Zhang wrote:
Thanks Eric.
I'd like to know if this issue will be resolved in later release of
RHEL (e.g., RHEL 6.3), if yes, I think I can wait.
RHEL 6.3 will probably be based on 0.9.10, which already includes the
fixes mentioned in bug 757382, so you are probably safe in waiting for
that release. I'm not sure when the RHEL 6.3 public beta starts, but
history of prior RHEL betas says it won't be much longer, if you'd like
to give that a try. (It's hard to ever get a definitive answer out of
engineers until an actual release occurs, because management has last
say on what schedules can or cannot be met.)
Regards,
Qian
> [please don't top-post on technical lists]
I'll reiterate this request.
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
4602
days inactive
4607
days old
6 comments
4 participants
participants (4)
-
Alex Jia -
Eric Blake -
Michal Privoznik -
Qian Zhang