Bug 1335545 - raise more descriptive error than "could not find capabilities"
Summary: raise more descriptive error than "could not find capabilities"
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-12 13:23 UTC by techtonik
Modified: 2024-12-17 12:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-12-17 12:07:46 UTC
Embargoed:


Attachments (Terms of Use)

Description techtonik 2016-05-12 13:23:54 UTC
Description of problem:
It is not clear what capabilities are missing and how to fix the issue.

How reproducible:
Always

Steps to Reproduce:
1.run kvm without VT-x or qemu without qemu

Actual results:
Error while creating domain: Error saving the server: Call to virDomainDefineXML failed: invalid argument: could not find capabilities for domaintype=kvm 

Error while creating domain: Error saving the server: Call to virDomainDefineXML failed: invalid argument: could not find capabilities for domaintype=qemu

Expected results:
Error while creating domain: Error saving the server: Call to virDomainDefineXML failed: invalid argument: could not find capabilities for domaintype=qemu: can't find "qemu" binary

Comment 1 Cole Robinson 2016-05-15 22:40:03 UTC
I know the root error is coming from libvirt, but what application is adding the 'saving the server' bit?

What libvirt version is this?

Comment 2 techtonik 2017-05-04 06:09:29 UTC
I don't know. This is the original report - https://github.com/vagrant-libvirt/vagrant-libvirt/issues/598

Comment 3 Daniel Berrangé 2024-12-17 12:07:46 UTC
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.


Note You need to log in before you can comment on or make changes to this bug.