I was going through gluster document it was talking about libgfapi, that
gives better performance.
And I also went through many bug description and comment and mail thread in
But still not understood, how to enable libgfapi ?
Is it supported in 4.1 ? I am confuse.
Please help me to understand whether it supported or not.
If supported, then how can I enable it ? or use it ?
I am running in to trouble with 4.1.4 after engine upgrade I am not able to
start or migrate virtual machines:
getting following error:
General command validation failure
Are there any workarounds?
I upgraded to the latest ovirt-engine-22.214.171.124-1.el6.noarch available in the
ovirt 3.6 repo, however I seem to be encountering a known bug (
https://bugzilla.redhat.com/show_bug.cgi?id=1387949) which looks to be
fixed in ovirt 126.96.36.199 but I can't seem to find out how to install this.
I was hoping it was via http://resources.ovirt.org/pub/ovirt-3.6-snapshot
but this link is dead.
Is anyone using ovirt 3.6.9 and how does one obtain it?
The issues I'm facing is, after trying to update my cluster version to 3.6,
my hosts weren't compatible, as it says they only compatible with version
3.3, 3.4 and 3.5 etc. I then upgraded 1 hosts to Centos 6.9 and installed
and updated the latest vdsm from the 3.6 repo, but this still didn't allow
me to change my cluster version. I then rolled back the cluster version to
At the moment because I've upgraded 1 host, I can't select this host as SPM
and I'm wondering if I can upgrade my remaining hosts, or will this prevent
any hosts from being my SPM? I'm seeing the following error "WARNING
Unrecognized protocol: 'SUBSCRI'" on my upgraded host.
I'm wanting to upgrade to the latest 3.6 as well as upgrade all my hosts,
so that I can start the ovirt 4 upgrade next.
Please could I have some guidance on this?
The ids file for sanlock is broken on one setup. The first host id in
the file is wrong.
>From the logfile i have:
verify_leader 1 wrong space name 0924ff77-ef51-435b-b90d-50bfbf2e�ke7
Note the broken char in the space name.
This also apears. And it seams as the hostid too is broken in the ids
leader4 sn 0924ff77-ef51-435b-b90d-50bfbf2e�ke7 rn ��7afa5-3a91-415b-
a04c-221d3e060163.vbgkvm01.a ts 4351980 cs eefa4dd7
Note the broken chars there as well.
If i check the ids file with less or strings the first row where my
vbgkvm01 host are. That has broken chars.
Can this be repaired in some way without taking down all the virtual
machines on that storage?
Please could someone assist me, my DC seems to be trying to re-negotiate
SPM and apparently it's failing. I tried to delete an old autogenerated
snapshot and shortly after that the issue seemed to start, however after
about an hour, the snapshot said successfully deleted, and then SPM
negotiated again albeit for a short period before it started trying to
Last week I upgraded from ovirt 3.5 to 3.6, I also upgraded one of my 4
hosts using the 3.6 repo to the latest available from that repo and did a
yum update too.
I have 4 nodes and my ovirt engine is a KVM guest on another physical
machine on the network. I'm using an FC SAN with ATTO HBA's and recently
we've started seeing some degraded IO. The SAN appears to be alright and
the disks all seem to check out, but we are having rather slow IOPS at the
moment, which we trying to track down.
ovirt engine CentOS release 6.9 (Final)
node01 (CentOS 6.9)
node01 was upgraded out of desperation after I tried changing my DC and
cluster version to 3.6, but then found that none of my hosts could be
activated out of maintenance due to an incompatibility with 3.6 (I'm still
not sure why as searching seemed to indicate Centos 6.x was compatible. I
then had to remove all 4 hosts, and change the cluster version back to 3.5
and then re-add them. When I tried changing the cluster version to 3.6 I
did get a complaint about using the "legacy protocol" so on each host under
Advanced, I changed them to use the JSON protocol, and this seemed to
resolve it, however once changing the DC/Cluster back to 3.5 the option to
change the protocol back to Legacy is no longer shown.
node02 (Centos 6.7)
node03 CentOS 6.7
node04 (Centos 6.7)
I'm seeing a rather confusing error in the /var/log/messages on all 4 hosts
Jul 31 16:41:36 node01 multipathd: 36001b4d80001c80d0000000000000000: sdb -
directio checker reports path is down
Jul 31 16:41:41 node01 kernel: sd 7:0:0:0: [sdb] Result:
Jul 31 16:41:41 node01 kernel: sd 7:0:0:0: [sdb] CDB: Read(10): 28 00 00 00
00 00 00 00 01 00
Jul 31 16:41:41 node01 kernel: end_request: I/O error, dev sdb, sector 0
I say confusing, because I don't have a 3000GB LUN
[root@node01 ~]# fdisk -l | grep 3000
Disk /dev/sdb: 3000.0 GB, 2999999528960 bytes
I did have one on Friday, last week, but I trashed it and changed it to a
1500GB LUN instead, so I'm not sure if perhaps this error is still trying
to connect to the old LUN perhaps?
My LUNS are as follows...
Disk /dev/sdb: 3000.0 GB, 2999999528960 bytes (this one doesn't actually
Disk /dev/sdc: 1000.0 GB, 999999668224 bytes
Disk /dev/sdd: 1000.0 GB, 999999668224 bytes
Disk /dev/sde: 1000.0 GB, 999999668224 bytes
Disk /dev/sdf: 1000.0 GB, 999999668224 bytes
Disk /dev/sdg: 1000.0 GB, 999999668224 bytes
Disk /dev/sdh: 1000.0 GB, 999999668224 bytes
Disk /dev/sdi: 1000.0 GB, 999999668224 bytes
Disk /dev/sdj: 1000.0 GB, 999999668224 bytes
Disk /dev/sdk: 1000.0 GB, 999999668224 bytes
Disk /dev/sdm: 1000.0 GB, 999999668224 bytes
Disk /dev/sdl: 1000.0 GB, 999999668224 bytes
Disk /dev/sdn: 1000.0 GB, 999999668224 bytes
Disk /dev/sdo: 1000.0 GB, 999999668224 bytes
Disk /dev/sdp: 1000.0 GB, 999999668224 bytes
Disk /dev/sdq: 1000.0 GB, 999999668224 bytes
Disk /dev/sdr: 1000.0 GB, 999988133888 bytes
Disk /dev/sds: 1500.0 GB, 1499999764480 bytes
Disk /dev/sdt: 1500.0 GB, 1499999502336 bytes
I'm quite low on SAN disk space currently so I'm a little hesitant to
migrate VM's around for fear of the migrations creating too many snapshots
and filling up my SAN. We are in the process of expanding the SAN Array
too, but we trying to get to the bottom of the bad IOPS at the moment
before adding on addition overhead.
Ping tests between hosts and engine all look alright, so I don't suspect
I know this is very vague, everything is currently operational, however as
you can see in the attached logs, I'm getting lots of ERROR messages.
Any help or guidance is greatly appreciated.
is anybody successfully using oVirt + Foreman for VM creation +
I'm using Foremn (latest version, 1.15.2) with latest oVirt version
(4.1.3) but I'm encountering several problem, especially related to
disks. For example:
- cannot create a VM with multiple disks though Foreman CLI (hammer)
- if I create a multidisk VM from Foreman, the second disk always gets
the "bootable" flag and not the primary image, making the VMs not
bootable at all.
Any other Foreman user sharing the pain here? Foramn's list is not so
useful so I'm trying to ask here. How do you programmatically create
virtual machines with oVirt and Foreman? Should I switch do directly
using oVirt API?
Thanks in advance
Don't know if this is the right place to ask this but I would like to set
up a trainingslab with oVirt.
I have deployed an engine and a host with local storage and want to run 1
server and 5 desktops off it.
But the desktops will be used on thin clients or old laptops with some
minimal os installation running spice client or a webbrowser.
I was wondering if anyone can give me pointer in how to set up a minimal
laptop which only need to run an spice client.
where did you manually install the packages ? engine or host machine ?
you can you provide the engine.log to see what might cause the error on the
maybe rollback the last yum transaction you did and try to run the engine
as far as for the host installation you might need to check the exiting
repositories (Cenots or other existing repos on the machine)
, its not recommended to use --skip-broken usually when adding a host.
On Tue, Aug 1, 2017 at 11:51 AM, Iurcev, Massimiliano <miurcev(a)inogs.it>
> Unfortunately this didn't work. I tried also to disable totally selinux
> without success.
> Then I decided to install gtk2 manually with the --skip-broken option, and
> apparently everything went fine.
> After this, the host installation goes on without errors.
> It says "Installation is closing up", then gets stuck indefinitely.
> Now the host-engine looks dead or messed up, even after a reboot... more
> in detail, the web portal is no longer accessible. :(
> On 30 July 2017 at 10:58, Yanir Quinn <yquinn(a)redhat.com> wrote:
>> Might be a selinux related issue, similar threads suggest either to
>> disable selinux completely or run on host:
>> # setenforce 0
>> # yum clean expire-cache
>> # yum update selinux-policy\*
>> # setenforce 1
>> keeping an eye out for other reasons/solutions.
>> Yanir Quinn
>> On Thu, Jul 27, 2017 at 5:32 PM, Iurcev, Massimiliano <miurcev(a)inogs.it>
>>> I installed ovirt-engine on Centos7. My target is to have a single host
>>> During the installation of the (first and unique) host, I get an error:
>>> Failed to install Host xxxx. Yum Non-fatal POSTIN scriptlet failure in
>>> rpm package gtk2-2.24.28-8.el7.x86_64.
>>> This error is followed by other errors:
>>> Failed to install Host xxxx. Failed to execute stage 'Package
>>> installation': One or more elements within Yum transaction failed.
>>> and finally:
>>> Host xxxx installation failed. Command returned failure code 1 during
>>> SSH session 'root(a)xxxx.mydomain.it'.
>>> All other libraries are yum-installed without problems.
>>> Users mailing list
I have similar requirement for Ovirt 4.1 PXE boot on UEFI enabled systems, however not able to do successful kickstart installation. Facing two issues
1) nodectl init or imgbase layout —init not working because of the reason commands not found
2) System keeps on network install cycle due to boot loader not been set or not installed - I don’t know sure exactly why?
Could you please help with these issues?
kickstart file contents
liveimg —url=http:/../../squasfs.img <— path shortened
ignoredisk —all —initlabel
clearpart —all —initlabel