> On 2 Jan 2017, at 12:01, Sandro Bonazzola <sbona...@redhat.com> wrote: > > > > On Wed, Dec 28, 2016 at 9:55 AM, Gianluca Cecchi <gianluca.cec...@gmail.com > <mailto:gianluca.cec...@gmail.com>> wrote: > > As I wrote, no qemu package proposed. Because oVirt provided qemu is greater > in version in respect with 7.3 > In fact, as I already wrote, I have now > qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 > qemu-img-ev-2.3.0-31.el7.16.1.x86_64 > qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 > qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 > > Hi Gianluca, I added 2.6.0 to oVirt 4.0 repository at > http://resources.ovirt.org/pub/ovirt-4.0/rpm/el7/ > <http://resources.ovirt.org/pub/ovirt-4.0/rpm/el7/>. > It was supposed to be published there with 4.0.6 GA coming ina few days but > it has been already tested enough to be promoted to release repository.
it would be best to remove it. We really do not want to get out of sync with platform It is already causing problems since qemu-kvm-rhev package is 2.6.0-27 and the one you placed in resources.ovirt.org is 2.6.0-27.1 (sure, it’s not a supported combination, but it complicates development) > > For having a qemu-kvm-ev version always aligned with CentOS release I would > suggest to run: > "yum install centos-release-qemu-ev" on your CentOS hosts. > > If you decide to use CentOS VIrt SIG provided packages on your hosts > (excluding the oVirt engine host which still require oVirt repositories) I > would suggest to remove ovirt-release rpms and /etc/yum.repos.d/ovirt-*.repo > and then run: > "yum install centos-release-ovirt40". > > this will add as dependencies: > Requires: centos-release-virt-common > Requires: centos-release-qemu-ev > Requires: centos-release-gluster37 > > providing the latest gluster 3.7 and latest qemu-kvm-ev for your hosts. > > Having both oVirt repos and Virt SIG repos enabled should still work being > both the repos built from the same sources but it's not recommended. > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <http://redhat.com/>_______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users