Description of problem: You cannot install 'xen' and 'blktap' on the same system which is a problem because you cannot use blktap without xen. How reproducible: Consistently Steps to Reproduce: 1. Run: 'yum install xen blktap' Actual results: Transaction check error: file /usr/sbin/tap-ctl conflicts between attempted installs of xen-runtime-4.4.1-6.fc21.x86_64 and blktap-3.0.0-2.fc21.git0.9.2.x86_64 file /usr/sbin/td-util conflicts between attempted installs of xen-runtime-4.4.1-6.fc21.x86_64 and blktap-3.0.0-2.fc21.git0.9.2.x86_64 Expected results: Xen and the latest blktap are installed and can work together Additional info: The Xen package should not include blktap components any more; the maintained blktap code is correctly packaged in the "blktap" package.
I believe the following patches are needed to prevent blktap compiling: http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=653881ce41ec8db3ce7fad38dc280c165f027bb4 http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=5a88f7033e354314a5935c583aabd2ffbd4504a2 http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=489ddd21e3bb7782902a2e983183c7b2f64a8fef along with a spec file change to configure passing --disable-blktap2 and removing the blktap components from the RPM An alternative fix might be to move the blktap components provided by Xen into an optional xen-blktap package so users can chose to either install xen-blktap or upstream blktap
I don't think either proposed solution is viable. If you disable building blktap2 in xen you drop blktap support from libxl so you can't use blktap from xen at all and you don't gain anything. It also means you lose some functionality as utilities such as qcow-create which would be dropped from xen and not replaced by blktap. A separate xen-blktap package won't work either because libxl would use xen's libblktapctl rather than blktap's. It might be possible to link xen against blktap but I don't have a lot of confidence in the blktap package (for example blktap-devel is uninstallable because of a broken requirement) and it would also be very tricky to do. The best solution would be to get that version of blktap integrated upstream in xen so the issue goes away, and the next best (if I am convinced it is worth it) is probably to follow the CentOS example and integrate that version of blktap within the xen packages.
Added Christopher Meng who updated the blktap package for 3.0.0 for Fedora Looking at the history of the blktap spec file I think this has always been the case; I think you've never been able to install 'xen' and 'blktap' together since Xen upgraded to 4.0 - blktap's initial commit includes the binaries that are also present in Xen's. It's strange because blktap was only added in 2012 but Xen has had these binaries since 2010. My understanding is that if it is possible, replacing Xen's blktap with Citrix's blktap (i.e. what's on github) is not a straight forward task by any means and would likely take a long time. I hadn't realised that CentOS had integrated blktap 2 with their xen-c6 package... integrating the upstream blktap with Xen might be a good approach in the short term.
*** Bug 1226687 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.