Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRichard W.M. Jones
2011-02-24 06:33:19 UTC
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
Comment 2Richard W.M. Jones
2011-03-08 08:25:47 UTC
Setting flags for 6.2.
Comment 3Richard W.M. Jones
2011-08-11 12:05:07 UTC
(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.
Comment 4Richard W.M. Jones
2011-08-11 12:11:48 UTC
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