4 Known Issues
This chapter describes known issues for Oracle Linux 7.7 (aarch64).
Note that additional issues that are specific to the kernel that you are using might also be present. If you are using the default UEK R5 kernel, see Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 5 Update 2 (4.14.35-1902). If you are using an alternate UEK release or update, refer to the release notes for the appropriate kernel version in Unbreakable Enterprise Kernel documentation.
Support Limited to Text-Mode Environments and Server Software
Oracle Linux 7.7 (aarch64) is engineered and tested for server-related usage only. Although packages for desktop and productivity features are built and provided, testing of these packages is limited and support for graphical mode packages is not provided in this update. You can install any of these packages on your platform, but some of these applications might not work or could have issues that are not documented here.
Oracle does not provide support for these packages and any assistance is community-based. If you choose to run a desktop environment or any desktop applications, direct your questions to the Oracle Linux for Arm community forum at https://community.oracle.com/community/technology_network_community/server_%26_storage_systems/linux/oracle-linux-for-arm.
Installation and Upgrade Issues
The following issues might be encountered during an Oracle Linux 7.7 (aarch64) installation.
Alternate installation options
When performing a text-based installation, the installer detects the video controller and offers a graphical installation on the system video console by default. The boot menu may not offer options to perform text-based or VNC-based installation.
To perform a text-based installation, you must specify the
inst.text
option on the boot command line.
If you intend to perform a remote graphical installation over
VNC, you must use the inst.vnc
option, as
well as specify boot options to configure the network.
Typically ip=dhcp
is used for this purpose.
For more information about boot options, see Oracle Linux 7: Installation Guide.
(Bug ID 27581120)
Graphical installer allows users to edit kickstart settings
When performing a graphical installation, where some installation options are already set by using a kickstart configuration file, it is still possible to modify these settings by clicking the various fields during the installation and editing the predefined content. These types of edits during the installation process requires that you intentionally attempt to modify the setting, effectively enabling an interactive installation, where options that are set in the kickstart configuration are not secured by any policy.
Note that this type of change is not possible when performing a text-based installation. During a text-based installation, you can only modify fields that have not already been predefined in the kickstart configuration file.
(Bug ID 28642357)
Installing the oracle-armtoolset-8 package sometimes fails
Running the yum install oracle-armtoolset-8 command sometimes fails to install the package. This failure occurs at the following stage of the installation:
Installing : oracle-armtoolset-8-runtime-8.0-1.el7_6.aarch64 16/69 Error unpacking rpm package oracle-armtoolset-8-runtime-8.0-1.el7_6.aarch64 error: unpacking of archive failed on file /opt/oracle/oracle-armtoolset-8/root/lib64: cpio: rename Installing : oracle-armtoolset-8-libgo-8.2.0-6.el7_6.aarch64 17/69 error: oracle-armtoolset-8-runtime-8.0-1.el7_6.aarch64: install failed Installing : oracle-armtoolset-8-libasan-8.2.0-6.el7_6.aarch64 18/69
Subsequent attempts to install the individual package also fail:
Failed: oracle-armtoolset-8-runtime.aarch64 0:8.0-1.el7_6
If you encounter this issue, run the following commands to
remove and then reinstall the
oracle-armtoolset-8
package:
sudo yum remove 'oracle-armtoolset-8*' sudo yum remove policycoreutils-python sudo rm -Rf /opt/oracle/oracle-armtoolset-8/ sudo yum install policycoreutils-python sudo yum install 'oracle-armtoolset-8*'
(Bug ID 29672241)
Kernel panic for QLogic cnic module on ThunderX2 during installation
The QLogic cnic
driver module is
unsupported on 64-bit Arm platforms. The Cavium ThunderX2
servers include hardware that can cause the
cnic
driver module to load, thus triggering
a kernel panic.
To work around this issue, black list the
cnic
module at boot by using the
module_blacklist=cnic
boot option in the
kernel command line for the installer. To prevent the module
from installing or loading in the future, create the file
/etc/modprobe.d/cnic.conf
file and add the
following lines:
blacklist cnic install cnic /bin/true
(Bug IDs 27011806, 28109733)
Error with PXE-based installation on UEFI virtual machine
An error appears when performing an installation on a
UEFI-based virtual machine by using a PXE boot, where there is
no ramfb
device present. Typically, the
error appears as follows:
Error: Image at 0023F1EB000 start failed: Not Found
This error message can be safely ignored, as it does not prevent the installation and is reported as debugging output. Note also that the error does not appear in earlier versions of the package, where support for the QemuRamfbDxe driver was not present.
(Bug ID 28868674)
Upgrade fails if open files limit is too low and rpm-plugin-systemd-inhibit is installed
Upgrades from Oracle Linux 7.6 (aarch64) to Oracle Linux 7.7 (aarch64) can fail if the log-in
session open files limit is set too low and the system that is
being upgraded includes multiple packages from many channels
or repositories. This issue can be triggered if the
rpm-plugin-systemd-inhibit
package is
installed and the session is configured for a maximum open
file limit that is lower than 4096. The issue typically
results in yum failing to update and produces error messages
similar to the following:
Verifying : glib2-static-2.56.1-1.el7.i686 glib2-static-2.56.1-1.el7.i686 was supposed to be installed but is not!
To resolve this issue, set the open file limit to 4096 before running the yum update command:
sudo ulimit -n 4096 sudo yum update -y
(Bug ID 28720235)
Automatic Bug Reporting Tool
The automated reporting 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 and can be used to generate
local bug reports but the features to automatically upload these
reports are not supported. For technical assistance, contact
Oracle Support by using the My Oracle Support portal or by
telephone.
btrfs-convert operation results in a file system that cannot be mounted
The btrfs-convert tool can be used to convert
an ext4
file system to
btrfs
. However, if the tool attempts to
convert a file system that has not been created with a sector
block size that matches the system default page size (which is
set to 64 KB for the aarch64 platform) the resulting file system
cannot be mounted. This issue can occur if the original
ext4
file system is not created by using the
-b 65536
option to specify a 64 KB block
size.
(Bug ID 28200561)
Manual execution of shim first-stage boot loader may fail in the UEFI shell
Manually loading of shim binaries from the UEFI shell may fail in some scenarios. The following cases are known to fail:
-
FS0:\EFI\redhat\shimaa64.efi
-
FS0:\EFI\redhat\> shimaa64.efi
FS0:\> \EFI\redhat\shimaa64.efi
is known to
work correctly.
A standard installation is unaffected by this bug. The problem is limited to the manual execution of shim in the UEFI shell.
(Bug ID 27962691)
Kdump tools fail to create a vmcore-dmesg.txt on systems with many CPUs
On systems with multiple CPUs, the crash dump tools that are
included with Kdump, fail to create a
vmcore-dmesg.txt
file, which is created with
the vmcore
file. This issue may result in the
following segmentation fault:
... kdump: saving to /sysroot//var/crash/127.0.0.1-2018-05-22-12:34:45/ kdump: saving vmcore-dmesg.txt /lib/kdump-lib-initramfs.sh: line 118: 459 Segmentation fault $_dmesg_collector /proc/vmcore > ${_path}/vmcore-dmesg-incomplete.txt kdump: saving vmcore-dmesg.txt failed kdump: saving vmcore Copying data : [100.0 %] \ eta: 0s kdump: saving vmcore complete
This issue is the result of a log buffer that is dynamically
allocated by the kernel. vmcore-dmesg
does
not know how to access memory that allocated in this way. The
issue is typically triggered on systems with 64 or more CPUs,
but has also been observed on a 32-core Ampere X-Gene 3 system.
The dmesg output can be retrieved manually by the running crash command against vmcore and then using the dmesg command when in the crash shell.
(Bug ID 28064675, 28670960)
Snapshots of KVM guests using UEFI fail and are unsupported
In this release, you cannot create snapshots of KVM guests if
they use UEFI. In older versions of QEMU and
libvirt
, the tools might allow you to create
the snapshot without an error or warning, but the snapshot could
be corrupted. More recent versions of these tools prevent
snapshot creation by producing an error similar to the
following:
sudo snapshot-create-as OL7-seboot
error: Operation not supported: internal snapshots of a VM with pflash based firmware are not supported
(Bug ID 26826800)
Uninstalling libpcap package can result in removal of a large number of libvirt packages
The libpcap
package is updated to enable
functionality for upcoming technologies. If you install this
package and then attempt to uninstall it, a large number of
libvirt
packages might also be uninstalled
due to dependency relationships. The libvirt
package has a dependency on the
libvirt-daemon-driver-nwfiler
package, and
this package has a dependency on libpcap
.
Removing libpcap
removes the entire
libvirt
family of packages.
(Bug ID 28582266)
Virtual machine with copied disk fails to boot
Attempting to start a virtual machine that has been created to use a copied virtual machine hard disk can fail with messages similar to the following:
Section 0 has negative size Failed to load image: Unsupported start_image() returned Unsupported Error: Image at 002384AD000 start failed: Unsupported Unloading driver at 0x002384AD000
After failing, the boot loader drops back into the UEFI interactive shell.
This issue is caused by a problem with the default EFI boot option that is used by the aarch64 virtual machine firmware when it attempts to boot the disk.
To work around the issue, when the virtual machine drops to the UEFI shell after it fails to boot, you can type the following information to manually load the appropriate shim binary:
Shell> sudo FS0:\EFI\BOOT\fbaa64.efi
Note that typing this information is a one-time requirement and future reboots of the same virtual machine do not require manual intervention.
(Bug ID 27972230)
grubby fatal error during kernel upgrade when /boot is on a btrfs subvolume
If /boot
is hosted on a
btrfs
subvolume, GRUB 2 is unable to
correctly process the initramfs
and
vmlinuz
pathnames. This problem occurs when
you update or install a new kernel and grubby
attempts to update the GRUB 2 configuration. In the case where
you are running a fresh installation of Oracle Linux 7.7 (aarch64), and you
upgrade the UEK kernel, the following error is displayed:
grubby fatal error: unable to find a suitable template
When the system is rebooted after the kernel update, the system boots to the old kernel.
The workaround for this problem is to use
grub2-mkconfig to regenerate the
/etc/grub2/grub.cfg
file immediately after
the kernel has been installed or upgraded, for example:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Obtain a listing of the kernel menu entries in the generated configuration as follows:
grep -P "submenu|^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2
From the listing, select the kernel entry that you want to run as the default kernel and set this entry as the default using the following command, substituting menu entry title with the title of the kernel entry that you identified in the listing:
sudo grub2-set-default "menu entry title"
You can use the grub2-editenv list command to
check that the saved_entry
has been updated
with the selected kernel menu title.
Reboot and use uname -a to check that the correct kernel is now running.
(Bug ID 22750169)
Hebrew LaTeX fonts
Installing the tex-fonts-hebrew
package fails
unless you first install all of the texlive*
packages.
Unable to create Oracle Linux 7 LXC containers on NFS
The creation of Oracle Linux 7 containers fails when the
root
file system
(/container
) is hosted on an NFS share. This
problem occurs because the iputils
package in
Oracle Linux 7 releases, (Updates 4 and 5) is built to use the Linux file
extended attributes [xattr(7)] security
capabilities(7)
. Because the NFS protocol does not
support these file capabilities, the iputils
package might not be installed into an NFS files system. For
example, when attempting to create an Oracle Linux 7.4 container, the
installation fails while installing the
iputils
package, producing the following
error:
Error unpacking rpm package iputils-20121221-7.el7.x86_64 error: unpacking of archive failed on file /usr/bin/ping: cpio: cap_set_file error: iputils-20121221-7.el7.x86_64: install failed
Similar issues are seen when attempting to install the
initscripts
and systemd
packages while creating an Oracle Linux 7.3 container.
This issue occurs on both NFSv3 and NFSv4.
Oracle Linux 6 containers are not affected. LXC is available as a technology preview in this update. Note that some functionality may not work correctly.
(Bug ID 25024258)
Segmentation fault when running bluedevil-wizard
The bluedevil-wizard, which is available in
the bluedevil
package, is unable to connect
or locate Bluetooth devices and fails with a segmentation fault
when it is run.
(Bug ID 27101618)
dsktune command fails with an unsupported error message
The dsktune command, which is included with
the 389 Directory Server base package
(389-ds-base
) fails with the following error
message notifying you that the system does not have support for
cx16
, which is a feature commonly available
on x86-64
platforms:
ERROR: This system does not support CMPXCHG16B instruction (cpuflag cx16). nsslapd-enable-nunc-stans must be set to "off" on this system. In a future release of Directory Server this platform will NOT be supported. ERROR : The above errors MUST be corrected before proceeding.
The dsktune command checks that a system meets requirements and can provide helpful information pertaining to onfiguration, but it is not required to run the 389 Directory Server.
(Bug ID 26861135)
Unable to customize guest name during installation with Virtual Machine Manager
During an installation with virt-manager
, if
you select a customized configuration and then edit the Name
field to customize the virtual machine (VM) name, an error
similar to the following occurs when you attempt to apply the
changes:
Error apply changes: 'NoneType' object has no attribute 'rfind' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/details.py", line 1887, in config_apply ret = self.config_overview_apply() File "/usr/share/virt-manager/virtManager/details.py", line 1979, in config_overview_apply self.vm.rename_domain(self.widget("overview-name").get_text()) File "/usr/share/virt-manager/virtManager/domain.py", line 596, in rename_domain new_nvram, old_nvram = self._copy_nvram_file(new_name) File "/usr/share/virt-manager/virtManager/domain.py", line 571, in _copy_nvram_file nvram_dir = os.path.dirname(old_nvram.path) File "/usr/lib64/python2.7/posixpath.py", line 129, in dirname i = p.rfind('/') + 1 AttributeError: 'NoneType' object has no attribute 'rfind'
This issue is only encountered when attempting to customize the Name field. If you apply any other customizations prior to the installation, such as changes to Title or Description, the installation proceeds as expected. Note that you can edit the Name field after the installation completes, if desired.
(Bug ID 29954660)