Bug 1003610 - RFE: capabilities: Expose xen blktap support
Summary: RFE: capabilities: Expose xen blktap support
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-02 13:30 UTC by Cole Robinson
Modified: 2016-03-20 22:26 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-03-20 22:26:14 UTC
Embargoed:


Attachments (Terms of Use)

Description Cole Robinson 2013-09-02 13:30:37 UTC
virt-install/virt-manager have had this check forever:

def is_blktap_capable(conn):
    # Ideally we would get this from libvirt capabilities XML
    if conn.is_remote():
        return False

    f = open("/proc/modules")
    lines = f.readlines()
    f.close()
    for line in lines:
        if line.startswith("blktap ") or line.startswith("xenblktap "):
            return True
    return False

If True, we use driver name='tap' for <disk> XML. As the comment above suggestions, libvirt should expose some tag in capabilities so we know a
host supports blktap, and tools don't need to probe lsmod or similar.

Comment 1 Cole Robinson 2016-03-20 22:26:14 UTC
blktap is apparently not the favored xen driver anymore, as detailed in bug 1171550, so while in theory libvirt should provide this info I don't think anyone practically cares about it anymore.


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