Red Hat Bugzilla – Bug 1101731
Rebase libvirt to current upstream release
Last modified: 2016-04-26 11:47:32 EDT
Description of problem: The current version of libvirt and related packages lack libvirt integration support for Vagrant. Many demos and developer outreach use Vagrant with libvirt as the provider. (Please feel free to clean up this decription if it needs more information.) Version-Release number of selected component (if applicable): These are the related Fedora packages in Rawhide: libvirt-1.2.4-1.fc20.x86_64.rpm libvirt-client-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-config-network-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-config-nwfilter-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-interface-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-lxc-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-network-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-nodedev-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-nwfilter-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-qemu-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-secret-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-driver-storage-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-kvm-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-lxc-1.2.4-1.fc20.x86_64.rpm libvirt-daemon-qemu-1.2.4-1.fc20.x86_64.rpm libvirt-devel-1.2.4-1.fc20.x86_64.rpm libvirt-docs-1.2.4-1.fc20.x86_64.rpm libvirt-python-1.2.4-1.fc20.x86_64.rpm How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I talked to William about this BZ on IRC, and he confirmed that this BZ is a rebase request, that he had run into some problems trying to use Vagrant with older libvirt packages and that they had resolved with the package versions listed in the description. I asked him to file specific BZs about any problems he finds so that they can be confirmed to be fixed.
Hi William, Do you have any problems on the test with the latest packages ? If no, then we will move the bug to verified with the rebased packages, thanks.
Move the bug to verified since the rebase is done.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0323.html