Memory usage inclines
by Tony Brian Albers
Hi guys,
We have a small test installation here running around 30 vms on 2
hosts.
oVirt 4.2.5.3
The hosts each have 512 GB memory, and the vms are sized with 4-8 GB
each.
I have noticed that over the last months, the memory usage in the
dashboard has been increasing and is now showing 946.8 GB used of
1007.2 GB.
What can be causing this?
TIA,
--
--
Tony Albers
Systems Architect
Systems Director, National Cultural Heritage Cluster
Royal Danish Library, Victor Albecks Vej 1, 8000 Aarhus C, Denmark.
Tel: +45 2566 2383 / +45 8946 2316
6 years
Ovirt Authentication extensions
by darkytoo＠gmail.com
I've seen the articles about hooking ovirt to AD and keycloak, but is there a way to hook it to something like ADFS? I'd like to have it require an MFA login and I know I can do it with ADFS.
6 years
Gluster with two ovirt nodes
by Stefan Wolf
Hello,
i like to set up glusterfs with two ovirt nodes and on more "normal" node
is this possible?
i 've setup glusterfs in cli on two ovirt nodes and 3rd network storage.
glusterfs is up and running.
But now i like to get something like VIP with ctdb for example. is there
any possibility to set this up with ovirt?
Or do i *ve to setup ovirt manually in centos to install ctdb?
Or are there any other ideas?
thank you stefan
6 years
Not able to install HostedEngine
by Stefan Wolf
Hello,
i like to setup a complete new cluster
I install the version 4.2.1.7
I set up ip during installation process
After reboot I enable by changing
/etc/sysconfig/network-scripts/ifcfg-ens1f0 from ONBOOT=no to yes
Than I try to install hosted-engine as described here:
https://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hoste...
I prepare the installation process with yum install ovirt-engine-appliance
then i 've tried both variants grafical installation with cockpit and the
cli
after setting up the network, the network is no longer working and the
installtion will break
everything seems fine but network isn't running
a reboot will not help
thx stefan
[image: image.png]
6 years
Ovirt 4.3 Alpha AMD 2970WX Windows VM creation and NUMA
by Darin Schmidt
Not sure if Users is the best place for this as Im using 4.3 to test support for my AMD 2970WX Threadripper but While trying to setup a Windows VM, it fails. I have a working CentOS 7 running. Heres what I get when I try to startup the VM.
VM Windows-Darin is down with error. Exit message: internal error: process exited while connecting to monitor: WARNING: Image format was not specified for '/dev/sg0' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
2018-12-02T18:43:05.358741Z qemu-kvm: warning: CPU(s) not present in any NUMA nodes: CPU 10 [socket-id: 10, core-id: 0, thread-id: 0], CPU 11 [socket-id: 11, core-id: 0, thread-id: 0], CPU 12 [socket-id: 12, core-id: 0, thread-id: 0], CPU 13 [socket-id: 13, core-id: 0, thread-id: 0], CPU 14 [socket-id: 14, core-id: 0, thread-id: 0], CPU 15 [socket-id: 15, core-id: 0, thread-id: 0]
2018-12-02T18:43:05.358791Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future
2018-12-02T18:43:05.359052Z qemu-kvm: can't apply global EPYC-x86_64-cpu.hv-synic=on: Property '.hv-synic' not found.
NUMA doesnt seem to resolve the issue any even if I set NUMA to be 1 and place it on a NUMA that has 12 cores and 64GB ram. I also dont fully understand NUMA because it creates 4 NUMA sockets even though technically there should be 2 correct? I dont get how NUMA is setup, but either way it doesnt help resolve any issues.
[root@ovirt ~]# numactl --hardware
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 24 25 26 27 28 29
node 0 size: 65429 MB
node 0 free: 54322 MB
node 1 cpus: 12 13 14 15 16 17 36 37 38 39 40 41
node 1 size: 0 MB
node 1 free: 0 MB
node 2 cpus: 6 7 8 9 10 11 30 31 32 33 34 35
node 2 size: 32754 MB
node 2 free: 27699 MB
node 3 cpus: 18 19 20 21 22 23 42 43 44 45 46 47
node 3 size: 0 MB
node 3 free: 0 MB
node distances:
node 0 1 2 3
0: 10 16 16 16
1: 16 10 16 16
2: 16 16 10 16
3: 16 16 16 10
link to my messages and vdsm log
https://drive.google.com/open?id=1v-Wjcj7xLZIcR2GKR-P659yE14r1-hsz
https://drive.google.com/open?id=1BHvcS2Dgan68hQkVdOmme1gP1ciSsejL
6 years
4.2.7 & centos 7.6 dependency problems
by Demeter Tibor
Dear All,
I would like to upgrade my ovirt 4.2.5 to 4.2.7.
The hosted engine upgrade was success, but on the nodes i've got an dependency error:
---> Package mesa-libgbm.x86_64 0:18.0.5-3.el7 will be installed
--> Processing Dependency: mesa-libglapi = 18.0.5-3.el7 for package: mesa-libgbm-18.0.5-3.el7.x86_64
--> Processing Dependency: libwayland-server.so.0()(64bit) for package: mesa-libgbm-18.0.5-3.el7.x86_64
---> Package nbdkit.x86_64 0:1.2.7-2.el7 will be installed
---> Package nbdkit-plugin-python2.x86_64 0:1.2.7-2.el7 will be installed
--> Processing Dependency: nbdkit-plugin-python-common = 1.2.7-2.el7 for package: nbdkit-plugin-python2-1.2.7-2.el7.x86_64
---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
--> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
---> Package python2-blockdev.x86_64 0:2.18-3.el7 will be installed
---> Package python2-futures.noarch 0:3.1.1-5.el7 will be installed
--> Running transaction check
---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed
---> Package mesa-libglapi.x86_64 0:18.0.5-3.el7 will be installed
---> Package nbdkit-plugin-python-common.x86_64 0:1.2.7-2.el7 will be installed
---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
--> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be erased
---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
--> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
--> Finished Dependency Resolution
Error: Package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 (updates)
Requires: nbdkit(x86-64) = 1.2.6-1.el7_6.2
Available: nbdkit-1.2.6-1.el7.x86_64 (base)
nbdkit(x86-64) = 1.2.6-1.el7
Available: nbdkit-1.2.6-1.el7_6.2.x86_64 (updates)
nbdkit(x86-64) = 1.2.6-1.el7_6.2
Installing: nbdkit-1.2.7-2.el7.x86_64 (ovirt-4.2-epel)
nbdkit(x86-64) = 1.2.7-2.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
How can I solve this?
Thanks in advance,
Regards,
Tibor
6 years
Network Setup after ovirt node Install and before add node to cluster
by Stefan Wolf
Hello,
I ve downloaded an installed OVIRT NODE 4.2.7.1.
During the installation I ‘ve setup a static ip (I ‘ve also tried dhcp, both work)
The installation passes and after the reboot ovirt node starts without any problems.
BUT the network is not configured.
I know https://www.ovirt.org/documentation/install-guide/chap-oVirt_Nodes/ and I know
https://www.ovirt.org/documentation/admin-guide/chap-Hosts/
and now I am between these two documents
oVirt is installed but network is not configured to add it to datacenter
of course I know the scripts under /etc/sysconfig/network-scripts
do I really have do edit it manuel?
if I change ip in command line
ip a add … dev..
and ip route add …
it fails to add node to datacenter
- with one of the last version I ‘ve added the IP address in bash
- added the host to datacenter,
- after reboot readd the ip address in bash after reboot
- an then I could change network settings in oVirt Manger
What is best practices for adding a node to datacenter when the ip address is not assigned after installation
Thx shb
6 years
Ovirt Maximums
by Brian Wilson
Is there a resource available that would describe the configurable maximums for the Ovirt Engine and Ovirt Nodes.
Things like:
How many Logical Networks per host?
If one does not exist does anyone have any experiences with reaching limits that caused issues specifically with regards to the number of networks on hosts.
6 years
