Hide Forgot
Description of problem: See https://bugzilla.redhat.com/show_bug.cgi?id=605124#c10 [root@auto-ppcp-001 tps]# virt-top libvir: error : Unknown failure Fatal error: exception Libvirt.Virterror(1, 0, _, 2, 0, 0, 0, _, _) Version-Release number of selected component (if applicable): virt-top-1.0.4-3.7.el6.ppc64
Setting flags for 6.2.
(In reply to comment #0) > Description of problem: > > See https://bugzilla.redhat.com/show_bug.cgi?id=605124#c10 > > [root@auto-ppcp-001 tps]# virt-top > libvir: error : Unknown failure > Fatal error: exception Libvirt.Virterror(1, 0, _, 2, 0, 0, 0, _, _) It seems most likely that this error comes from virInitialize. The fields are: code = VIR_ERR_INTERNAL_ERROR domain = VIR_FROM_NONE message = (not seen) level = VIR_ERR_ERROR str1 = str2 = str3 = NULL int1 = int2 = (not seen) Intriguingly this could be from libvirt, or it could be the error synthesized by ocaml-libvirt bindings when virGetLastError returns NULL. The reason that the ordinary pretty printer for Libvirt.Virterror was not called is that this code happens when virt-top starts up, before entering the main program, and before entering the try- block that would pretty print these errors. There are a range of reasons why virInitialize might have failed, but without full debugging output (LIBVIRT_DEBUG=1) it's not very easy to tell. Note the original error was reported on PPC64. I'm going to add a section in the manual page about libvirt debugging.
Upstream commit 067b868b9cce7620774d7fb57dac6fd8df45d8df.
this bug can reproduce with: virt-top-1.0.4-3.7.el6.ppc64 libvirt-0.8.7-15.el6.ppc64 verify with: virt-top-1.0.4-3.10.el6.ppc64 libvirt-0.9.4-2.el6.ppc64 #virt-top virt-top 23:35:52 - ppc64 4/1CPU 2497MHz 3925MB 0.0% 0 domains, 0 active, 0 running, 0 sleeping, 0 paused, 0 inactive D:0 O:0 X:0 CPU: 0.0% Mem: 0 MB (0 MB by guests) no error when launch virt-top,virt-top worked well. verification passed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1692.html