Bug 1003620 - RFE: Improve default xen blktap handling (requires libvirt changes)
Summary: RFE: Improve default xen blktap handling (requires libvirt changes)
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-02 13:38 UTC by Cole Robinson
Modified: 2015-09-23 21:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-09-23 21:36:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Cole Robinson 2013-09-02 13:38:21 UTC
See: https://bugzilla.redhat.com/show_bug.cgi?id=1003610

Libvirt should expose xen blktap support in capabilities XML so virt-manager can stop looking at /proc/modules.

Also, a xen user reported that with recent xen, driver_name=tap2 works but driver_name=tap doesn't:

http://www.redhat.com/archives/virt-tools-list/2013-June/msg00031.html

Might be worth investigating as well

Comment 1 Cole Robinson 2015-09-23 21:36:07 UTC
Just dropped explicit blktap support entirely since it's deprecated upstream:

commit 7c10d8a27f0f635c185d1b85d6d26120d51c8aa2
Author: Cole Robinson <crobinso>
Date:   Wed Sep 23 17:26:48 2015 -0400

    devicedisk: Tweak driver defaults for xen
    
    Following some discussion here:
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1171550
    
    jfehlig suggested better defaults for modern xen. End result is:
    
    - Drop the blktap check, since it's deprecated (yaay)
    - If xen + block device, use driver_name=phy
    - Otherwise if on modern enough libvirt + libxl, do the same thing we
      do for qemu.


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