IBM Singapore Supercomputing Virtual Forum 30 June 2020


In the past few months, technology has been put on a test like never before. On one hand healthcare research professionals have be grappling with the onset of a pandemic, trying to find answers in data and numbers. On the other hand, corporates are struggling to make sure that continuity is maintained in order to minimize long term economic impact. In some form or the other, both segments are embracing technology for a better future. Join us for this virtual summit where we bring in the experts from the domain of HPC, AI and Quantum to explore how the paradigm has shifted from what we ‘want’ to what we ‘essentially need’ from Tech for Good.

For more information, do take a look at


Trying to allocate 1005 pages for VMLINUZ error when booting with RHEL or CentOS 6.5 disks


I was booting the RHEL 6.5 or CentOS 6.5 on a IBM PureFlex System and I have this error. This occurs when When installing Red Hat Enterprise Linux 6 from DVD media the installation will default to native Extensible Firmware Interface (EFI) mode boot. I do not have

According to IBM Website,

The workaround is simply to install the operating system in the traditional legacy mode, since there is generally no reason to install in other than Legacy mode. The workaround is only necessary if the media you are booting defaults to EFI mode (DVD or EFI Preboot eXecution Environment (PXE)) otherwise a legacy installation (e.g. – traditional PXE) is the default and is unaffected by this issue.

To force a legacy installation of the operating system from the EFI bootable DVD media the user should:

Press F12 key when the IBM splash screen is shown during system boot.
Select Legacy Only option and press Enter.
The operating system will boot and install in traditional legacy boot mode.

And the issue was resolved.


  1. Red Hat Enterprise Linux 6 (RHEL6) native Extensible Firmware Interface (EFI) install is not supported with greater than 512 GB memory – IBM System x and BladeCenter
  2. Bug 691860 – UEFI version of ISO fails to boot when >4gig (since f14)

IBM Community Compilers for Power

Compiler options:

– GNU Compiler Collection (GCC) for Linux on Power:

– IBM Advance Toolchain for Linux on Power:

– IBM XL C/C++ for Linux Community Edition:

– IBM XL Fortran for Linux Community Edition:


– IBM ESSL Community Edition:

AI platform:

– IBM WML Community Edition:


– It can be found at MPI IBM WML Community Conda Channel. It is found at spectrum-mpi for linux-ppc64le.


IBM and Quantum Computing

News from IBM on Quantum Computing


Quiskit – the “Quantum Information Science Kit” SDK is an open source platform that allows developers and coders familiar with Python and Jupyter Notebooks to program our quantum computers

  • QISKit AQUA builds and runs algorithms, and contains algorithms and domain-specific tools, making it possible to run classical computing applications on quantum computers, as well as for others to build their own applications. Aqua is one of four Qiskit elements:
  • Qiskit Terra: the ‘earth’ element, is the foundation on which the rest of the software lies. Terra provides a bedrock for composing quantum programs at the level of circuits and pulses.Qiskit Ignis: the ‘fire’ element, is dedicated to fighting noise and errors and to forging a new path. This includes better characterization of errors, improving gates, and computing in the presence of noise.
  • Qiskit Aer: the ‘air’ element, permeates all Qiskit elements. To really speed up development of quantum computers we need better simulators, emulators and debuggers.

News about IBM Q

Quantum Computing in the NISQ era and beyond

IBM Spectrum Scale v5 GUI

Management GUI enhancements in IBM Spectrum Scale release 5.0.0

Monitoring and Managing the IBM ESS Using the GUI

Configuring performance metrics and display options in the Statistics page of the GUI


Technical Blogs on IBM Spectrum Scale v5.0.2.0

  1. How NFS exports became more dynamic with Spectrum Scale 5.0.2
  2. HPC storage on AWS (IBM Spectrum Scale)
  3. Upgrade with Excluding the node(s) using Install-toolkit
  4. Offline upgrade using Install-toolkit
  5. IBM Spectrum Scale for Linux on IBM Z ? What’s new in IBM Spectrum Scale 5.0.2
  6. What’s New in IBM Spectrum Scale 5.0.2
  7. Starting IBM Spectrum Scale 5.0.2 release, the installation toolkit supports upgrade rerun if fresh upgrade fails.
  8. IBM Spectrum Scale installation toolkit enhancements over releases
  9. Announcing HDP 3.0 support with IBM Spectrum Scale
  10. IBM Spectrum Scale Tuning Overview for Hadoop Workload
  11. Making the Most of Multicloud Storage
  12. Disaster Recovery for Transparent Cloud Tiering using SOBAR
  13. Your Optimal Choice of AI Storage for Today and Tomorrow
  14. Analyze IBM Spectrum Scale File Access Audit with ELK Stack
  15. Mellanox SX1710 40G switch MLAG configuration for IBM ESS
  16. Protocol Problem Determination Guide for IBM Spectrum Scale SMB and NFS Access issues
  17. Access Control in IBM Spectrum Scale Object
  18. IBM Spectrum Scale HDFS Transparency Docker support
  19. Protocol Problem Determination Guide for IBM Spectrum Scale Log Collection

Enabling SRIOV in BIOS for IBM Servers and Blade Servers

Step 1: Power on the system, and press F1 to enter the Setup utility.

Step 2: Select System Settings and then Network.

Step 3: Under the Network Device List, select the device to be configured and press Enter to see all the Network Device options (Figure 1).


Step 4: Select the device’s description and press Enter to configure the device (Figure 2)


Step 5: From the selection menu, select Advanced Mode and press Enter to change the value (Figure 3).


Step 6: Choose Enable and press Enter.

Step 7: On the same selection menu, select Controller Configuration and press Enter to enter the configuration menu.

Step 8: Select Configure SRIOV and hit Enter.

Step 9: On the Configure SRIOV page, press Enter to toggle the values

Step 10: Select Enable and press Enter

Step 11: Select Save Current Configurations and press Enter.

Step 12: Press Esc to exit the menu. Then, click Save to save the configuration.

Step 13: Reboot the system.