Skip to main content

Red Hat Enterprise Linux 6 technology capabilities and limits


Red Hat Enterprise Linux 6 technology capabilities and limits
·         Red Hat Enterprise Linux Server version comparison
·         Red Hat Enterprise Linux Desktop version comparison
·         Virtualization limits for Red Hat Enterprise Linux hypervisors
Version 3
Version 4
Version 5
Version 6
Maximum logical CPUs [2]




x86
16
32
32
32
Itanium 2
8
256/512
256/1024
N/A[6]
x86_64
8
64/64
160/255
160/4096
POWER
8
64/128
128/128
128
System z
64 (z900)
64 (z10 EC)
101 (zEC12)
101 (zEC12)
Maximum memory[5]




x86
64GB[3]
64GB[3]
16GB[4]
16GB[4]
Itanium 2
128GB
2TB
2TB
N/A[6]
x86_64
128GB
256GB/1TB
1TB
3TB/64TB
POWER
64GB
128GB/1TB
512GB/1TB
2TB
System z
256GB (z900)
1.5TB (z10 EC)
3TB (z196)
3TB (z196)
Required minimums




x86
256MB
256MB
512MB minimum/
1 GB/logical CPU recommended
512MB minimum/
1 GB/logical CPU recommended
x86_64
256MB
256MB
512MB minimum/
1 GB/logical CPU recommended
1GB minimum/
1 GB/logical CPU recommended
Itanium 2
512MB
512MB
512MB/
1 GB/logical CPU recommended
N/A[6]
POWER
512MB
512MB
1GB minimum/
2GB recommended
2GB minimum/
2GB required per install
Minimum diskspace
800MB
800MB
1GB minimum/
5GB recommended
1GB minimum/
5GB recommended
File systems and storage limits




Maximum filesize (Ext3)
2TB
2TB
2TB
2TB
Maximum file system size (Ext3)
2TB
8TB
16TB
16TB
Maximum file size (Ext4)
--
--
16TB
16TB
Maximum file system size (Ext4)
--
--
16TB
16TB
Maximum file size (GFS)
2TB
16TB/8EB
16TB/8EB[7]
N/A
Maximum file system size (GFS)
2TB
16TB/8EB
16TB/8EB[7]
N/A
Maximum file size (GFS2)
--
--
100TB
100TB
Maximum file system size (GFS2)
--
--
100TB
100TB
Maximum file size (XFS)
--
--
100TB
100TB
Maximum file system size (XFS)
--
--
100TB
100TB
Maximum Boot LUN size (BIOS)
--
--
2TB
2TB
Maximum Boot LUN size (UEFI)
--
--
N/A
Any[10]
Maximum x86 per-process virtual address space
Approx. 4GB
Approx. 4GB
Approx. 3GB[4]
Approx. 3GB[4]
Maximum x86_64 per-process virtual address space

512GB
2TB
128TB
Kernel and OS features




Kernel foundation
Linux 2.4.21
Linux 2.6.9
Linux 2.6.18
2.6.32 - 2.6.34
Compiler/toolchain
GCC 3.2
GCC 3.4
GCC 4.1
GCC 4.4
Languages supported
10
15
19
22
NIAP/CC certified[11]
Yes (3+)
Yes (4+)
Yes (4+)
Under evaluation
Common Criteria certified KVM[11]
--
--
Under evaluation
Under evaluation
IPv6
--
--
Ready Logo Phase 2
Under evaluation
Compatibility libraries
V2.1
V2.1 and V3
V3 and V4
V4 and V5
FIPS certified[11]
--
--
Yes
Under evaluation
Common Operating Environment (COE) compliant
Yes
Yes
N/A
N/A
LSB-compliant
Yes - 1.3
Yes - 3
Yes - 3.1
Under evaluation
GB18030
No
Yes
Yes
Yes
Client environment




Desktop GUI
Gnome 2.2
Gnome 2.8
Gnome 2.16
Gnome 2.28
Graphics
XFree86
X.org
X.org 7.1.1
X.org 7.4
OpenOffice
V1.1
V1.1.2
V2.0.4[12]
V3.2[12]
Gnome Evolution
V1.4
V2.0
V2.8.0
V2.28
Default browser
Mozilla
Firefox
Firefox 1.5[12]
Firefox 3.6[12]



Comments

Post a Comment

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image downloaded we can start a contai
Post a Comment
Read more

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --now cockpit.socket If firewall is runnin
Post a Comment
Read more

Containers Without Docker on RHEL/Fedora

Docker is perfectly doing well with the containerization. Since docker uses the Server/Client architecture to run the containers. So, even if I am a client or developer who just wants to create a docker image from Dockerfile I need to start the docker daemon which of course generates some extra overhead on the machine.  Also, a daemon that needs to run on your system, and it needs to run with root privileges which might have certain security implications. Here now the solution is available where we do not need to start the daemon to create the containers. We can create the images and push them any of the repositories and images are fully compatible to run on any of the environment.  Podman is an open-source Linux tool for working with containers. That includes containers in registries such as docker.io and quay.io. let's start with the podman to manage the containers.  Install the package  [root@rhel8 ~] # dnf install podman -y  OR [root@rhel8 ~] # yum
1 comment
Read more