Re: [ovirt-users] Please add me to the users list

[Sandro Bonazzola]

Il 22/Apr/2017 06:22, "Precht, Andrew"  ha
scritto:

Hi Ovirt users,

I’m hoping to join this user mailing list. My name is Andrew Precht, I work
at the San Jose Library in San Jose CA. We are setting up a virtual
environment using oVirt for our teenagers to use. With the goal of exposing
them to open source software that they might come across in an enterprise
environment. I / We have a lot to learn and hope we can become supporting
members of this community.

Thanks,
Andrew


Welcome to oVirt community!
In order to subscribe to this mailing list you can go to lists.ovirt.org
and follow instructions.







___
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

[ovirt-users] Disable memory balloon on cluster not adopted by new VMs

[Gianluca Cecchi]

Hello,
I'm in 4.1.1.
I create a cluster that (seems by default) has in the "Optimization"
section the parameter:

Enable Memory Balloon Optimization

checked.
I notice that then, when I create a new VM, by default it has in its
"Resource Allocation" section the "Memory Balloon Device Enable" part
checked too.
So far so good... I don't know actually if this fact is inherited by the
cluster configuration.

In a second time I edit the cluster and disable the Memory Balloon
Optimization parameter.
Still when I create a VM it has Memory Balloon device enabled...

Is this expected? I presume that if I disable at cluster level, this will
have no effect for a VM of that cluster...

Any comment welcome.

Bye,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt GUI bug? clicking "ok" on upgrade host confirmation screen

[Nelson Lameiras]

Hello, 

Since "upgrade" functionality is available for hosts in oVirt GUI I have this 
strange bug : 

- Click on "Installation>>Upgrade" 
- Click "ok" on confirmation screen 
- -> (bug) confirmation screen does not dissapear as expected 
- Click "ok" again on confirmation screen -> error : "system is already 
upgrading" 
- Click "cancel" to be able to return to oVirt 

This happens using on : 
ovirt engine : oVirt Engine Version: 4.1.1.6-1.el7.centos 
client : windows 10 
client : chrome Version 57.0.2987.133 (64-bit) 

This bug was already present on oVirt 4.0 before updating to 4.1. 

Has anybody else have this problem? 

(will try to reproduce with firefox, IE) 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] How to be sure to propagate Cluster's configuration

[Nelson Lameiras]

Hello oVirt gurus, 

Memory ballioning was creating more problems than solving in our cluster so we 
decided to deactivate it. 

- Is changing this setting immediatly taken into account ? 
- Do I need to reactivate hosts? 
- Do I need to reboot vms? 

Same questions for settings " KSM control ", Migration Policy and Scheduling 
Policy. 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 4.0 to 4.1 CentOS7.3 and libvirtd 2.0.0 segfault issue

[Yaniv Kaul]

On Fri, Apr 21, 2017 at 4:38 PM, Rafał Wojciechowski <
i...@rafalwojciechowski.pl> wrote:

> hi,
>
> my issue was related to bug in libvirtd.
> it was found in core dump by libvirt team
>
> "
>
> I'll send a patch to upstream libvirt to fix this crash.  However it can take
> a while to get it back to CentOS/RHEL.  The source of this crash is that you
> have a "tun0" network interface without IP address and that interface is
> checked before "ovirtmgmt" and it causes the crash.  You can workaround it
> by removing the "tun0" interface if it doesn't have any IP address.
>
> Pavel
>
> "
>
> workaround is working fine for me.
>

Thanks for following this!
Any idea how did you get to have the tun0 there in the first place?
Y.

Regards,
> Rafal Wojciechowski
>
> W dniu 18.04.2017 o 16:55, Rafał Wojciechowski pisze:
>
> hi,
>
> I was unable to just remove glibc and install it again - I have
> reinstalled it and rebooted the machine but it was not fixed anything
> Thanks anyway.
>
> Regards,
> Rafal Wojciechowski
> W dniu 18.04.2017 o 10:53, Yanir Quinn pisze:
>
> Hi Rafal
> not sure it relates to your issue, but i experienced a similar issue with
> segfault (running on fedora 25)
> to resolve it i had to remove glibc packages and then install them again
> (maybe a same workaround for libvirt will do the job here)
>
> Regards
> Yanir Quinn
>
> On Tue, Apr 18, 2017 at 9:32 AM, Francesco Romani 
> wrote:
>
>>
>>
>> On 04/18/2017 08:09 AM, Rafał Wojciechowski wrote:
>> >
>> > hello,
>> >
>> > I made comparison(+diff) between xml passing through vdsm which is
>> > working and another one which cause libvirtd segfault
>> >
>> > https://paste.fedoraproject.org/paste/eqpe8Byu2l-3SRdXc6LTLl
>> 5M1UNdIGYhyRLivL9gydE=
>> >
>> >
>> > I am not sure if below setting are fine but I dont know how to change
>> them
>> >
>> > 
>> > (I dont have so much ram and vgamem)
>> >
>>
>> those are kibibytes though
>> (https://libvirt.org/formatdomain.html#elementsVideo), are pretty
>> conservarvative settings
>> >
>> > > > passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1"
>> type="spice">
>> > (ports with "-"? maybe it is fine because of autoport settings...)
>> >
>>
>> Yes, "-1" means "autoallocation from libvirt".
>> I don't see obvious issues in this XML, and, most importantly, one
>> invalid XML should never cause libvirtd to segfault.
>>
>> I'd file a libvirt bug.
>>
>>
>> --
>> Francesco Romani
>> Senior SW Eng., Virtualization R
>> Red Hat
>> IRC: fromani github: @fromanirh
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> 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

[ovirt-users] bug with ConsoleWriter ?

[Fabrice Bacchella]

I'm trying to dump informations about console with the following code:

vm = vms_service.list(search='name=fa41')[0]

# Find the service that manages the graphics consoles of the virtual machine:
vm_service = vms_service.vm_service(vm.id)
consoles_service = vm_service.graphics_consoles_service()
console_type = consoles_service.list()[0]

console_type = connection.follow_link(console_type)
buf = None
writer = None
buf = io.BytesIO()
writer = xml.XmlWriter(buf, indent=True)
ConsoleWriter.write_one(console_type, writer)
writer.flush()
print buf.getvalue()
But i got the following result :

Traceback (most recent call last):
  File "./export_console.py", line 69, in 
ConsoleWriter.write_one(console_type, writer)
  File ".../venv/lib/python2.7/site-packages/ovirtsdk4/writers.py", line 1262, 
in write_one
if obj.enabled is not None:

If I add print console_type.__dict__, it contains:

{'_address': None, '_instance_type': None, '_href': 
'/ovirt-engine/api/vms/61a6de0a-2a21-4e90-bc20-29e3f0cd0ad8/graphicsconsoles/7370696365',
 '_description': None, '_tls_port': None, '_comment': None, '_port': None, 
'_name': None, '_vm': , '_protocol': 
, '_template': None, '_id': '7370696365'}


Did I miss something, or is that a but with the console writer ? 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Compiling oVirt for Debian.

[Leni Kadali Mutungi]

Also I noticed when running `make` and `make install` for otopi after
running ./configure with the --enable-java-sdk and --with-maven
options that in both instances, code (for lack of a better word) gets
downloaded from https://repo.maven.apache.org/. I was wondering if
there was a way instead to check if the latest jar and pom modules
have been downloaded and then continue with the build using what is
already there. For a user like myself who's on a capped connection,
that would helpful since it would trim the amount of data used. Of
course, it is possible that it is minimal, but I also thought it would
be handy to avoid the duplication of effort so to speak.

As an aside, at what time is the community online in IRC? I ask
because I have had difficulty working this out from the documentation
which says 07:00 UMT to 11:00 UMT (09:00 IST to 17:00 PST). I haven't
been able to work out what timezone UMT is (all I got was Universal
Military Time and a successor standard to GMT, which I was unable to
make sense of unfortunately) and all I got for IST was Indian Standard
Time which would be okay, only that PST stands for Pacific Standard
Time (PDT in the summer) and that wouldn't add up :)

However if the mailing list is the preferred option, then I shall be
more than happy to stick to that :D

On 4/21/17, Leni Kadali Mutungi  wrote:
> Have run into difficulties building ovirt-host-deploy. I tried to
> build otopi using the commands given in the INSTALL file and made sure
> to run `./configure` with the options --enable-java-sdk and
> --with-maven. Unfortunately, when I restarted the building of
> ovirt-host-deploy, I failed to make it past ./configure with the
> resulting error below:
>
> user@localhost:~/ovirt-host-deploy$ ./configure --enable-java-sdk
> --with-maven
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking for a sed that does not truncate output... /bin/sed
> checking whether NLS is requested... yes
> checking for msgfmt... /usr/bin/msgfmt
> checking for gmsgfmt... /usr/bin/msgfmt
> checking for xgettext... /usr/bin/xgettext
> checking for msgmerge... /usr/bin/msgmerge
> checking for a sed that does not truncate output... (cached) /bin/sed
> checking whether make sets $(MAKE)... (cached) yes
> checking whether ln -s works... yes
> checking if 'ln -sr' supported... yes
> checking for pyflakes... pyflakes
> checking for pep8... no
> checking for mvn... mvn
> checking for javac... javac
> checking for jar... jar
> checking for otopi-bundle... no
> checking for a Python interpreter with version >= 2.6... python
> checking for python... /usr/bin/python
> checking for python version... 2.7
> checking for python platform... linux2
> checking for python script directory...
> ${prefix}/lib/python2.7/dist-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.7/dist-packages
> checking python module: otopi... yes
> configure: error: otopi-devtools required but missing
>
> I've run ./configure with the options and without it, and I've got the
> same error. Sandro in IRC had suggested that I adapt the full options
> for ./configure in Fedora and use them in Debian. Those are as
> follows:
>
>  ./configure --build=x86_64-redhat-linux-gnu
> --host=x86_64-redhat-linux-gnu --program-prefix=
> --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr
> --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
> --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64
> --libexecdir=/usr/libexec --localstatedir=/var
> --sharedstatedir=/var/lib --mandir=/usr/share/man --info
> --docdir=/usr/share/doc/otopi-1.6.3 --disable-python-syntax-check
> --enable-java-sdk --with-local-version=otopi-1.6.3-0.0.master.fc26
> COMMONS_LOGGING_JAR=/usr/share/java/commons-logging.jar
> JUNIT_JAR=/usr/share/java/junit.jar
>
> I got stuck at `--build=x86_64-redhat-linux-gnu` since `uname -a`
> gives: Linux localhost 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2
> (2016-06-25) x86_64 GNU/Linux
> I wasn't sure if I should substitute `x86_64-redhat-linux-gnu` with
> `x86_64-gnu-linux`. Also the ./configure script downloaded
> otopi-1.7.0.master so that I would need to change that as well as the
> reference to Fedora in
> `--with-local-version=otopi-1.6.3-0.0.master.fc26`. I went onto the
> #debian-next channel and was advised to spare myself future pain by
> looking into packaging the necessary stuff for Debian instead of
> trying to hack out a build that will be painful to maintain in future.
>
> Pointers, docs, advice are all welcome.
>
> On 4/20/17, Yedidyah Bar David  wrote:
>> On Thu, Apr 20, 2017 at 3:45 PM, Leni Kadali Mutungi
>>  wrote:
>>> On 

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

[Jamie Lawrence]

> On Apr 21, 2017, at 6:38 AM, knarra  wrote:
> 
> On 04/21/2017 06:34 PM, Jamie Lawrence wrote:
>>> On Apr 20, 2017, at 10:36 PM, knarra  wrote:
 The installer claimed it did, but I believe it didn’t. Below the error 
 from my original email, there’s the below (apologies for not including it 
 earlier; I missed it). Note: 04ff4cf1-135a-4918-9a1f-8023322f89a3 is the 
 HE - I’m pretty sure it is complaining about itself. (In any case, I 
 verified that there are no other VMs running with both virsh and 
 vdsClient.)
>> ^^^
>> 
 2017-04-19 12:27:02 DEBUG otopi.context context._executeMethod:128 Stage 
 late_setup METHOD otopi.plugins.gr_he_setup.vm.runvm.Plugin._late_setup
 2017-04-19 12:27:02 DEBUG otopi.plugins.gr_he_setup.vm.runvm 
 runvm._late_setup:83 {'status': {'message': 'Done', 'code': 0}, 'items': 
 [u'04ff4cf1-135a-4918-9a1f-8023322f89a3']}
 2017-04-19 12:27:02 ERROR otopi.plugins.gr_he_setup.vm.runvm 
 runvm._late_setup:91 The following VMs have been found: 
 04ff4cf1-135a-4918-9a1f-8023322f89a3
 2017-04-19 12:27:02 DEBUG otopi.context context._executeMethod:142 method 
 exception
 Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in 
 _executeMethod
 method['method']()
   File 
 "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-setup/vm/runvm.py",
  line 95, in _late_setup
 _('Cannot setup Hosted Engine with other VMs running')
 RuntimeError: Cannot setup Hosted Engine with other VMs running
 2017-04-19 12:27:02 ERROR otopi.context context._executeMethod:151 Failed 
 to execute stage 'Environment setup': Cannot setup Hosted Engine with 
 other VMs running
 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:760 
 ENVIRONMENT DUMP - BEGIN
 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:770 ENV 
 BASE/error=bool:'True'
 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:770 ENV 
 BASE/exceptionInfo=list:'[(, 
 RuntimeError('Cannot setup Hosted Engine with other VMs running',), 
 )]'
 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:774 
 ENVIRONMENT DUMP - END
>>> James, generally this issue happens when the setup failed once and you 
>>> tried re running it again.  Can you clean it and deploy it again?  HE 
>>> should come up successfully. Below are the steps for cleaning it up.
>> Knarra,
>> 
>> I realize that. However, that is not the situation in my case. See above, at 
>> the mark - the UUID it is complaining about is the UUID of the hosted-engine 
>> it just installed. From the answers file generated from the run (whole thing 
>> below):
>> 
>> OVEHOSTED_VM/vmUUID=str:04ff4cf1-135a-4918-9a1f-8023322f89a3
>> Also see the WARNs I mentioned previously, quoted below. Excerpt:
>> 
>> Apr 19 12:29:20 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm root WARN 
>> File: 
>> /var/lib/libvirt/qemu/channels/04ff4cf1-135a-4918-9a1f-8023322f89a3.com.redhat.rhevm.vdsm
>>  already removed
>> Apr 19 12:29:20 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm root WARN 
>> File: 
>> /var/lib/libvirt/qemu/channels/04ff4cf1-135a-4918-9a1f-8023322f89a3.org.qemu.guest_agent.0
>>  already removed
>> Apr 19 12:29:30 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm 
>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Failed to connect 
>> to broker, the number of errors has exceeded the limit (1)
>> I’m not clear on what it is attempting to do there, but it seems relevant.
> I remember that you said HE vm was not started when the installation was 
> successful. Is Local Maintenance enabled on that host?
> 
> can you please check if the services 'ovirt-ha-agent' and 'ovirt-ha-broker' 
> running fine and try to restart them once ?

Agent and broker logs from before are down in the original message quoting.  
They’re running, but not fine.

[root@sc5-ovirt-2 jlawrence]# ps ax|grep ha-
130599 ?Ssl3:52 /usr/bin/python 
/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker --no-daemon
132869 ?Ss 0:13 /usr/bin/python 
/usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent --no-daemon
133501 pts/0S+ 0:00 grep --color=auto ha-
[root@sc5-ovirt-2 jlawrence]# systemctl restart ovirt-ha-agent ovirt-ha-broker
[root@sc5-ovirt-2 jlawrence]# tail -40 
/var/log/ovirt-hosted-engine-ha/broker.log
Thread-46::INFO::2017-04-21 
10:52:57,058::storage_backends::119::ovirt_hosted_engine_ha.lib.storage_backends::(_check_symlinks)
 Cleaning up stale LV link 
'/rhev/data-center/mnt/glusterSD/sc5-gluster-1.squaretrade.com:_ovirt__engine/a1155699-0bcf-44c5-aa55-a574ca3ad313/ha_agent/hosted-engine.metadata'
Thread-53::INFO::2017-04-21 
10:52:57,070::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
 Connection closed

Re: [ovirt-users] LACP Bonding issue

[Derek Atkins]

Bryan Sockel  writes:

> That was my next thought, wanted to see if there was another way before I got
> to that point.

Just let me know if you want to see my configuration files in
/etc/sysconfig/network-scripts/  I'm happy to share them.

-derek
-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Please add me to the users list

[Precht, Andrew]

Hi Ovirt users,

I’m hoping to join this user mailing list. My name is Andrew Precht, I work at 
the San Jose Library in San Jose CA. We are setting up a virtual environment 
using oVirt for our teenagers to use. With the goal of exposing them to open 
source software that they might come across in an enterprise environment. I / 
We have a lot to learn and hope we can become supporting members of this 
community.

Thanks,
Andrew



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 4.0 to 4.1 CentOS7.3 and libvirtd 2.0.0 segfault issue

[Rafał Wojciechowski]

hello,

I am not sure.
I have simple openvpn client profile with systemd enabled on boot time, 
but I think I was not included it anywhere for libvirt/ovirt purpose.


also strange for me was statement that this interface was without IP - 
this interface should be up with IP after connection established... but 
anyway even if some dependencies occurs, then it should be handled 
somehow with proper error.


Regards,

Rafal Wojciechowski


W dniu 21.04.2017 o 17:41, Yaniv Kaul pisze:



On Fri, Apr 21, 2017 at 4:38 PM, Rafał Wojciechowski 
> wrote:


hi,

my issue was related to bug in libvirtd.
it was found in core dump by libvirt team

"

I'll send a patch to upstream libvirt to fix this crash.  However it can 
take
a while to get it back to CentOS/RHEL.  The source of this crash is that you
have a "tun0" network interface without IP address and that interface is
checked before "ovirtmgmt" and it causes the crash.  You can workaround it
by removing the "tun0" interface if it doesn't have any IP address.

Pavel

"

workaround is working fine for me.


Thanks for following this!
Any idea how did you get to have the tun0 there in the first place?
Y.

Regards,
Rafal Wojciechowski

W dniu 18.04.2017 o 16:55, Rafał Wojciechowski pisze:


hi,

I was unable to just remove glibc and install it again - I have
reinstalled it and rebooted the machine but it was not fixed anything
Thanks anyway.

Regards,
Rafal Wojciechowski

W dniu 18.04.2017 o 10:53, Yanir Quinn pisze:

Hi Rafal
not sure it relates to your issue, but i experienced a similar
issue with segfault (running on fedora 25)
to resolve it i had to remove glibc packages and then install
them again (maybe a same workaround for libvirt will do the job
here)

Regards
Yanir Quinn

On Tue, Apr 18, 2017 at 9:32 AM, Francesco Romani
> wrote:



On 04/18/2017 08:09 AM, Rafał Wojciechowski wrote:
>
> hello,
>
> I made comparison(+diff) between xml passing through vdsm
which is
> working and another one which cause libvirtd segfault
>
>

https://paste.fedoraproject.org/paste/eqpe8Byu2l-3SRdXc6LTLl5M1UNdIGYhyRLivL9gydE=


>
>
> I am not sure if below setting are fine but I dont know
how to change them
>
> 
> (I dont have so much ram and vgamem)
>

those are kibibytes though
(https://libvirt.org/formatdomain.html#elementsVideo
), are
pretty
conservarvative settings
>
>  passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1"
type="spice">
> (ports with "-"? maybe it is fine because of autoport
settings...)
>

Yes, "-1" means "autoallocation from libvirt".
I don't see obvious issues in this XML, and, most
importantly, one
invalid XML should never cause libvirtd to segfault.

I'd file a libvirt bug.


--
Francesco Romani
Senior SW Eng., Virtualization R
Red Hat
IRC: fromani github: @fromanirh

___
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


___ 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

Re: [ovirt-users] Compiling oVirt for Debian.

[Leni Kadali Mutungi]

Have run into difficulties building ovirt-host-deploy. I tried to
build otopi using the commands given in the INSTALL file and made sure
to run `./configure` with the options --enable-java-sdk and
--with-maven. Unfortunately, when I restarted the building of
ovirt-host-deploy, I failed to make it past ./configure with the
resulting error below:

user@localhost:~/ovirt-host-deploy$ ./configure --enable-java-sdk --with-maven
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for a sed that does not truncate output... /bin/sed
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for a sed that does not truncate output... (cached) /bin/sed
checking whether make sets $(MAKE)... (cached) yes
checking whether ln -s works... yes
checking if 'ln -sr' supported... yes
checking for pyflakes... pyflakes
checking for pep8... no
checking for mvn... mvn
checking for javac... javac
checking for jar... jar
checking for otopi-bundle... no
checking for a Python interpreter with version >= 2.6... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/dist-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/dist-packages
checking python module: otopi... yes
configure: error: otopi-devtools required but missing

I've run ./configure with the options and without it, and I've got the
same error. Sandro in IRC had suggested that I adapt the full options
for ./configure in Fedora and use them in Debian. Those are as
follows:

 ./configure --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --program-prefix=
--disable-dependency-tracking --prefix=/usr --exec-prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64
--libexecdir=/usr/libexec --localstatedir=/var
--sharedstatedir=/var/lib --mandir=/usr/share/man --info
--docdir=/usr/share/doc/otopi-1.6.3 --disable-python-syntax-check
--enable-java-sdk --with-local-version=otopi-1.6.3-0.0.master.fc26
COMMONS_LOGGING_JAR=/usr/share/java/commons-logging.jar
JUNIT_JAR=/usr/share/java/junit.jar

I got stuck at `--build=x86_64-redhat-linux-gnu` since `uname -a`
gives: Linux localhost 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2
(2016-06-25) x86_64 GNU/Linux
I wasn't sure if I should substitute `x86_64-redhat-linux-gnu` with
`x86_64-gnu-linux`. Also the ./configure script downloaded
otopi-1.7.0.master so that I would need to change that as well as the
reference to Fedora in
`--with-local-version=otopi-1.6.3-0.0.master.fc26`. I went onto the
#debian-next channel and was advised to spare myself future pain by
looking into packaging the necessary stuff for Debian instead of
trying to hack out a build that will be painful to maintain in future.

Pointers, docs, advice are all welcome.

On 4/20/17, Yedidyah Bar David  wrote:
> On Thu, Apr 20, 2017 at 3:45 PM, Leni Kadali Mutungi
>  wrote:
>> On 4/18/17, Yedidyah Bar David  wrote:
>>> On Sun, Apr 16, 2017 at 6:54 AM, Leni Kadali Mutungi
>>>  wrote:
>> I think that all of them are maintained on gerrit.ovirt.org, and most
>> have
>> mirrors on github.com/ovirt.
>>
 Found all the source code on gerrit.ovirt.org; not all of it is
 mirrored to github.com/ovirt

>> If you haven't yet, you might want to check also:
>>
>> http://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/
>> Adding to otopi support for apt/dpkg is indeed interesting and
>> useful,
>> but
>> imo isn't mandatory for a first milestone. Not having an apt packager
>> will
>> simply mean you can't install/update packages using otopi, but other
>> things
>> should work. Notably, you won't be able to use engine-setup for
>> upgrades,
>> at least not the way it's done with yum and versionlock.

 So does this mean I shouldn't bother with installing otopi, because
 according to the development guide for RPM-based systems, it seems
 only the ovirt-host-deploy, ovirt-setup-lib, and ovirt-js-dependencies
 are the packages required.
>>>
>>> ovirt-host-deploy requires otopi, and also engine-setup (from the engine
>>> git repo) does. So unless you want to start manually imitating what
>>> these
>>> do (which might not be a terrible idea, if you want to understand more
>>> deeply how things work, but will take more time), you do 

Re: [ovirt-users] Ovirt 4.0 to 4.1 CentOS7.3 and libvirtd 2.0.0 segfault issue

[Rafał Wojciechowski]

hi,

my issue was related to bug in libvirtd.
it was found in core dump by libvirt team

"

I'll send a patch to upstream libvirt to fix this crash.  However it can take
a while to get it back to CentOS/RHEL.  The source of this crash is that you
have a "tun0" network interface without IP address and that interface is
checked before "ovirtmgmt" and it causes the crash.  You can workaround it
by removing the "tun0" interface if it doesn't have any IP address.

Pavel

"

workaround is working fine for me.

Regards,
Rafal Wojciechowski

W dniu 18.04.2017 o 16:55, Rafał Wojciechowski pisze:


hi,

I was unable to just remove glibc and install it again - I have 
reinstalled it and rebooted the machine but it was not fixed anything

Thanks anyway.

Regards,
Rafal Wojciechowski

W dniu 18.04.2017 o 10:53, Yanir Quinn pisze:

Hi Rafal
not sure it relates to your issue, but i experienced a similar issue 
with segfault (running on fedora 25)
to resolve it i had to remove glibc packages and then install them 
again (maybe a same workaround for libvirt will do the job here)


Regards
Yanir Quinn

On Tue, Apr 18, 2017 at 9:32 AM, Francesco Romani > wrote:




On 04/18/2017 08:09 AM, Rafał Wojciechowski wrote:
>
> hello,
>
> I made comparison(+diff) between xml passing through vdsm which is
> working and another one which cause libvirtd segfault
>
>

https://paste.fedoraproject.org/paste/eqpe8Byu2l-3SRdXc6LTLl5M1UNdIGYhyRLivL9gydE=


>
>
> I am not sure if below setting are fine but I dont know how to
change them
>
> 
> (I dont have so much ram and vgamem)
>

those are kibibytes though
(https://libvirt.org/formatdomain.html#elementsVideo
), are pretty
conservarvative settings
>
>  passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1"
type="spice">
> (ports with "-"? maybe it is fine because of autoport settings...)
>

Yes, "-1" means "autoallocation from libvirt".
I don't see obvious issues in this XML, and, most importantly, one
invalid XML should never cause libvirtd to segfault.

I'd file a libvirt bug.


--
Francesco Romani
Senior SW Eng., Virtualization R
Red Hat
IRC: fromani github: @fromanirh

___
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


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

[knarra]

On 04/21/2017 06:34 PM, Jamie Lawrence wrote:

On Apr 20, 2017, at 10:36 PM, knarra  wrote:

The installer claimed it did, but I believe it didn’t. Below the error from my 
original email, there’s the below (apologies for not including it earlier; I 
missed it). Note: 04ff4cf1-135a-4918-9a1f-8023322f89a3 is the HE - I’m pretty 
sure it is complaining about itself. (In any case, I verified that there are no 
other VMs running with both virsh and vdsClient.)

^^^


2017-04-19 12:27:02 DEBUG otopi.context context._executeMethod:128 Stage 
late_setup METHOD otopi.plugins.gr_he_setup.vm.runvm.Plugin._late_setup
2017-04-19 12:27:02 DEBUG otopi.plugins.gr_he_setup.vm.runvm 
runvm._late_setup:83 {'status': {'message': 'Done', 'code': 0}, 'items': 
[u'04ff4cf1-135a-4918-9a1f-8023322f89a3']}
2017-04-19 12:27:02 ERROR otopi.plugins.gr_he_setup.vm.runvm 
runvm._late_setup:91 The following VMs have been found: 
04ff4cf1-135a-4918-9a1f-8023322f89a3
2017-04-19 12:27:02 DEBUG otopi.context context._executeMethod:142 method 
exception
Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in 
_executeMethod
 method['method']()
   File 
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-setup/vm/runvm.py",
 line 95, in _late_setup
 _('Cannot setup Hosted Engine with other VMs running')
RuntimeError: Cannot setup Hosted Engine with other VMs running
2017-04-19 12:27:02 ERROR otopi.context context._executeMethod:151 Failed to 
execute stage 'Environment setup': Cannot setup Hosted Engine with other VMs 
running
2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT 
DUMP - BEGIN
2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:770 ENV 
BASE/error=bool:'True'
2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:770 ENV 
BASE/exceptionInfo=list:'[(, RuntimeError('Cannot 
setup Hosted Engine with other VMs running',), )]'
2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:774 ENVIRONMENT 
DUMP - END

James, generally this issue happens when the setup failed once and you tried re 
running it again.  Can you clean it and deploy it again?  HE should come up 
successfully. Below are the steps for cleaning it up.

Knarra,

I realize that. However, that is not the situation in my case. See above, at 
the mark - the UUID it is complaining about is the UUID of the hosted-engine it 
just installed. From the answers file generated from the run (whole thing 
below):


OVEHOSTED_VM/vmUUID=str:04ff4cf1-135a-4918-9a1f-8023322f89a3

Also see the WARNs I mentioned previously, quoted below. Excerpt:


Apr 19 12:29:20 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm root WARN File: 
/var/lib/libvirt/qemu/channels/04ff4cf1-135a-4918-9a1f-8023322f89a3.com.redhat.rhevm.vdsm
 already removed
Apr 19 12:29:20 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm root WARN File: 
/var/lib/libvirt/qemu/channels/04ff4cf1-135a-4918-9a1f-8023322f89a3.org.qemu.guest_agent.0
 already removed
Apr 19 12:29:30 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm 
ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Failed to connect to 
broker, the number of errors has exceeded the limit (1)

I’m not clear on what it is attempting to do there, but it seems relevant.
I remember that you said HE vm was not started when the installation was 
successful. Is Local Maintenance enabled on that host?


can you please check if the services 'ovirt-ha-agent' and 
'ovirt-ha-broker' running fine and try to restart them once ?





I know there is no failed install left on the gluster volume, because when I 
attempt an install, part of my scripted prep process is deleting and recreating 
the Gluster volume. The below instructions are more or less what I’m doing 
already in a script[1]. (the gluster portion of the script process is: stop the 
volume, delete the volume, remove the mount point directory to avoid Gluster’s 
xattr problem with recycling directories, recreate the directory, change perms, 
create the volume, start the volume, set Ovirt-recc’ed volume options.)

-j

[1] We have a requirement for automated setup of all production resources, so 
all of this ends up being scripted.


1) vdsClient -s 0 list table | awk '{print $1}' | xargs vdsClient -s 0 destroy

2) stop the volume and delete all the information inside the bricks from all 
the hosts

3) try to umount storage from /rhev/data-center/mnt/ - umount -f 
/rhev/data-center/mnt/  if it is mounted

4) remove all dirs from /rhev/data-center/mnt/ - rm -rf /rhev/data-center/mnt/*

5) start  volume again and start the deployment.

Thanks
kasturi



If I start it manually, the default DC is down, the default cluster has the 
installation host in the cluster,  there is no storage, and the VM doesn’t show 
up in the GUI. In this install run, I have not yet started the engine manually.

you wont be seeing HE vm until HE storage is imported into the UI. HE storage 
will be 

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

[Jamie Lawrence]

> On Apr 20, 2017, at 10:36 PM, knarra  wrote:

>> The installer claimed it did, but I believe it didn’t. Below the error from 
>> my original email, there’s the below (apologies for not including it 
>> earlier; I missed it). Note: 04ff4cf1-135a-4918-9a1f-8023322f89a3 is the HE 
>> - I’m pretty sure it is complaining about itself. (In any case, I verified 
>> that there are no other VMs running with both virsh and vdsClient.)

^^^ 

>> 2017-04-19 12:27:02 DEBUG otopi.context context._executeMethod:128 Stage 
>> late_setup METHOD otopi.plugins.gr_he_setup.vm.runvm.Plugin._late_setup
>> 2017-04-19 12:27:02 DEBUG otopi.plugins.gr_he_setup.vm.runvm 
>> runvm._late_setup:83 {'status': {'message': 'Done', 'code': 0}, 'items': 
>> [u'04ff4cf1-135a-4918-9a1f-8023322f89a3']}
>> 2017-04-19 12:27:02 ERROR otopi.plugins.gr_he_setup.vm.runvm 
>> runvm._late_setup:91 The following VMs have been found: 
>> 04ff4cf1-135a-4918-9a1f-8023322f89a3
>> 2017-04-19 12:27:02 DEBUG otopi.context context._executeMethod:142 method 
>> exception
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in 
>> _executeMethod
>> method['method']()
>>   File 
>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-setup/vm/runvm.py",
>>  line 95, in _late_setup
>> _('Cannot setup Hosted Engine with other VMs running')
>> RuntimeError: Cannot setup Hosted Engine with other VMs running
>> 2017-04-19 12:27:02 ERROR otopi.context context._executeMethod:151 Failed to 
>> execute stage 'Environment setup': Cannot setup Hosted Engine with other VMs 
>> running
>> 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:760 
>> ENVIRONMENT DUMP - BEGIN
>> 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:770 ENV 
>> BASE/error=bool:'True'
>> 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:770 ENV 
>> BASE/exceptionInfo=list:'[(, 
>> RuntimeError('Cannot setup Hosted Engine with other VMs running',), 
>> )]'
>> 2017-04-19 12:27:02 DEBUG otopi.context context.dumpEnvironment:774 
>> ENVIRONMENT DUMP - END
> James, generally this issue happens when the setup failed once and you tried 
> re running it again.  Can you clean it and deploy it again?  HE should come 
> up successfully. Below are the steps for cleaning it up.

Knarra,

I realize that. However, that is not the situation in my case. See above, at 
the mark - the UUID it is complaining about is the UUID of the hosted-engine it 
just installed. From the answers file generated from the run (whole thing 
below):

 OVEHOSTED_VM/vmUUID=str:04ff4cf1-135a-4918-9a1f-8023322f89a3

Also see the WARNs I mentioned previously, quoted below. Excerpt:

 Apr 19 12:29:20 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm root WARN 
 File: 
 /var/lib/libvirt/qemu/channels/04ff4cf1-135a-4918-9a1f-8023322f89a3.com.redhat.rhevm.vdsm
  already removed
 Apr 19 12:29:20 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm root WARN 
 File: 
 /var/lib/libvirt/qemu/channels/04ff4cf1-135a-4918-9a1f-8023322f89a3.org.qemu.guest_agent.0
  already removed
 Apr 19 12:29:30 sc5-ovirt-2.squaretrade.com vdsm[70062]: vdsm 
 ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Failed to connect 
 to broker, the number of errors has exceeded the limit (1)

I’m not clear on what it is attempting to do there, but it seems relevant.

I know there is no failed install left on the gluster volume, because when I 
attempt an install, part of my scripted prep process is deleting and recreating 
the Gluster volume. The below instructions are more or less what I’m doing 
already in a script[1]. (the gluster portion of the script process is: stop the 
volume, delete the volume, remove the mount point directory to avoid Gluster’s 
xattr problem with recycling directories, recreate the directory, change perms, 
create the volume, start the volume, set Ovirt-recc’ed volume options.)

-j

[1] We have a requirement for automated setup of all production resources, so 
all of this ends up being scripted.

> 1) vdsClient -s 0 list table | awk '{print $1}' | xargs vdsClient -s 0 destroy
> 
> 2) stop the volume and delete all the information inside the bricks from all 
> the hosts
> 
> 3) try to umount storage from /rhev/data-center/mnt/ - umount -f 
> /rhev/data-center/mnt/  if it is mounted
> 
> 4) remove all dirs from /rhev/data-center/mnt/ - rm -rf 
> /rhev/data-center/mnt/*
> 
> 5) start  volume again and start the deployment.
> 
> Thanks
> kasturi
>> 
>> 
 If I start it manually, the default DC is down, the default cluster has 
 the installation host in the cluster,  there is no storage, and the VM 
 doesn’t show up in the GUI. In this install run, I have not yet started 
 the engine manually.
>>> you wont be seeing HE vm until HE storage is imported into the UI. HE 
>>> storage will be automatically imported into the UI (which will import HE vm 
>>> too )once a 

[ovirt-users] Kill a long running task in oVirt 4.0.5

[Anantha Raghava]

Hi,

We are using oVirt 4.0.5. I tried to import an exported VM into the 
oVirt infrastructure. The process started and from last 24 hrs, it is 
still running and I am unable to kill it either.


I tried to use "stopTask" command, but host is reporting "stopTask" 
command is available. How do we kill the long running task?

--

Thanks & Regards,


Anantha Raghava


DISCLAIMER:
This e-mail communication and any attachments may be privileged and 
confidential to eXza Technology Consulting & Services, and are intended 
only for the use of the recipients named above If you are not the 
addressee you may not copy, forward, disclose or use any part of it. If 
you have received this message in error, please delete it and all copies 
from your system and notify the sender immediately by return e-mail. 
Internet communications cannot be guaranteed to be timely, secure, error 
or virus-free. The sender does not accept liability for any errors or 
omissions.



Do not print this e-mail unless required. Save Paper & trees.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.1.1 and ovn problems

[Gianluca Cecchi]

On Thu, Apr 20, 2017 at 6:54 PM, Gianluca Cecchi 
wrote:

> Hello,
> I installed some months ago a test setup in 4.1.0 with ovn.
> Now after updating engine and host to 4.1.1 it seems the services are up
> but it doesn't work.
> If I run a VM with a network device in OVN external provider, it cant'
> boot and I get this in engine.log:
>
>
> [snip]

>
> At the page
> https://www.ovirt.org/blog/2016/11/ovirt-provider-ovn/
>
> I see this note about ports:
>
> "
> Since OVS 2.7, OVN central must be configured to listen to requests on
> appropriate ports:
>
> ovn-sbctl set-connection ptcp:6642
> ovn-nbctl set-connection ptcp:6641
> "
>
> and in my case I indeed passed from 2.6.90 to 2.7.0...
>
> Do I need to run these two commands?
> Or any other configuration settings?
>
> Thanks in advance,
> Gianluca
>

I confirm that after running these two commands all work ok again and I'm
able to start a VM with a vnic provided by the OVN provider

[root@ractorshe ~]# ovn-sbctl set-connection ptcp:6642
[root@ractorshe ~]# ovn-nbctl set-connection ptcp:6641
[root@ractorshe ~]#
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Extending data domain size

[Alexis HAUSER]

Hi, 

Is it possible in ovirt-4.0 to extend the size of a data domain ? 
In theory it should be possible with LVM to do it, but does ovirt provide this 
functionality ? 

Regards 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Communicate between the guest vm's hosted on, different hosts on different data centres using OVS

[Charles Tassell]

Hmm, so you have 2 10G ports on each host.  1 port is currently in use 
with oVirt, and the other isn't?  Then I think you just add a new 
network in the Networks tab called OVNLink, then go into the Hosts tab, 
click on each host and then on the Network Interfaces tab in the bottom 
of the window and assign the unused 10G network device to that link.


I haven't used OVN with oVirt, but that would work with regular 
networking so I think it should work with OVN.


If the link is already in use, you should be able to do the same thing 
only when you add the new network set it up with a VLAN ID. If you are 
going through a switch then the switch will have to be setup to handle 
the VLANs.



On 2017-04-20 10:07 PM, Linov Suresh wrote:

Hi Charles,

We use an Ethernet cable to connect between the hosts through 10G port.

We want to use the guest VM's hosted on different hosts 10G network. 
oVirt already supports SR-IOV. So we should guest 10G speed for our VM's.


In KVM we can create a second bridge and add the 10G interface to the 
bridge would do the trick.


But in oVirt how do we do this? We want to use our OVs network, which 
was created using OVN Provider.


Linov Suresh


On Thu, Apr 20, 2017 at 6:59 PM, Charles Tassell > wrote:


Hi Suresh,

  You would need to connect the two OVN instances somehow.  If
it's just two single hosts, I think the easiest way would be to
create a VPN connection between the two hosts with OpenVPN or the
like and then add the tun/tap interfaces into the OVN on each
box.  You might run into problems if you start adding more hosts
though, as if the host with the VPN goes down it would disconnect
the two datacenters.

  If the two datacenters are on the same physical network (ie, you
just mean oVirt datacenter and not different colocation providers)
then adding a VLAN to the NICs connected to the OVN interface
would work.  You would probably have to setup some sort of channel
bonding/LACP as you add more hosts, but OVN should be able to
handle that simply enough.

On 2017-04-20 07:33 PM, users-requ...@ovirt.org
 wrote:

Date: Thu, 20 Apr 2017 14:43:26 -0400
From: Linov Suresh >
To: users@ovirt.org 
Subject: [ovirt-users] Communicate between the guest vm's
hosted on
different hosts on different data centres using OVS
Message-ID:
   

Re: [ovirt-users] Hosted engine Single Sign-On to VM with freeIPA not working

[Paul]

Hi Ondra,
It is over a year since the last message, so I thought let's give this a new
try.
Did setup a new test environment with latest versions, all RH-family (Centos
7.3 with ovirt 4.1)
Ovirt engine works fine with IPA, in the console I can log in with
credentials. But SSO still does not work :-(
Unfortunately the workaround with "authconfig --enablenis --update" breaks
polkit.service and cascades in a lot of other fails making the VM failing to
boot properly.
Any suggestions?
Regards,
Paul

System setup:
--- Engine
[root@engine ~]# cat /etc/redhat-release 
CentOS Linux release 7.3.1611 (Core) 
[root@engine ~]# uname -a
Linux engine.domain.com 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[root@engine ~]# rpm -qa | grep ovirt
ovirt-engine-setup-plugin-ovirt-engine-common-4.1.1.8-1.el7.centos.noarch
ovirt-imageio-proxy-1.0.0-0.201701151456.git89ae3b4.el7.centos.noarch
ovirt-iso-uploader-4.0.2-1.el7.centos.noarch
ovirt-engine-setup-plugin-ovirt-engine-4.1.1.8-1.el7.centos.noarch
ovirt-engine-tools-4.1.1.8-1.el7.centos.noarch
ovirt-engine-backend-4.1.1.8-1.el7.centos.noarch
ovirt-engine-extension-aaa-jdbc-1.1.4-1.el7.centos.noarch
ovirt-engine-extension-aaa-ldap-setup-1.3.1-1.el7.centos.noarch
ovirt-release41-4.1.1.1-1.el7.centos.noarch
ovirt-setup-lib-1.1.0-1.el7.centos.noarch
ovirt-imageio-common-1.0.0-1.el7.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch
ovirt-engine-extensions-api-impl-4.1.1.8-1.el7.centos.noarch
ovirt-engine-extension-aaa-ldap-1.3.1-1.el7.centos.noarch
ovirt-imageio-proxy-setup-1.0.0-0.201701151456.git89ae3b4.el7.centos.noarch
ovirt-engine-dwh-4.1.1-1.el7.centos.noarch
ovirt-engine-setup-plugin-websocket-proxy-4.1.1.8-1.el7.centos.noarch
ovirt-engine-tools-backup-4.1.1.8-1.el7.centos.noarch
ovirt-engine-setup-4.1.1.8-1.el7.centos.noarch
ovirt-engine-vmconsole-proxy-helper-4.1.1.8-1.el7.centos.noarch
ovirt-engine-dashboard-1.1.0-7.el7.centos.noarch
ovirt-engine-metrics-1.0.2-1.el7.centos.noarch
ovirt-engine-userportal-4.1.1.8-1.el7.centos.noarch
ovirt-engine-dbscripts-4.1.1.8-1.el7.centos.noarch
ovirt-engine-4.1.1.8-1.el7.centos.noarch
ovirt-engine-wildfly-10.1.0-1.el7.x86_64
python-ovirt-engine-sdk4-4.1.3-2.el7.centos.x86_64
ovirt-vmconsole-proxy-1.0.4-1.el7.centos.noarch
ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch
ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch
ovirt-engine-lib-4.1.1.8-1.el7.centos.noarch
ovirt-host-deploy-java-1.6.3-1.el7.centos.noarch
ovirt-engine-dwh-setup-4.1.1-1.el7.centos.noarch
ovirt-engine-websocket-proxy-4.1.1.8-1.el7.centos.noarch
ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.1.1.8-1.el7.centos.noarch
ovirt-engine-webadmin-portal-4.1.1.8-1.el7.centos.noarch
ovirt-engine-restapi-4.1.1.8-1.el7.centos.noarch
ovirt-guest-agent-common-1.0.13-2.el7.noarch
ovirt-host-deploy-1.6.3-1.el7.centos.noarch
ovirt-vmconsole-1.0.4-1.el7.centos.noarch
ovirt-engine-extension-aaa-misc-1.0.1-1.el7.noarch
ovirt-web-ui-0.1.2-4.el7.centos.x86_64
ovirt-engine-setup-base-4.1.1.8-1.el7.centos.noarch

---  IPA 
[root@ipa01 log]# cat /etc/redhat-release 
CentOS Linux release 7.3.1611 (Core)
[root@ipa01 log]# uname -a
Linux ipa01.domain.com 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[root@ipa01 log]# rpm -qa | grep ipa
python2-ipalib-4.4.0-14.el7.centos.7.noarch
python2-ipaserver-4.4.0-14.el7.centos.7.noarch
libipa_hbac-1.14.0-43.el7_3.14.x86_64
python-libipa_hbac-1.14.0-43.el7_3.14.x86_64
python-iniparse-0.4-9.el7.noarch
ipa-common-4.4.0-14.el7.centos.7.noarch
ipa-client-common-4.4.0-14.el7.centos.7.noarch
python-ipaddress-1.0.16-2.el7.noarch
sssd-ipa-1.14.0-43.el7_3.14.x86_64
python2-ipaclient-4.4.0-14.el7.centos.7.noarch
ipa-client-4.4.0-14.el7.centos.7.x86_64
ipa-server-4.4.0-14.el7.centos.7.x86_64
ipa-server-common-4.4.0-14.el7.centos.7.noarch
ipa-admintools-4.4.0-14.el7.centos.7.noarch
ipa-server-dns-4.4.0-14.el7.centos.7.noarch

---Client---
[root@ad01 ~]# cat /etc/redhat-release 
CentOS Linux release 7.3.1611 (Core) 
[root@ad01 ~]# uname -a
Linux ad01.domain.com 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
 [root@ad01 ~]# rpm -qa | grep ipa
python2-ipaclient-4.4.0-14.el7.centos.7.noarch
python-iniparse-0.4-9.el7.noarch
ipa-client-common-4.4.0-14.el7.centos.7.noarch
python-libipa_hbac-1.14.0-43.el7_3.14.x86_64
ipa-client-4.4.0-14.el7.centos.7.x86_64
sssd-ipa-1.14.0-43.el7_3.14.x86_64
python-ipaddress-1.0.16-2.el7.noarch
python2-ipalib-4.4.0-14.el7.centos.7.noarch
ipa-common-4.4.0-14.el7.centos.7.noarch
libipa_hbac-1.14.0-43.el7_3.14.x86_64
[root@ad01 ~]# rpm -qa | grep ovirt
ovirt-guest-agent-pam-module-1.0.13-2.el7.x86_64
ovirt-guest-agent-common-1.0.13-2.el7.noarch
ovirt-guest-agent-gdm-plugin-1.0.13-2.el7.noarch

Relevant logs:
--- client ---
[root@ad01 ~]# vi /var/log/messages
Apr 21 10:07:59 ad01 [sssd[krb5_child[2635]]]: Preauthentication failed
Apr 21 10:07:59 ad01 [sssd[krb5_child[2635]]]: 

Re: [ovirt-users] Question about Huge Pages

[Michal Skrivanek]

> On 20 Apr 2017, at 17:39, Gianluca Cecchi  wrote:
> 
> On Thu, Apr 20, 2017 at 10:35 AM, Michal Skrivanek  > wrote:
> 
>> On 19 Apr 2017, at 16:28, Gianluca Cecchi > > wrote:
>> 
>> On Wed, Apr 19, 2017 at 3:44 PM, Martin Polednik > > wrote:
>> 
>> 
>> If you are using recent CentOS (or I guess Fedora), there isn't any
>> extra setup required. Just create the custom property:
>> 
>> Both my engine and my hosts are CentOS 7.3 + updates
> 
> that’s good
> 
>>  
>> 
>> On the host where engine is running:
>> 
>> $ engine-config -s "UserDefinedVMProperties=hugepages=^.*$"
>> $ service ovirt-engine restart
>> 
>> and you should see 'hugepages' when editing a VM under custom properties.
>> 
>> So no vdsm hook at all to install?
> 
> today you still need the hook.
> 
>> 
>>  
>> Set the number to (desired memory / 2048) and you're good to go. The
>> VM will run with it's memory backed by hugepages.
>> 
>> As in sysctl.conf? So that if I want 4Gb of Huge Pages I have to set 2048?
> 
> yes. there might be some 
> 
>> 
>>  
>> If you need
>> hugepages even inside the VM, do whatever you would do on a physical
>> host.
>> 
>> mpolednik
>> 
>> 
>> yes, the main subject is to have Huge Pages inside the guest, so that Oracle 
>> RDBMS at startup detect them and use them
> 
> yes, so if you do that via sysctl.conf on real HW just do the same here, or 
> modify kernel cmdline.
> 
> Note that those are two separate things
> the hook is making QEMU process use hugepages memory in the host - that 
> improves performance of any VM
> then how it looks in guest is no concern to oVirt, it’s guest-side hugepages. 
> You can enable/set them regardless the previous step, which may be fine if 
> you just want to expose the capability to some app  - e.g. in testing that 
> the guest-side Oracle can work with hugepages in the guest.
> But you probably want both Oracle to see hugepages and also actually use them 
> - then you need both reserve that on host for qemu process and then inside 
> guest reserve that for oracle. I.e. you need to add a “buffer” on host side 
> to accommodate the non-hugepages parts of the guest e.g. on 24GB host you can 
> reserve 20GB hugepages for VMs to use, and then run a VM with 20GB memory, 
> reserving 16GB hugepages inside the guest for oracle to use.
> 
> Thanks,
> michal
> 
>> 
>> Gianluca 
> 
> 
> I'm making some tests right now. 
> Steps done: 
> - configure huge pages on hypervisor
> 
> [root@ractor ~]# cat /etc/sysctl.d/huge-pages.conf 
> # 20/04/2017 8Gb
> vm.nr_hugepages = 4096
> [root@ractor ~]# 
> 
> rebooted host (I also updated in the mean time it to latest 4.1.1 packages 
> with vdsm-4.19.10.1-1.el7.centos.x86_64 and 
> vdsm-hook-hugepages-4.19.10.1-1.el7.centos.noarch)
> I also set "transparent_hugepage=never" boot parameter because I know that 
> they are in conflict with Huge Pages
> 
> So the situation is:
> 
> [root@ractor ~]# cat /proc/cmdline 
> BOOT_IMAGE=/vmlinuz-3.10.0-514.16.1.el7.x86_64 root=/dev/mapper/centos-root 
> ro rd.lvm.lv =centos/root rd.lvm.lv 
> =centos/swap rhgb quiet LANG=en_US.UTF-8 
> transparent_hugepage=never
> [root@ractor ~]# 
> 
> [root@ractor ~]# cat /proc/meminfo | grep -i huge
> AnonHugePages: 0 kB
> HugePages_Total:4096
> HugePages_Free: 4096
> HugePages_Rsvd:0
> HugePages_Surp:0
> Hugepagesize:   2048 kB
> [root@ractor ~]# 
> 
> I edited a pre-existing CentOS 6 VM setting for it 8Gb of ram and 2048 pages 
> (4Gb) in custom property forhugepages.
> 
> When I power on I get this addition in qemu-kvm process definition as 
> expected:
> 
> -mem-path /dev/hugepages/libvirt/qemu
> 
> I noticed that now I have on host
> 
> [root@ractor vdsm]# cat /proc/meminfo | grep -i huge
> AnonHugePages: 0 kB
> HugePages_Total:6144
> HugePages_Free: 2048
> HugePages_Rsvd:0
> HugePages_Surp:0
> Hugepagesize:   2048 kB
> [root@ractor vdsm]# 
> 
> So apparently it did allocated 2048 new huge pages...
> Does it mean that actually I have not to pre-allocate huge pages at all on 
> host and it eventually will increase them (but not able to remove then I 
> suppose) ?
> 
> Anyway the count doesn't seem correct... because it seems that a total of 
> 4096 pages are in use/locked... (HugePages_Total - HugePages_Free + 
> HugePages_Rsvd)
> while they should be 2048.
> 
> [root@ractor vdsm]# ll /dev/hugepages/libvirt/qemu/
> total 0
> [root@ractor vdsm]# ll /hugetlbfs/libvirt/qemu/
> total 0
> [root@ractor vdsm]# 
> 
> If I power off the VM
> 
> [root@ractor vdsm]# cat /proc/meminfo | grep -i huge
> AnonHugePages: 0 kB
> HugePages_Total:4096
> HugePages_Free: 4096
> HugePages_Rsvd:0
> HugePages_Surp:0
> Hugepagesize:   2048 kB
>