[ovirt-users] 3rd party qemu/libvirt rpms and ovirt

Itamar Heim iheim at redhat.com
Tue Jul 8 13:47:26 UTC 2014


On 07/08/2014 04:35 PM, Tiemen Ruiten wrote:
> On 07/08/14 15:24, Itamar Heim wrote:
>> On 07/08/2014 02:04 PM, Tiemen Ruiten wrote:
>>> Well yes, I thought of that. But my reasoning was that if I only upgrade
>>> these specific packages, there is less difference and less potential for
>>> issues. On the other hand, CentOS 7 is mostly based on Fedora 19, so it
>>> could work...guess I can only find out by trying.
>>>
>>> On 07/08/14 12:03, Sven Kieske wrote:
>>>> Well if you are desperate enough to try
>>>> such an unknown third party repo
>>>> you might as well try the freshly released
>>>> centos7?
>>>>
>>>> Am 08.07.2014 11:54, schrieb Tiemen Ruiten:
>>>>> Hello,
>>>>>
>>>>> I'm trying to setup a new oVirt environment based on F19 hosts, but
>>>>> I'm
>>>>> running into so many issues, that I'm thinking of switching 'back' to
>>>>> CentOS. However I would lose the advanced features (libgfapi, live
>>>>> snapshots etc.) that are enabled in the F19 libvirt/qemu/kvm packages.
>>>>> So after some googling a came across Alexandar Evseev's repository
>>>>> with
>>>>> all the newest virtualization rpms packaged for CentOS 6:
>>>>> http://download.opensuse.org/repositories/home:/aevseev/CentOS6/x86_64/
>>>>>
>>>>>
>>>>> However, I can't find any information at all about the status of these
>>>>> packages or any indication about stability. Is anyone familiar with
>>>>> this
>>>>> repository and would it be possible to use these packages in an oVirt
>>>>> environment?
>>>>>
>>>
>>>
>>
>> libgfapi is not enabled in vdsm until libvirt has proper support for
>> snapshots.
>> for the other 'advanved features', you can use the .el6 rpm built in
>> jenkins.ovirt.org
> All right, that's useful information. Maybe I didn't get my terminology
> right: I want to host my VM-images on a GlusterFS volume, on a separate
> storage cluster. Will it be possible to create a GlusterFS storage
> domain on a CentOS cluster that utilizes that? Or should I use the posix
> storage domain and specify glusterfs as a type? Is there any difference
> in performance, since libgfapi isn't enabled anyway?
>

gluster storage domain can be used with any recent .el6 version iirc, it 
doesn't use libgfapi (yet).
using the gluster storage domain means you'll get libgfapi automatically 
at upgrade when its enabled back again



More information about the Users mailing list