Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1465747
Summary: | libvirtd doesn't detect SVM | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brendan Shephard <brendan.shephard> |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | agedosier, awilliam, berrange, brendan.shephard, clalancette, crobinso, itamar, jdenemar, laine, libvirt-maint, mattdm, veillard, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-07-05 18:50:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brendan Shephard
2017-06-28 06:30:24 UTC
Can you try with libvirt 3.3.0? I think this should be fixed by a series of commits ending with v3.2.0-197-g5b4a6adb5. Brendan, you can grab a newer libvirt from the virt-preview repo for testing: https://fedoraproject.org/wiki/Virtualization_Preview_Repository (In reply to Jiri Denemark from comment #1) > Can you try with libvirt 3.3.0? I think this should be fixed by a series of > commits ending with v3.2.0-197-g5b4a6adb5. Apologies for the late response. The one I pulled from the testing repo was $ libvirtd --version libvirtd (libvirt) 3.4.0 It works with this one. Thanks for the prompt response, love your work. This issue is proposed as a blocker (see #1467599) for F26 release. Is it possible to have a less-invasive fix than upgrading to 3.4.0? (In reply to Matthew Miller from comment #4) > This issue is proposed as a blocker (see #1467599) for F26 release. Is it > possible to have a less-invasive fix than upgrading to 3.4.0? It is probably possible to backport the fixes Jiri mentions to the version in Fedora 26. Closing as a dupe of the blocker bug, since there's more useful information / discussion there. *** This bug has been marked as a duplicate of bug 1467599 *** |