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.
Description of problem:
We need a clearer indication from libvirt, on cpu pinning errors instead of
the current generic code.
Such error expansion will allow the engine to report to Admin the root cause for why start VM fail.
Version-Release number of selected component (if applicable):
# rpm -qa | grep libvirt
libvirt-daemon-1.2.8-13.el7.x86_64
libvirt-daemon-driver-secret-1.2.8-13.el7.x86_64
libvirt-daemon-driver-storage-1.2.8-13.el7.x86_64
libvirt-daemon-driver-network-1.2.8-13.el7.x86_64
libvirt-daemon-driver-interface-1.2.8-13.el7.x86_64
libvirt-daemon-driver-nodedev-1.2.8-13.el7.x86_64
libvirt-daemon-driver-qemu-1.2.8-13.el7.x86_64
libvirt-daemon-kvm-1.2.8-13.el7.x86_64
libvirt-daemon-driver-nwfilter-1.2.8-13.el7.x86_64
libvirt-client-1.2.8-13.el7.x86_64
Additional info:
[by dfediuck]:
"Unknown libvirterror: ecode: 8" is a generic libvirt error.
Sometimes there's more than a single generic error as you can see in [1]
which makes it impossible to differentiate the problem.
This will be a feedback to the user who failed to run a VM.
So this is for explaining the failure.
[1] http://lists.ovirt.org/pipermail/users/2014-January/020003.html
What is the exact problem here? "Unknown libvirterror: ecode: 8" is a message from vdsm. The error reported by libvirt can be found in the email thread you linked: "invalid argument: cannot set memory higher than max memory" that is a pretty good error message from virDomainSetMemory(). Not to mention that I don't see anything related to CPU-pinning here.
I agreed with Ilanit that this bug is actually a tracking bug that can be used to group all specific bugs in this area.
The "Additional info" part of the bug description is completely unrelated.
After discussing this topic with Martin Sivak, there are two sets of problems here.
1) wrong or hard to understand error message in some specific scenarios
2) general issues with the way libvirt reports errors (errors cannot be translated in rhev according to clients' settings; too low level errors messages complaining, e.g., about bitmap errors without giving any clue what the bitmap is used for)
For 1) just file a bug against libvirt whenever you encounter a scenario in which libvirt reports bad error message and we will (try to) fix that.
Fixing 2) is of course harder. We need someone who understands what RHEV needs (probably Martin) to send an email to libvirt-list describing what RHEV wants to do with the error messages provided by libvirt and how it is impossible to do that now. Fixing these issues may require some nontrivial design decisions which need to be made upstream.
The original concrete problem shouldn't be relevant anymore.
We will track individual enhancements separately. There's no magic generic solution for all messaged