Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices
Copyright Notice
Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
License Restrictions Warranty/Consequential Damages Disclaimer
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
Warranty Disclaimer
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
Restricted Rights Notice
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
Hazardous Applications Notice
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Third-Party Content, Products, and Services Disclaimer
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Alpha and Beta Draft Documentation Notice Disclaimer
If this document is in preproduction status:
This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
E53499-05
July 2014
Abstract
This document contains information about the initial release of Oracle Linux 7. This document may be updated after it is released. To check for updates to this document, and to view other Oracle documentation, refer to the Documentation section on the Oracle Technology Network (OTN) Web site:
http://www.oracle.com/technology/documentation/
http://www.oracle.com/technetwork/server-storage/linux/overview/index.html
This document is intended for users and administrators of Oracle Linux 7. It describes potential issues and the corresponding workarounds you may encounter while using Oracle Linux 7. Oracle recommends that you read this document before installing Oracle Linux 7.
Document generated on: 2014-07-10 (revision: 2088)
Table of Contents
The Oracle Linux 7 Release Notes provides a summary of the new features and known issues in the initial release of Oracle Linux 7.
This document is written for system administrators who want to use Oracle Linux 7. It is assumed that readers have a general understanding of the Linux operating system.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
The latest version of this document and other documentation for this product are available at:
http://www.oracle.com/technetwork/server-storage/linux/documentation/index.html
The following text conventions are used in this document:
Convention | Meaning |
|---|---|
boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
| Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |
Table of Contents
This section describes the new features that Oracle Linux 7 introduces and the major changes from the previous release of Oracle Linux.
You can install Oracle Linux 7 on x86-64 systems with up to 2048 logical CPUs and 64 TB of memory. The theoretical upper limit is 5120 logical CPUs and 64 TB of memory, but this configuration is not supported. A minimum of 2 logical CPUs and 1 GB of memory per logical CPU is recommended. Although the minimum disk space required for installation is 1GB, a minimum of 5 GB is recommended.
The following table lists the maximum file size and maximum file system size for the btrfs, ext4, and XFS file systems.
File System Type | Maximum File Size | Maximum File System Size |
|---|---|---|
btrfs | 50 TB | 50 TB |
ext4 | 50 TB | 50 TB |
XFS | 16 TB | 500 TB |
The maximum supported size for a bootable LUN is 50 TB. GPT and UEFI support are required for LUNs larger than 2 TB.
The maximum size of the address space that is available to each process is 128 TB.
Oracle Linux 7 supports the use of the following kernels:
Red Hat Compatible Kernel (RHCK), based on mainline Linux version 3.10.
Unbreakable Enterprise Kernel Release 3 (UEK R3), starting with 3.8.13, based on mainline Linux version 3.8. This is the default kernel.
UEFI Secure Boot is not currently supported with UEK R3.
The Anaconda installer has been enhanced and includes the following notable features:
An enhanced graphical interface.
A new text interface that can be used in a write-only mode.
Support for non-partitioned, directly-formatted devices.
tmpfs configuration.
LVM thin provisioning.
Configuration of btrfs or XFS for the root file system. Note
that the file system type for /boot
cannot be btrfs.
The default file system type is XFS, which replaces ext4.
Encryption of swap and all file systems except for
/boot. For a btrfs file system, the
encryption applies to all subvolumes.
Bonding and teaming of network interfaces.
Apache HTTP Server version 2.4 provides the following notable features:
The event Multi-Processing Module (MPM) and integrated proxy module support for the FastCGI protocol allow the server to serve more concurrent requests.
Improvements to asynchronous read and write handling.
Embedded Lua scripting.
For more information see http://httpd.apache.org/docs/2.4/new_features_2_4.html.
Oracle Linux 7 introduces the following notable authentication features:
If POSIX attributes are defined, authentication can obtain a user or group ID from Active Directory instead of using an ID generated from a Security Identifier. Clients must be running Oracle Linux 5 Update 9 and later, Oracle Linux 6 Update 3 and later, or Oracle Linux 7.
The slapi-nis package contains the
following plug-ins:
nisserver-plugin enables a directory
server to act as a NIS server.
schemacompat-plugin enables a
directory server to modify how entries in the directory
information tree (DIT) are presented to clients.
These plug-ins are designed to help transition a network from NIS to LDAP.
The GRUB2 boot loader in Oracle Linux 7 provides the following notable enhancements over the previous version of GRUB:
Support for the BIOS, EFI, and Open Firmware.
Support for GPT.
Support for additional file system types, including HFS+ and NTFS.
The installer does not permit you to configure GRUB2 in partitions as some file systems do not allow enough space for the boot loader.
The Linux Containers (LXC) feature allows you to safely and securely run multiple applications or instances of an operating system on a single host without risking them interfering with each other. Containers are lightweight and resource-friendly, which saves both rack space and power. For more information, see Linux Containers.
LXC is supported for both UEK R3 and RHCK. You can configure both 32-bit and 64-bit guest containers. However, some applications might not be supported for use with these features.
The MySQL Community 5.6 packages are available in the
Extras directory on the Oracle Linux 7 full
installation DVD image. These packages and the MySQL Community
5.5 packages will be made available on ULN and Oracle Public
Yum.
It is not possible to install MySQL and MariaDB on the same system as package conflicts exist. Installing the MySQL packages replaces any conflicting MariaDB packages.
See Chapter 3, Installation and Availability and Section 3.2, “Installing the MySQL Packages from the DVD Image”.
Oracle Linux 7 provides the following notable enhancements to support networking:
The chronyd service enables mobile
systems and virtual machines to update their system clock
after a period of suspension or disconnection from a
network. You can use the chronyc command
to manage the chronyd service. For more
information, see the chronyc(1) manual
page.
Domain Name System Security Extensions (DNSSEC) allow a DNS client to verify the authenticity of a DNS server and to check that responses to DNS queries have not been modified.
The firewalld service provides a
dynamically managed firewall that allows applications and
system services to add firewall rules. By default, the
firewalld service is enabled and the
iptables and ip6tables
services are disabled. For more information, see
https://fedoraproject.org/wiki/FirewallD.
The nmcli utility notifies the
NetworkManager about configuration changes. By default,
NetworkManager now does not monitor configuration file for
changes. However, it still responds to any changes made
using the D-Bus API. For more information, see the
nmcli(1) manual page.
OpenLMI provides an infrastructure for configuring, managing, and monitoring hardware, operating system software, and services on Linux systems, including bare-metal servers and virtual machine guests, as well as storage systems and networks. OpenLMI abstracts the complexity of system management and presents a simpler administration interface. The Open LMI agents on a managed system are accessible via the OpenLMI controller, which also provides access to client applications using C/C++, Java, Python, or the CLI. For more information, see http://www.openlmi.org.
The Red Hat Compatible Kernel (RHCK) is based on mainline Linux version 3.10 and provides the following notable features:
Compression of swap memory to reduce I/O overhead (zram).
Crash dumps can be recorded on systems with up to 3 TB of memory.
DynTick support for suspending the system tick when there is only a single runnable task.
Hardware Error Reporting Mechanism (HERM), which replaces
mcelog and EDAC.
NUMA-aware scheduling and memory allocation for improving the performance of NUMA systems.
Oracle Linux 7 introduces the following notable security features:
The SSH 2 AuthenticationMethods option
specifies one or more comma-separated lists of
authentication methods. If only one list is specified, a
user is granted access if he or she successfully completes
all of the methods in the list. If several lists are
specified, a user must complete at least one of the lists.
Each listed authentication method must be enabled in
/etc/ssh/sshd_config.
The available methods are hostbased,
keyboard-interactive,
password, and
publickey. You can use the
keyboard-interactive method to invoke
authentication mechanisms such as Pluggable Authentication
Modules (PAM). You can configure PAM modules that use
authentication methods such as GSSAPI, Kerberos, hardware
tokens, or biometric matching.
The following example configuration requires either public-key authentication followed by PAM-defined authentication or connection from a trusted host followed by public-key authentication:
AuthenticationMethods "publickey,keyboard-interactive:pam hostbased,publickey"
To overcome the inherent vulnerability of processes sharing a system key table, applications can use the GSS Proxy system service to set up a unique Kerberos context.
The selinuxuser_use_ssh_chroot variable
must be set for confined SELinux users (for example,
guest_u, staff_u, or
user_u). To ensure high security when
specifying the Open SSH ChrootDirectory
option, configure chrooted users as the confined user
guest_u.
Version 3.15.2 and later of the nss
packages support the following AES-GCM cipher suites with
TLS 1.2:
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
OCSP and CRLs no longer accept MD2, MD4, and MD5 signatures.
Oracle Linux 7 introduces the following notable features for managing storage and file systems:
Oracle Linux 7 with both UEK R3 and RHCK uses the Linux-IO
(LIO) Target to provide the block-storage SCSI target for
FCoE, iSCSI, and Mellanox InfiniBand (iSER and SRP). To
manage LIO, you can use the targetcli
shell, which accepts plug-ins that support additional fabric
types and functionality. For more information, see the
targetcli(8) manual page and
http://linux-iscsi.org/wiki/Targetcli.
The System Storage Manager command-line utility
(ssm) unifies the configuration and
management of storage and file systems by subsuming the
functionality of commands such as btrfs,
cryptsetup, dmsetup,
fsck, lv*,
mdadm, mkfs,
mount, pv*,
tune2fs, vg*, and
xfs_*. For more information, see the
ssm(8) manual page and
http://storagemanager.sourceforge.net.
Oracle Linux 7 provides the temporary file system
(tmpfs), which is configured in volatile
memory and whose contents do not persist after a system
reboot. To mount this file system on
/tmp, use the
systemctl command to enable the
tmp.mount systemd
mount point unit. The tmpfs file system
is suitable for use by non-privileged processes that need to
store small quantities of temporary data.
The snapper command allows you to manage
read-only snapshots of btrfs file systems and
thinly-provisioned LVM logical volumes. For more
information, see the snapper(8) manual
page and
http://snapper.io/documentation.html.
The following features are still under development, but are made available for testing and evaluation purposes with UEK R3.
DRBD (Distributed Replicated Block Device)
A shared-nothing, synchronously replicated block device (RAID1 over network), designed to serve as a building block for high availability (HA) clusters. It requires a cluster manager (for example, pacemaker) for automatic failover.
Transcendent memory
Transcendent Memory (tmem) provides a new approach for improving the utilization of physical memory in a virtualized environment by claiming underutilized memory in a system and making it available where it is most needed. From the perspective of an operating system, tmem is fast pseudo-RAM of indeterminate and varying size that is useful primarily when real RAM is in short supply. To learn more about this technology and its use cases, see the Transcendent Memory project page at http://oss.oracle.com/projects/tmem/.
For the RHCK, the following features are currently under technology preview:
Active Directory and LDAP sudo providers.
Block and object storage layouts for parallel NFS (pNFS).
Block device caching by LVM, which allows small, fast devices to act as caches for large, slow devices.
btrfs file system. Oracle supports btrfs with UEK R3.
Crash kernel can be configured to boot with more than a single CPU.
DIF/DIX for data integrity checking on SCSI devices.
kpatch, which is a kernel patching utility. Alternatively, you can configure Ksplice if you have an Oracle Linux Premier Support account. Ksplice is fully supported by Oracle with both RHCK and UEK R3.
LSI Syncro CS feature in the megaraid_sas
driver to support High-Availability Direct-Attached storage
(HA-DAS) adapters.
LVM API.
More than 32 PCI slots can be configured with PCI Bridge in QEMU.
OpenLMI Software Provider.
PCI Express Bus, AHCI Bus, and USB 3.0 host adapter emulation are provided for KVM guests.
SCAP Workbench and the OSCAP Anaconda add-on.
Single-Root I/O virtualization (SR-IOV) in the
qlcnic driver.
Storage array management, which includes a command-line interface and the libStorageMgmt API.
The dm-era device-mapper target records
changes made to blocks over a specified time period.
Trusted Network Connect.
virtio-blk-data-plane in Quick EMUlator
(QEMU) improves block I/O performance.
Oracle Linux maintains user-space compatibility with Red Hat Enterprise Linux, which is independent of the kernel version that underlies the operating system. Existing applications in user space will continue to run unmodified on the Unbreakable Enterprise Kernel Release 3 (UEK R3) and no re-certifications are needed for RHEL certified applications.
To minimize impact on interoperability during releases, the Oracle Linux team works closely with third-party vendors whose hardware and software have dependencies on kernel modules. The kernel ABI for UEK R3 will remain unchanged in all subsequent updates to the initial release. UEK R3 contains changes to the kernel ABI relative to UEK R2 that require recompilation of third-party kernel modules on the system. Before installing UEK R3, verify its support status with your application vendor.
The following sections describe the most notable changes in Oracle Linux 7 from Oracle Linux 6.
Parameters defined in /etc/sysconfig files
are automatically exported in Oracle Linux 7. You no longer
need to use the export command.
The host name is now defined in
/etc/hostname instead of
/etc/sysconfig/network.
Network interface names are now based on information derived from the system BIOS or alternatively from a device's firmware, system path, or MAC address. This feature ensures that interface names persist across system reboots, hardware reconfiguration, and updates to device drivers and the kernel.
If you enable the biosdevname boot option
(biosdevname=1), the biosdevname plugin to the
udev device manager assigns names to network interfaces as follows:
Ethernet interfaces on the motherboard are named
emN, where
N is the number of the
interface starting from 1.
Network interfaces on a PCI card are named
pSpP,
where S is the slot number and
P is the port number.
Virtual interfaces are named
pSpP_V,
where S is the slot number,
P is the port number, and
V is the virtual interface
number.
If biosdevname is set to 0 (the default),
systemd naming assigns the prefixes,
en, wl, and
ww to Ethernet, wireless LAN, and wireless
WAN interfaces respectively. The prefix is followed by a
suffix based on the hardware configuration, system bus
configuration, or MAC address of the device:
oN
Onboard device with index number
N.
pBsS[fF][dD]
PCI device with bus number B,
slot number S, function
number F, and device ID
D.
pBsS[fF][uP]...[cC][iI]
USB device with bus number B,
slot number S, function
number F, port number
P, configuration number
C, and interface number
I.
sS[fF][dD]
Hot-plug device with slot number
S, function number
F, and device ID
D.
xM
Device with MAC address M.
For example, an Ethernet port on the motherboard might be named eno1
or em1, depending on whether the value of
biosdevname is 0 or 1.
The kernel assigns a legacy, unpredictable network interface
name (ethN and
wlanN) only if
it cannot discover any information about the device that would
allow it to disambiguate the device from other such devices.
You can use the net.ifnames=0 boot
parameter to reinstate the legacy naming scheme.
Using the net.ifnames or
biosdevname boot parameters to change the
naming scheme can rendering existing firewall rules invalid.
Changing the naming scheme can also affect other software
that refers to network interface names.
The output of the ifconfig command has changed format. You might need to amend any programs that parse the output of this command. For future compatibility, it is recommended that you modify such programs to use the ip command instead of ifconfig.
Although legacy support for firstboot allows third-party modules to continue to function, it is recommended that you rewrite these modules to work with the installer and Initial Setup.
As initrd is now able to mount the
/usr file system at boot time, the files in
/bin, /lib,
/lib64, and /sbin have
been moved to /usr/bin,
/usr/lib, /usr/lib64,
and /usr/sbin. Symbolic links in
/ provide backward compatibility for
programs.
System-wide default localization settings such as the default
language, keyboard, and console font are now defined in
/etc/locale.conf and
/etc/vconsole.conf instead of
/etc/sysconfig/i18n.
Oracle Linux 7 supports using PVM guests with UEK R3. You cannot use PVM guests with RHCK as this functionality is not supported upstream.
Oracle recommends using HVM with PV drivers for Oracle Linux 7 guests. You should only configure a PVM guest if the host system does not support hardware virtualization. On any 64-bit system built in the last few years, an HVM guest can take advantage of hardware-assisted paging to outperform a PVM guest.
The following sections describe alternate methods for installing Oracle Linux 7 on a PVM guest:
After installing Oracle Linux 7 on a PVM guest, boot the guest with UEK R3 and configure UEK R3 as the default boot kernel. See Section 1.16.8.3, “Setting UEK R3 as the Default Boot Kernel for a PVM Guest”.
To install Oracle Linux 7 in graphical mode on an HVM guest before switching to PVM mode:
Create a VM guest with domain type HVM with PV drivers.
Add the Oracle Linux 7 DVD image to the VM guest as a CD/DVD.
Start the VM guest and install Oracle Linux 7.
After completing the installation, change the guest domain type to PVM.
To install Oracle Linux 7 on a PVM guest in text mode:
Create a VM guest with domain type PVM.
Add the Oracle Linux 7 DVD image to the VM guest as a CD/DVD.
Start the VM guest and open its serial console.
Install Oracle Linux 7 in text mode.
To configure UEK R3 as the default boot kernel on an Oracle Linux 7 PVM guest:
Display the menu entries that are defined in
/boot/grub2/grub.cfg, for example:
# grep '^menuentry' /boot/grub2/grub.cfg
menuentry 'Oracle Linux Everything, with Linux 3.10.0-123.el7.x86_64' ... {
menuentry 'Oracle Linux Everything, with Linux 3.8.13-35.2.1.el7uek.x86_64' ... {
menuentry 'Oracle Linux Everything, with Linux 0-rescue-052e316f566e4a45a3391cff21b4174b' ... {In this example, menu entries 0, 1, and 2 correspond to the RHCK, UEK R3, and the rescue kernel respectively.
Edit /etc/default/grub and change the
value defined for GRUB_DEFAULT from
saved to the menu entry number for
UEK R3, for example:
GRUB_DEFAULT=1
You must use a number to define the menu entry for the default boot kernel. You cannot use a string value.
Regenerate /boot/grub2/grub.cfg:
# grub2-mkconfig -o /boot/grub2/grub.cfg
The new logging daemon, journald, records
system messages in non-persistent journal files in memory and
in /run/log/journal.
journald forwards messages to
rsyslog, which processes and archives only
syslog messages by default. If required,
you can configure rsyslog to archive any
other messages that journald forwards,
including kernel, boot, initrd,
stdout, and stderr
messages.
The systemd daemon replaces Upstart for
managing system run levels and services. Replacing
init, systemd is the
first process that starts after the system boots, and is the
final process that is running when the system shuts down.
systemd controls the final stages of
booting and prepares the system for use.
systemd also speeds up booting by loading
services concurrently.
Table 1.1, “systemctl Command Equivalents” shows the nearest equivalent systemctl command for various system management commands used in Oracle Linux 6.
Table 1.1 systemctl Command Equivalents
Legacy Command | Nearest Equivalent systemctl Command | Description |
|---|---|---|
chkconfig --list
|
systemctl is-enabled
|
Check whether a service is enabled to start at boot
time. The |
chkconfig |
systemctl disable
| Disable a service from starting at boot time. |
chkconfig |
systemctl enable
| Enable a service to start at boot time. |
halt | systemctl halt | Halt the system. |
pm-hibernate | systemctl hibernate | Put the system into hibernation. |
pm-suspend | systemctl suspend | Suspend the system. |
pm-suspend-hybrid | systemctl hybrid-sleep | Put the system into hibernation and suspend its operation. |
poweroff | systemctl poweroff | Power off the system. |
reboot | systemctl reboot | Reboot the system. |
runlevel | systemctl list-units --type target |
Display the currently active targets, which taken as
a group constitute the nearest equivalent that
|
service |
systemctl start
| Start a service. |
service |
systemctl status
| Display the status of a service. |
service |
systemctl stop
| Stop a service. |
telinit
|
systemctl isolate
|
Change the |
As well as services
(name.service)
and targets
(name.target),
other types of unit that you can manage in
systemd include devices
(name.device),
file system mount points
(name.mount),
and sockets
(name.socket).
For example, the following command instructs the system to
mount the temporary file system (tmpfs) on
/tmp at boot time:
# systemctl enable tmp.mount
Table 1.2, “systemd Target Equivalents” shows the nearest
equivalent systemd targets to the run
levels that are used in Oracle Linux 6.
Table 1.2 systemd Target Equivalents
Run Level in Oracle Linux 6 | Nearest Equivalent systemd Targets in Oracle Linux 7 | Description |
|---|---|---|
0 |
| Shut down and power off the system. |
1 |
| Set up a rescue shell. |
2 |
| Set up a non-graphical, multi-user system. |
3 |
| Set up a non-graphical, multi-user system with networking. |
4 |
| User defined or not used. |
5 |
| Set up a multi-user system with networking and display manager. |
6 |
| Shut down and reboot the system. |
The runlevel* targets are implemented as
symbolic links.
The nearest equivalent systemd target to
the Oracle Linux 6 run levels 2, 3, and 4 is
multi-user.target.
You can use the following commands to display the current
default systemd target and to configure a
new default target:
#systemctl get-default#systemctl set-defaultname.target
If required, you can create customized versions of the targets
that are defined in
/usr/lib/systemd/system.
For more information, see the systemctl(1)
and systemd.unit(5) manual pages and
http://freedesktop.org/wiki/Software/systemd/.
systemd has the following limitations
that can affect the compatibility of legacy programs running
under Oracle Linux 7:
All service script actions time out after 5 minutes to prevent the system hanging indefinitely.
By default, systemd assigns each
system service to a dedicated cpu
control group, which prevents services from accessing
real-time scheduling. For details of workarounds, see
http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/.
If a systemd target does not have an
equivalent Oracle Linux 6 run level, legacy commands
such as runlevel return
N to indicate an unknown run level.
Services cannot inherit user context so some legacy service initialization scripts might not work correctly.
systemd can interpret and use the
headers in Linux Standard Base service scripts.
systemd does not attempt to stop
services that are not running.
systemd supports the
disable, enable,
restart, start,
status, and stop
actions for services. To support other service
functions, you must use a separate program such as a
service script.
The chkconfig command might display incorrect information about run levels and services.
The legacy service command forwards
service action requests to systemd
but /etc/init.d service scripts do
not.
Table of Contents
This chapter describes the known issues for the initial release for Oracle Linux 7.
During installation, if you select Encrypt my data on the Installation Destination screen and then perform manual partitioning, the Encrypt check box is not shown as selected on the Manual Partitioning screen. This check box refers to encryption that you can configure on a file system type that supports encryption or on an LVM logical volume that contains the file system. If you click Modify, the Encrypt check box on the Configure Volume screen is shown as selected for the volume, meaning that the encryption will be applied at the level of the underlying block device.
For LVM, selecting Encrypt my data encrypts the LVM physical volume and all the logical volumes that it contains. If you do not select Encrypt my data, you can encrypt the logical volume by selecting the Encrypt check box on the Manual Partitioning screen or encrypt the physical volume by selecting the Encrypt check box on the Configure Volume screen.
For btrfs, encryption can only be applied to the block device
that contains the file system, including its subvolumes. For
example, enabling encryption for the /home
subvolume of a btrfs root file system implicitly enables
encryption for the root file system itself. You can only select
the Encrypt check
box on the Configure Volume screen. As btrfs does not support
encryption at the file-system level, you cannot select the
Encrypt check box on
the Manual Partitioning screen for a btrfs file system.
Do not select the Encrypt check
box or a BTRFS,
LVM, or
LVM Thin Provisioning
device type for /boot. The
/boot file system must be configured on a
standard partition and should be of type ext4 or XFS.
When entering a password in the Disk Encryption Passphrase dialog, press Tab to move between the entry fields. You cannot use the mouse to select the fields.
Installation fails on a Cisco N20-B6625-1 blade server which is configured to SAN boot over a Cisco VIC FCoE HBA. There is no current workaround. (Bug ID 18481679)
Per-CPU allocation fails when the kvm_intel
module is loaded with UEK R3. Messages such as the following are
logged:
kvm_intel: Could not allocate 48 bytes percpu data PERCPU: limit reached, disable warning
There is no current workaround for UEK R3. (Bug ID 18459498)
The avahi-daemon fails to start with UEK R3
and messages such as the following are logged:
WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Unit avahi-daemon.service entered failed state.
The workaround is to comment out the
disallow-other-stacks entry in
/etc/avahi/avahi-daemon.conf as shown here:
#disallow-other-stacks=yes
(Bug ID 18459758)
On UEFI-based systems, using the grub2-set-default and grub2-config commands to change the boot order does not work. The workaround is to select the required kernel manually at boot time. (Bug ID 18508957)
If you enable the crashkernel=auto kernel
parameter for UEK R3 to simplify Kdump configuration, both
dmesg output and
/proc/cmdline show
crashkernel=.
This is the expected behavior for the implementation, where
NNNM@0M@0M implies the auto
setting. For Xen, crashkernel=auto is
supported only for Domain 0.
At boot time, systemd fails to load the
autofs4 and ipv6 modules
and errors such as the following are logged:
systemd[1]: Failed to insert module 'autofs4' systemd[1]: Failed to insert module 'ipv6'
There is no current workaround for UEK R3. (Bug ID 18470449)
The following issues might be encountered for PVM guests:
PVM guests do not initialize the frame buffer when used with the Red Hat Compatible Kernel (RHCK). Guest installation, including text-based installation, that relies on the frame buffer device being available, fails with a blank screen being displayed. This issue does not affect installations that use Kickstart, the text console, or VNC. Two alternate workarounds are described in Section 1.16.8.1, “Installing Oracle Linux 7 on an HVM Guest Before Switching to PVM Mode”Section 1.16.8.2, “Installing Oracle Linux 7 Directly on a PVM Guest”. (Bug ID 18266964)
PVM guests cannot boot under Oracle VM 3.2. (Bug IDs 18809548, 18969789, and 19056041)
It is not possible to use the UEK R3 boot ISO image to install Oracle Linux 7 on a PVM guest. (Bug IDs 18757821 and 18817699)
An Oracle Linux 7 PVM guest ignores the default boot kernel and boots the RHCK. The workaround is to configure UEK R3 as the default boot kernel. See Section 1.16.8.3, “Setting UEK R3 as the Default Boot Kernel for a PVM Guest”. (Bug ID 18896345)
You must use a number to define the menu entry for the default boot kernel. You cannot use a string value. (Bug ID 18896496)
The graphical console does not work on Oracle Linux 7 PVM guests. (Bug ID 18896390)
The following error message indicates that IPv6 NAT is not
currently supported by firewalld with UEK R3.
ERROR: ipv6 table 'nat' does not exist (or not enough permission to check)
(Bug ID 18504545)
The oracleasm script fails if SELinux is in
Enforcing mode. The suggested workaround is
to disable the SELInux policy module for Oracle ASM before
running oracleasm:
#semodule -d oracleasm#semodule -l | grep oracleasmoracleasm 1.0.0 Disabled
(Bug ID 18513404)
The systemctl command supports the
disable, enable,
restart, start,
status, and stop actions
for services such as o2cb and
oracleasm. To perform actions such as
configure, invoke the
/etc/init.d script for the service directly.
(Bug IDs 18527520 and 18528039)
The btrfs-convert command fails when invoked to convert an ext2, ext3, or ext4 file system to btrfs. This error occurs whether the system has been booted with UEK R3 or RHCK. There is currently no known workaround or fix available. (Bug ID 18534417)
The following issues may be encountered when upgrading:
The redhat-upgrade-tool-cli utility
requires that you install version 3.2.29-43.0.1 or later
of the yum package on the Oracle Linux
6 Update 5 system that you want to upgrade. If you use an
earlier version of the yum package, the
upgrade tool fails with dependency errors. (Bug ID
18648783)
The old RHCK is not removed during the upgrade. (Bug ID 18767222)
If you do not run the preupgrade assistant utility preupg, an
upgraded system hangs while rebooting with the message starting wait for
plymouth boot screen to quit. (Bug ID 18815298)
Link to Bug DB: 18815298
The redhat-upgrade-tool-cli utility does not exit if UEK R3 is not installed. (Bug ID 18900135)
The postupgrade scripts fail if a proxy is required to access Oracle Public Yum. (Bug ID 19169163)
The libcgroup package in Oracle Linux 7 does not include the
cgconfig and cgred control group services. To
restore these services on an upgraded system, install the
libcgroup-tools package. (Bug ID 19177606)
Installing the tex-fonts-hebrew package fails
unless you first install all texlive*
packages. (Bug ID 19059949)
The sosreport -o selinux -a command reports many SELinux warnings for files that do not belong to RPMs. This is the expected behavior. You can safely ignore these warnings. (Bug ID 18913115)
Attempting to create an lxc-oracle container
on a remote file system mounted using NFS v4 fails. In addition,
attempting to mount a remote file system using NFS v4 from
within an lxc-oracle container also fails.
The workaround is to use NFS v3 instead. (Bug ID 16316266)
Network teaming is not currently supported for use with UEK R3. The workaround is to use bonding instead. (Bug ID 19151770)
The daemons and features provided by the Red Hat Automatic Bug Reporting Tool (ABRT) are
not supported with Oracle Linux. ABRT packages and associated files, such as
libreport, are included in the distribution to satisfy package
dependencies, but the features within these packages are not supported. For technical
assistance, contact Oracle Support via the My Oracle Support portal or by telephone.
The following issues might be encountered with InfiniBand devices:
You might see the following warning messages if you use the ibportstate disable command to disable a switch port:
ibwarn: [2696] _do_madrpc: recv failed: Connection timed out ibwarn: [2696] mad_rpc: _do_madrpc failed; dport (Lid 38) ibportstate: iberror: failed: smp set portinfo failed
You can safely ignore these warnings. (Bug ID 16248314)
To configure Internet Protocol over InfiniBand (IPoIB):
Edit the
/etc/sysconfig/network-scripts/ifcfg-ib
configuration file, where NN
is the number of the interface.
Stop the NetworkManager service:
# systemctl stop NetworkManagerStart the RDMA service:
# systemctl stop rdmaBring up the interface:
# ifup ibN(Bug ID 19150870)
The IPoIB driver supports the use of either connected mode
or datagram mode with an interface, where datagram mode is
the default mode. Changing the mode of an InfiniBand
interface by echoing either connected or
datagram to
/sys/class/net/ib
is not supported. It is also not possible to change the mode
of an InfiniBand interface while it is enabled.
N/mode
To change the IPoIB mode of an InfiniBand interface:
Edit the
/etc/sysconfig/network-scripts/ifcfg-ib
configuration file, where NN is the number of the
interface:
To configure connected mode, specify
CONNECTED_MODE=yes in the file.
To configure datagram mode, either specify
CONNECTED_MODE=no in the file or do not specify this
setting at all (datagram mode is enabled by default).
Before saving your changes, make sure that you have not specified more than
one setting for CONNECTED_MODE in the file.
To enable the specified mode on the interface, use the following commands to take down the interface and bring it back up:
#ifdown ib#Nifup ibN
(Bug ID 17479833)
When the rds_ib_srq parameter for the
rds_rdma module is enabled and the module
is in use (for example, when running the
rds-stress tool), restarting the
rdma service (which reloads the
rds_rdma module) generates error messages
visible in dmesg or
/var/log/messages. (Bug ID 19010606)
Table of Contents
You can download a full Oracle Linux 7 installation media image from the Oracle Software Delivery Cloud at http://edelivery.oracle.com/linux. You can also obtain Oracle Linux 7 packages from the Unbreakable Linux Network (ULN) and the Oracle Public Yum server.
The following table lists some of the channels and repositories that will be made available on ULN and Oracle Public Yum for Oracle Linux 7.
ULN Channel | Public Yum Repository | Description |
|---|---|---|
|
| Latest packages for Oracle Linux 7. |
|
| Base packages for the initial release (Update 0) of Oracle Linux 7. |
| Patches for the initial-release packages of Oracle Linux 7. | |
|
| GPL-licensed packages for Oracle Linux 7 that have not been sourced from upstream. |
| DTrace user-space packages for Oracle Linux 7. | |
| Ksplice packages for Oracle Linux 7. | |
|
| MySQL Community Edition 5.5 packages for Oracle Linux 7. |
|
| MySQL Community Edition 5.6 packages for Oracle Linux 7. |
|
|
Latest optional packages (including most
|
| Oracle software packages for Oracle Linux 7. | |
|
| Latest Unbreakable Enterprise Kernel Release 3 (UEK R3) packages for Oracle Linux 7. |
| OpenFabrics Enterprise Distribution (OFED) 2.0 packages for UEK R3 on Oracle Linux 7. See Section 3.3, “Installing OFED Packages from the ol7_x86_64_UEKR3_OFED20 Channel”. | |
| Oracle VM VirtualBox packages for Oracle Linux 7. |
Some ULN channels will not be made available until after the initial release.
Oracle Public Yum does not provide equivalent repositories for some channels that are available on ULN. These channels provide non-open source packages.
The kernel source code is available after the initial release via a public git source code repository at https://oss.oracle.com/git/?p=linux-uek3-3.8.git.
UEK R3 is the default boot kernel for fresh installations of Oracle Linux 7.
For systems that are running UEK R3 and are subscribed to the
ol7_x86_64_UEKR3 channel on ULN, or the
ol7_x86_64_UEKR3 repository on Oracle Public
Yum, you upgrade to the latest UEK release as follows:
Upgrade all packages on the system, including kernel packages.
# yum updateBy default, the boot manager automatically enables the most recent kernel version so you do not need to change your GRUB configuration.
Reboot the system.
# systemctl rebootIt is possible to upgrade an Oracle Linux 6 Update 5 system to Oracle Linux 7 under the following conditions:
The system meets the minimum installation requirements for Oracle Linux 7. See Section 1.1, “System Requirements”.
UEK R3 has been installed on the system to be upgraded and is the default boot kernel. Upgrading from UEK R2 is not supported.
No Oracle product stack is present on the system.
The following table shows the changes that are applied to any kernels that are configured on the system being upgraded.
|
Kernel on Original System |
Kernel on Upgraded System |
|---|---|
|
RHCK (2.6.32) |
RHCK (3.10.0) for Oracle Linux 7 is installed. RHCK (2.6.32) is removed. |
|
UEK R3 (3.8.13) |
UEK R3 (3.8.13) for Oracle Linux 7 is installed and made the default boot kernel. The previous version of UEK R3 is removed. |
To perform the upgrade:
If the system to be upgraded contains valuable data, make a backup or snapshot of the system so that you can recover its previous state should the upgrade fail.
Obtain the latest versions of the following packages from ULN in the
ol6_x86_64_addons channel, or from Oracle Public Yum in the
ol6_addons repository:
openscap
preupgrade-assistant-ui
preupgrade-assistant
preupgrade-assistant-contents
redhat-upgrade-tool
Install the packages by using the yum localinstall command:
# yum localinstall openscap preupgrade-assistant* redhat-upgrade-toolRun the preupg command to perform an upgrade assessment:
# preupg
preupg outputs the results of the assessment as a
tar.gz archive
(preupg_results-)
under timestamp.tar.gz/root/preupg-results. Make a copy of this file for future
reference.
Examine the contents of the assessment results file (result.html)
in the archive. If the file reports any needs_action or
needs_inspection issues, read the remediation instructions for
these issues and perform any required actions before proceeding with the upgrade. You
might also need to perform some actions after performing the upgrade.
Run the redhat-upgrade-tool-cli command to perform the upgrade.
For example, to upgrade from an Oracle 7 installation repository at a URL:
# redhat-upgrade-tool-cli --network 7.0 --instrepo=OL7_repo_URL --debuglog=/tmp/upgrade.log
For more information, use the --help option to redhat-upgrade-tool-cli.
Reboot the system to start the upgrade process.
The system performs the package upgrade before booting UEK R3 with Oracle Linux 7.
For more information, see the Oracle Linux 7 Installation Guide.
If the system is registered with ULN and has access to ULN channels or it has access to Oracle
Public Yum, the preferred method is to install the MySQL packages from the
ol7_x86_64_MySQL55 or ol7_x86_64_MySQL56 channels
on ULN or from the ol7_MySQL55 or ol7_MySQL56
repositories on Oracle Public Yum.
To install the MySQL Community Edition 5.6 packages from the Extras
directory on the Oracle Linux 7 full installation DVD image:
Mount the DVD image on the system.
For example, download the DVD image file to the system, create a mount point, and mount the image on this mount point:
#mkdir -p /var/OSimage/OL7u0_x86_64#mount -o loop,ro OracleLinux-R7-U0-Server-x86_64-dvd.iso /var/OSimage/OL7u0_x86_64
Alternatively, mount the DVD image from a physical or virtual DVD:
#mkdir -p /var/OSimage/OL7u0_x86_64#mount -o ro /dev/cdrom /var/OSimage/OL7u0_x86_64
Create a local directory for the MySQL packages and copy the packages to this directory:
#mkdir -p /var/MySQL56_OL7#cp -a -T /var/OSimage/OL7u0_x86_64/Extras /var/MySQL56_OL7
If the createrepo utility does not exist on the system, use the following command to install it:
# yum install createrepoCreate a yum repository for the MySQL packages:
# createrepo /var/MySQL56_OL7
Rename the existing Oracle Linux repository file, usually
/etc/yum.repos.d/public-yum-ol7.repo, so
that the file name does not have the
.repo extension, for example:
# mv /etc/yum.repos.d/public-yum-ol7.repo /etc/yum.repos.d/public-yum-ol7.repo.orig
Create a new repository file,
/etc/yum.repos.d/OL7u0.repo, which
contains the following entries:
[OL7_u0] name=Oracle Linux 7u0 x86_64 baseurl=file:///var/OSimage/OL7u0_x86_64 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle gpgcheck=1 enabled=1 [OL7_MySQL56] name=MySQL 5.6 for Oracle Linux 7u0 x86_64 baseurl=file:///var/MySQL56_OL7 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle gpgcheck=1 enabled=1
Use yum to install the MySQL packages, for example:
# yum install mysql-community-benchInstalling the MySQL packages replaces any conflicting MariaDB packages
(mariadb*).
To restore the original repository configuration after installing the MySQL packages:
Restore the original Oracle Linux repository file that you renamed in step 6, for example:
# mv /etc/yum.repos.d/public-yum-ol7.repo.orig /etc/yum.repos.d/public-yum-ol7.repo
Rename the new repository file that you created in step
7 so that the file name does not have the
.repo extension, for example:
# mv /etc/yum.repos.d/OL7u0.repo /etc/yum.repos.d/OL7u0.repo.origAlternatively, remove the file if you do not intend to install additional MySQL packages in the future:
# rm /etc/yum.repos.d/OL7u0.repoUnmount the DVD image:
# umount /var/OSimage/OL7u0_x86_64To save disk space, you can remove the directory where you set up the local repository for the MySQL packages:
# rm -rf /var/MySQL56_OL7 If you subscribe a system to the ol7_x86_64_UEKR3_OFED20 channel on
ULN, remove any existing OFED packages before installing any new OFED packages from this
channel. The OFED packages are not upgradable if you installed them from the Oracle Linux 7
full installation DVD image, the ol7_x86_64_latest channel on ULN, or the
ol7_latest repository on Oracle Public Yum, or if they are present on
an Oracle Linux 6 Update 5 system that you have upgraded to Oracle Linux 7.
Use the rpm command to remove the old OFED packages, for example:
# rpm -e infiniband-diags \
libibcm \
libibcm-devel \
libibmad \
libibmad-devel \
libibumad \
libibumad-devel \
libibverbs \
libibverbs-devel \
libmlx4 \
librdmacm \
librdmacm-devel \
opensm-devel \
opensm-libs \
ibacm-devel \
ibutils \
ibutils-libsYou can then use yum to install the new packages, for example:
# yum install ibutilsIf you see a package conflict, use rpm to remove the old package before trying to install the new package again.
Table of Contents
The following sections list the changes to source packages from the upstream release.
The following packages from the upstream release have been removed:
libehca
libica
libreport-plugin-rhtsupport
libreport-rhel
libreport-rhel-anaconda-bugzilla
librtas
libservicelog
libvpd
libzfcphbaapi
lsvpd
openssl-ibmca
powerpc-utils
powerpc-utils-python
ppc64-diag
ppc64-utils
publican-redhat
python-rhsm
Red_Hat_Enterprise_Linux-Release_Notes-7-as-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-bn-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-de-DE
Red_Hat_Enterprise_Linux-Release_Notes-7-en-US
Red_Hat_Enterprise_Linux-Release_Notes-7-es-ES
Red_Hat_Enterprise_Linux-Release_Notes-7-fr-FR
Red_Hat_Enterprise_Linux-Release_Notes-7-gu-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-hi-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-it-IT
Red_Hat_Enterprise_Linux-Release_Notes-7-ja-JP
Red_Hat_Enterprise_Linux-Release_Notes-7-kn-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-ko-KR
Red_Hat_Enterprise_Linux-Release_Notes-7-ml-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-mr-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-or-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-pa-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-pt-BR
Red_Hat_Enterprise_Linux-Release_Notes-7-ru-RU
Red_Hat_Enterprise_Linux-Release_Notes-7-ta-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-te-IN
Red_Hat_Enterprise_Linux-Release_Notes-7-zh-CN
Red_Hat_Enterprise_Linux-Release_Notes-7-zh-TW
redhat-access-gui
redhat-logos
redhat-support-lib-python
redhat-support-tool
s390utils
servicelog
subscription-manager
subscription-manager-migration-data
virt-who
yaboot
The following packages from the upstream release have been modified:
abrt
abrt-java-connector
anaconda
autofs
basesystem
coreutils
dbus
dhcp
firefox
fuse
gdm
glusterfs
grub2
grubby
gstreamer
httpd
ipa
irqbalance
iscsi-initiator-utils
java-1.7.0-openjdk
kabi-yum-plugins
kde-settings
libreoffice
libreport
libreswan
libxml2
libxslt
lorax
mkbootdisk
nss
os-prober
PackageKit
pcs
plymouth
policycoreutils
python-blivet
redhat-bookmarks
redhat-indexhtml
redhat-lsb
redhat-release-server
redhat-rpm-config
redhat-upgrade-dracut
redhat-upgrade-tool
rhn-client-tools (updated to support
ULN)
rhnsd
rpmdevtools
rsyslog
selinux-policy
setroubleshoot
setroubleshoot-plugins
sos
system-config-date
system-config-kickstart
systemtap
tog-pegasus
wireshark
xfsprogs
xsane
xulrunner
yum
yum-rhn-plugin
yum-utils
The following optional packages have been modified:
publican
sanlock
jetty-artifact-remote-resources
jetty-parent
jetty-toolchain
The following modules have been removed from UEK R3 for Oracle Linux 7 compared with UEK R3 for Oracle Linux 6 Update 5:
3c574_cs
3c589_cs
3c59x
3w-xxxx
8390
acenic
aic7xxx
aic94xx
amd8111e
at76c50x-usb
atmel
atmel_cs
atmel_pci
axnet_cs
b43
b43legacy
can
can-bcm
can-dev
can-raw
cassini
c_can
c_can_platform
cciss
cdc-phonet
cxgb
dl2k
e100
ems_pci
ems_usb
esd_usb2
fealnx
fmvj18x_cs
forcedeth
ips
ipw2100
ipw2200
ixgb
kvaser_pci
libertas
libertas_cs
libertas_sdio
libertas_tf
libertas_tf_usb
libipw
mac80211_hwsim
megaraid_mbox
mptfc
mptlan
myri10ge
natsemi
ne2k-pci
niu
nmclan_cs
ns83820
p54common
p54pci
p54usb
pch_can
pcnet32
pcnet_cs
plx_pci
r6040
rt2400pci
rt2500pci
rt2500usb
rtl8180
s2io
sc92031
sis190
sis900
sja1000
sja1000_platform
slcan
smc91c92_cs
softing
softing_cs
starfire
sundance
sungem
sungem_phy
sunhme
sym53c8xx
tehuti
tlan
typhoon
usb8xxx
vcan
via-rhine
via-velocity
vxge
xirc2ps_cs
zd1211rw
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices