Visit Azul.com Support

Azul Zulu Prime System Tools Issues Known in Previous Releases

Looking for Zing? The Azul Zing Virtual Machine is now Azul Zulu Prime Builds of OpenJDK and part of Azul Platform Prime. Learn more.

The following table lists known issues prior to the release of Azul Zulu Prime System Tools (ZST) 5.22.9.

Release Known Description

5.22.9

ZST Zing Memory fails to start on machines with UEFI Secure Boot enabled.

Workaround:

Disable UEFI Secure Boot.

5.22.8

Ubuntu 20.04 and Linux kernels 5.3.0 (and newer) in general, as a security feature, do pre-zeroing of all newly allocated pages. This leads to performance regression in Zing Memory reservation speed, which may result in failure to configure Zing Memory on large systems.

Workaround:

Update grub with init_on_alloc=0, reboot the system, and configure zing-memory.

5.22.6

ZST DKMS build fails on 5.4.x kernels with the following error message: coderecipe for target 'zm_adapter.o' failed.

Workaround:

Please see linux 5.4-rc4 Unable to build simple kernel module.

5.22.2

kzmd process prevents from restarting zing-memory or uninstalling ZST.

Workaround:

Before uninstalling ZST, run rmmod zing_mm.ko.

5.22.1

If the enhanced memory defragmentation is enabled on kernels older than 2.6.32-431, the system can crash due to RHEL/CentOS 6.4 bug 6660. See here for details.

5.22.1

CPU soft lockup on RHEL 7.x systems.

Workaround:

Increase the watchdog_thresh value echo 60 > /proc/sys/kernel/watchdog_thresh.

5.22.1

zing-ps -V does not display the correct ZST version after upgrades.

5.22.1

Installer prompts to configure zing-memory on upgrades.

5.22.0

Uninstalling ZST fails on multiple debian based hosts.

Workaround:

Before upgrading to ZST 5.22.0, comment out the /bin/systemctl disable zing-memory > /dev/null line in the /var/lib/dpkg/info/zing-zst.prerm script.

5.22.0

Upgrading from ZST 5.21.x to ZST 5.22.0 on RHEL7 displays the following message:

rpm -Uvh zing-zst-8b.3.10.0-5.22.0.0.5.el7.x86_64.rpm

Preparing…​ [100%]

Updating / installing…​

1:zing-zst-8b.3.10.0-5.22.0.0.5.el7 [ 50%]

You must configure Zing Memory. Running 'system-config-zing-memory' now is recommended.

Cleaning up / removing…​

2:zing-zst-8a.3.10.0-5.21.4.0.2.el7warning: file /usr/lib/zing/include/os/types.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/shared_user_data.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/sched.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/process_token.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/process_info.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/posix_redefines.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/pi.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/pagesize.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/memstats.hpp: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/memory.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/memctl.h: remove failed: No such file or directory

warning: file /usr/lib/zing/include/os/errors.h: remove failed: No such file or directory

[100%]

Workaround:

Ignore the message.

5.21.4

Support for Amazon Linux 2 is disabled in ZST 5.21.4.

5.21.2

Azul Platform Prime cores are not dumped when zing-core-pattern is enabled on Ubuntu 18.04.

5.20.4

Failing to uninstall ZST on a privileged container.

Workaround:

If a user needs to upgrade the ZST on a CoreOS Host the following steps are advised:

  1. Manually stop zing-memory from within the container.

  2. Exit from the container.

  3. Start a new privilege container.

  4. Install and configure ZST by following the installation instructions.

5.20.3

Cores generated with zing-core pattern enabled are not encrypted with openssl 1.1.

5.12.0

Uninstalling ZST on RHEL 6.8 displays the following warning messages:

Warning: erase unlink of /lib/modules/zing-driver/extra/zm_linux_<kernel_ version>.o failed: No such file or directory

These messages can be ignored.

5.7.18

When upgrading from ZST 5.7.17 to ZST 5.7.18 on Ubuntu systems, these errors can be ignored:

/etc/init.d/zing-agent: line 57: [: too many arguments

/etc/init.d/zing-certd: line 44: [: too many arguments

/etc/init.d/zing-httpd: line 58: [: too many arguments

5.7.17

Upgrading ZST from 5.7.17 to 5.7.18 on Ubuntu displays warning messages. Ignore the following messages:

/etc/init.d/zing-agent: line 57: [: too many arguments

/etc/init.d/zing-certd: line 44: [: too many arguments

/etc/init.d/zing-httpd: line 58: [: too many arguments

5.7.15

Upgrading ZST to 5.7.15 on RHEL/CentOS 7.x displays warning messages. Ignore these messages

warning: file /usr/lib/zing/libc_hooks2.so.1.0.0: remove failed: No such file or directory

5.7.15

Azul Platform Prime 15.05.0.0 will not run with ZST 5.7.15 without a configuration change. Contact Azul Systems Support for assistance to use Azul Platform Prime 15.05.0.0 with ZST 5.7.15.

5.7.11

Attempting to install the ZST package for Ubuntu 12.04 on an Ubuntu 10.04 system will fail and leave the system unable to open a new ssh session. To remedy the issue, uninstall the ZST package form the existing shell session.

5.7.6

Azul Platform Prime processes still running after uninstall when both relocated binaries and regular binaries are installed. Issue may arise under deployment control systems like EFS.

5.7.6

Cannot renew license through the OEM UI.

5.7.6

Can bundle Azul Platform Prime cores with non matching executable.