oVirt Host installation oVirt Host 4 on Fedora 23 with VMWare
WorkStation 12
- · Using Fedora23 as the host.
- · Basic Minimal Installation of Fedora 23
- · Fedora23 machine is installed and running on VMWare WorkStation version 12.
- · The base machine is AMD Opteron 5 based on which the ovirt engine 4.0 is installed is one of the Fedora 23 Server.
- · The base machine is a laptop in whose BIOS SVM VIRTUALIZATION is enabled.
- · The Virtual machine processor settings for the oVirt Engine as well as oVirt host are as set in the VM Properties on the VMWare Workstation as “Virtualize Intel VT-x/EPT or AMD-V/RI
·
[root@ovirthost1 ~]# uname -a
Linux ovirthost1.example.com 4.2.3-300.fc23.x86_64 #1 SMP Mon
Oct 5 15:42:54 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@ovirthost1 ~]# cat /etc/redhat-release
Fedora release 23 (Twenty Three)
[root@ovirthost1 ~]#
1) Install the RPM for the repos of ovirt 4.0
wget
http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
rpm -ivh ovirt-release40.rpm
2) Confirm the repo is visible and vdsm packages are seen
cd /var/cache/yum
&& rm -rf * && yum clean all && yum repolist
The list of the repositories looks like below.
dnf repolist
Last metadata expiration check performed 0:07:36 ago on Mon
Jun 27 08:21:19 2016.
repo id
repo name
status
*fedora
Fedora 23 - x86_64 46,074
ovirt-4.0
Latest oVirt 4.0 Release 180
ovirt-4.0-patternfly1 Copr repo for patternfly1 owned by
patternfly 2
*updates
Fedora 23 - x86_64 - Updates 19,666
virtio-win-stable
virtio-win builds roughly matching what was shipped 2
[root@ovirthost1 ~]#
3) Ensure that these repositories are seen on the fedora 23
host as these will be the requirement when the ovirt Engine installs this as
the oVirt host. The process of installation of the fedora23s server as oVirt
hosts installs rpms which come from this repos.
4) For my setup the firewall is disabled also the
Network.Manager service is stopped and disabled as seen.
systemctl disable
firewalld.service
systemctl stop
firewalld.service
systemctl disable
Network.Manager
systemctl stop
Network.Manager
5) Ensure that the libvirtd service is enabled for autostart.
Also libvirtd has to be running.
[root@ovirthost1 ~]# systemctl enable libvirtd.service
[root@ovirthost1 ~]#
[root@ovirthost1 ~]# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded
(/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Drop-In:
/etc/systemd/system/libvirtd.service.d
└─unlimited-core.conf
Active: active
(running) since Thu 2016-06-02 20:53:05 IST; 3 weeks 3 days ago
6) Add the host to the oVirt-Engine. (Login to the oVirt
Engine using admin user at https://<ovirt_Engine_FQDN>:443/ovirt-engine)
7) As the oVirt Engine adds the host to a cluster which you
create in the GUI or the default cluster and the center, the following are seen
as the host gets successfully added to the cluster in the oVirt Engine.
These logs are from ovirt-ENgine server at the location
/var/log/messages/ovirt-engine/engine.log
2016-06-27 02:09:54,448 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler5) [1cec4f0d] Correlation ID: null, Call Stack: null,
Custom Event ID: -1, Message: Critical, Low disk space. Host
ovirthost.example.com has less than 500 MB of free space left on:
/var/run/vdsm/, /tmp. Low disk space might cause an issue upgrading this host.
2016-06-27 02:09:55,409 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler8) [] Fetched 0 VMs from VDS
'4244422c-ea6d-4ab3-abe7-bb0581f5efde'
2016-06-27 02:10:11,429 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler10) [4e5952e7] Fetched 0 VMs from VDS
'4244422c-ea6d-4ab3-abe7-bb0581f5efde'
2016-06-27 02:10:27,457 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler3) [50cd768e] Fetched 0 VMs from VDS
'4244422c-ea6d-4ab3-abe7-bb0581f5efde'
2016-06-27 02:10:43,482 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler2) [6c6b13f9] Fetched 0 VMs from VDS
'4244422c-ea6d-4ab3-abe7-bb0581f5efde'
2016-06-27 02:10:59,504 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler9) [3a942f11] Fetched 0 VMs from VDS
'4244422c-ea6d-4ab3-abe7-bb0581f5efde'
2016-06-27 02:11:15,530 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler8) [] Fetched 0 VMs from VDS
'4244422c-ea6d-4ab3-abe7-bb0581f5efde'
After the
server is added successfully as the host of the cluster in one of the data
centers, you can see that the "libvirtd" service is up and running as
below.
[root@ovirthost ~]# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded
(/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Drop-In:
/etc/systemd/system/libvirtd.service.d
└─unlimited-core.conf
Active: active (running)
since Mon 2016-06-27 11:23:36 IST; 10h ago
Docs:
man:libvirtd(8)
http://libvirt.org
Main PID: 19993
(libvirtd)
CGroup:
/system.slice/libvirtd.service
└─19993
/usr/sbin/libvirtd --listen
Jun 27 11:23:34 ovirthost.example.com systemd[1]: Starting
Virtualization dae...
Jun 27 11:23:36 ovirthost.example.com libvirtd[19993]: libvirt
version: 1.2.1...
Jun 27 11:23:36 ovirthost.example.com libvirtd[19993]: Module
/usr/lib64/libv...
Jun 27 11:23:36 ovirthost.example.com libvirtd[19993]: Module
/usr/lib64/libv...
Jun 27 11:23:36 ovirthost.example.com libvirtd[19993]: Module
/usr/lib64/libv...
Jun 27 11:23:36 ovirthost.example.com libvirtd[19993]: Module
/usr/lib64/libv...
Jun 27 11:23:36 ovirthost.example.com libvirtd[19993]: Module
/usr/lib64/libv...
Jun 27 11:23:36 ovirthost.example.com systemd[1]: Started
Virtualization daemon.
Hint: Some lines were ellipsized, use -l to show in full.
No comments:
Post a Comment