Oracle VM Server x86: Installing Oracle VM Manager

First check the hardware requirements:

After downloading the right image (please do not laugh, this is really a problem), inside a Oracle Linux the following steps have to be done:

mount /dev/cdrom /mnt
mount: /dev/sr0 is write-protected, mounting read-only

and

# ls /mnt/
components       oracle-validated.params  OvmSDK_3.4.4.1709.zip  sample.yml
createOracle.sh  ovmm-installer.bsx       runInstaller.sh        TRANS.TBL

First try:

[root@localhost ~]# /mnt/createOracle.sh
Missing required package, Oracle VM Manager requires 'iptables-services' to be installed, you can use 'yum install iptables-services' to install it.

Ok:

[root@localhost ~]# yum install iptables-services

And here we go:

# /mnt/createOracle.sh
Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service.
Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
Created symlink from /etc/systemd/system/basic.target.wants/iptables.service to /usr/lib/systemd/system/iptables.service.
Adding group 'oinstall' with gid '54321' ...
Adding group 'dba'
Adding user 'oracle' with user id '54321', initial login group 'dba', supplementary group 'oinstall' and  home directory '/home/oracle' ...
Changing ownership of '/home/oracle' to oracle:dba
Creating user 'oracle' succeeded ...
For security reasons, no default password was set for user 'oracle'. If you wish to login as the 'oracle' user, you will need to set a password for this account.
Verifying user 'oracle' OS prerequisites for Oracle VM Manager ...
oracle    soft    nofile        8192
oracle    hard    nofile        65536
oracle    soft    nproc        2048
oracle    hard    nproc        16384
oracle    soft    stack        10240
oracle    hard    stack        32768
oracle    soft    core        unlimited
oracle    hard    core        unlimited
Setting  user 'oracle' OS limits for Oracle VM Manager ...
Altered file /etc/security/limits.conf
Original file backed up at /etc/security/limits.conf.orabackup
Verifying & setting of user limits succeeded ...
Creating mountpoint '/u01' ...
Modifying iptables for OVM
Adding rules to enable access to:
     7002  : Oracle VM Manager https
       123 : NTP
     10000 : Oracle VM Manager CLI Tool
Redirecting to /bin/systemctl status iptables.service
Redirecting to /bin/systemctl status iptables.service
Redirecting to /bin/systemctl restart iptables.service
iptables: Saving firewall rules to /etc/sysconfig/iptables:[  OK  ]
Redirecting to /bin/systemctl restart iptables.service
Rules added.

Before starting the "runInstaller.sh" i had to install the following packages:

yum install zip unzip net-tools perl-Data-Dumper

But then:

[root@localhost ~]# /mnt/runInstaller.sh

Oracle VM Manager Release 3.4.4 Installer

Oracle VM Manager Installer log file:
/var/log/ovmm/ovm-manager-3-install-2018-02-22-163152.log

Please select an installation type:
   1: Install
   2: Upgrade
   3: Uninstall
   4: Help

   Select Number (1-4): 1

Verifying installation prerequisites ...

And ready for login:

Oracle database 18c: Installation via RPM

After the release of 18c i did a short dive into the "guide to new features" announced on oracle.com:

 And take a look, what can be found in "Database Overall -> Install, config, and patch":

RPM-based Database Installation

RPM-based Database Installation (RDI) enables an RPM-based installation of the Oracle Database software. Using the rpm-ivh command, an RPM-based database installation performs the preinstallation validations, extracts the packaged software, reassigns the ownership of the extracted software to the preconfigured user and groups, maintains the Oracle inventory, and executes all the root operations required to complete the Oracle Database software installation.
RPM-based Database Installation enables you to leverage an RPM framework to easily deploy Oracle Database.

A kind of rpm installation was introduced for the installation of grid infrastructure in 12.2 (oracle documentation): Image based installation
So no worries, you have to start the runInstaller.sh after rpm -i. But let's see, how you have to specify the Oracle_Home in this rpm-process.

EDIT: On 20th july 2018 the documentation is released. See here.
EDIT2: October 2018: Installation done via rpm

Oracle VM Server x86: Installation walkthrough / step by step for a node/server

Last week i tried to setup Oracle VM. For all who are interested, here a short walkthrough.
First the VirtualBox Setup: The VM which should contain the Oracle VM server:

Let's boot:

 

Next reboot:

 And here we go:

Ubuntu Kernel: Adding a new menuentry as default before menuentry 'Ubuntu' (grub)

After the problem with s2disk/hibernate on my Ubuntu 17.10 i wanted to change the grub boot menu:
I wanted to add my new default kernel at the beginning  - before the 'Ubuntu' menuentry.

Adding the menuentry inside /boot/grub/grub.cfg does not work, because after the first kernel update the command update-grub will overwrite all changes.

Easiest way:
Go to /etc/grub.d/ and move

mv 40_custom 09_custom

Inside 09_custom add your new menuentry (just copy the one you want from /boot/grub/grub.cfg):

root@zerberus:/etc/grub.d# cat 09_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
        menuentry 'Ubuntu, mit Linux 4.13.0-17-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-17-generic-advanced-40d34826-4f8a-aefc' {
                recordfail
                load_video
                gfxmode $linux_gfx_mode
                insmod gzio
                if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
                insmod part_gpt
                insmod ext2
                set root='hd0,gpt5'
                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  40d34826-4f8a-aefc-d422f755d339
                else
                  search --no-floppy --fs-uuid --set=root 40d34826-4f8a-aefc                fi
                echo    'Linux 4.13.0-17-generic wird geladen …'
                linux   /boot/vmlinuz-4.13.0-17-generic root=UUID=40d34826-4f8a-aefc ro  noplymouth resume=UUID=709f3f5a-5e73-b42d-b93915cea971
                echo    'Initiale Ramdisk wird geladen …'
                initrd  /boot/initrd.img-4.13.0-17-generic
        }

 And then run update-grub once again and you are done....