SUSE Linux Enterprise Server 10 Tech Specs & System Requirements
SUSE Linux Enterprise Server Technical Specifications
Linux Server System Requirements
Minimum Linux server system requirements for installation
- Local installation: 512 MB RAM, SSH-based network
- Graphical installation: 512 MB RAM, VNC-based network
- Installation via FTP: 512 MB RAM
Minimum Linux server system requirements for operation
- 512 MB RAM
- 750 MB hard disk space for software
- 750 MB hard disk space for user data
Recommended Linux server system requirements
- At least 512 MB RAM for Xen virtual host server
- At least additional 256 MB RAM per Xen virtual machine
Supported processor platforms
- AMD64
- IBM POWER
- IBM System z (64-bit)
- Intel 64
- Itanium Processor Family (Itanium II or newer)
- x86
Package Descriptions
Detailed descriptions of all packages included on SUSE® Linux Enterprise Server. Check the support site to see the list of supported packages.
SUSE Linux Enterprise Server 10 Service Pack 2 for x86
SUSE Linux Enterprise Server 10 Service Pack 2 for AMD64 & Intel EM64T
SUSE Linux Enterprise Server 10 Service Pack 2 for Intel Itanium Processor Family
SUSE Linux Enterprise Server 10 Service Pack 2 for IBM PPC
SUSE Linux Enterprise Server 10 Service Pack 2 for IBM zSeries
SUSE Linux Enterprise Server 10 Service Pack 1 for x86
SUSE Linux Enterprise Server 10 Service Pack 1 for AMD64 & Intel EM64T
SUSE Linux Enterprise Server 10 Service Pack 1 for Intel Itanium Processor Family
SUSE Linux Enterprise Server 10 Service Pack 1 for IBM PPC
SUSE Linux Enterprise Server 10 Service Pack 1 for IBM zSeries
SUSE Linux Enterprise Server 10 for x86
SUSE Linux Enterprise Server 10 for AMD64 & Intel EM64T
SUSE Linux Enterprise Server 10 for Intel Itanium Processor Family
SUSE Linux Enterprise Server 10 for IBM PPC
SUSE Linux Enterprise Server 10 for IBM zSeries
Kernel Limits
This table summarizes the various limits which exist in our recent kernels and utilities (if related) for SUSE Linux Enterprise 10 Service Pack 2. This is Novell's award-winning family of Linux operating system products based on a common code base, including SUSE Linux Enterprise Server 10, SUSE Linux Enterprise Desktop 10, SUSE Linux Enterprise Real Time 10 and others.
φ = insufficient data| SLE 10 SP2 (2.6.16.60 |
x86 (IA-32) |
ia64 (Itanium) |
x86_64 (AMD64/EM64T) |
s390x (IBM System z) |
ppc64 (IBM System p) |
|
|---|---|---|---|---|---|---|
| Kernel related items | ||||||
| CPU bits | 32 | 64 | 64 | 64 | 64 | |
| max. # CPUs | 32 (up to 128 with bigsmp kernel on certified systems) |
up to 4096 (on certified SGI systems) |
32 (up to 128 on certified systems) |
64 | 128 | |
| max. RAM (theoretical / certified) | 64/16 GiB | 1 PiB/4 TiB | 64 TiB/512 GiB | 4 TiB/256 GiB | 1 PiB/512 GiB | |
| max. swap space | up to 32 * 64 GB | |||||
| max. user-/kernelspace | 3/1 GiB | 2 EiB/φ | 128 TiB/128 TiB | φ/φ | 2 TiB/2 EiB | |
| max. #processes | 1048576 | |||||
| max. #threads per process | tested with more than 120000; maximum limit depends on memory and other parameters | |||||
| max. size per block device | up to 16 TiB on 32-bit architectures, and up to 8 EiB on 64-bit architectures | |||||
| Filesystem related items | ||||||
| max. filesystem size | ext2/3: 16 TiB (244 bytes) nfs v2: 8 EiB (263 bytes) nfs v3: 8 EiB (263 bytes) nfs v4: 8 EiB (263 bytes) reiserfs: 16 TiB (244 bytes) xfs: 8 EiB (263 bytes) ocfs2: 16 TiB (244 bytes) |
|||||
| max. file size | ext2/3: 2 TiB (241 bytes) jfs: 8 EiB (263 bytes) nfs v2: 2 GiB (231 bytes) nfs v3: 8 EiB (263 bytes) reiserfs: 1 EiB (260 bytes), but page cache limits this to 8 TiB on architectures with 32 bit int xfs: 8 EiB (263 bytes) ocfs2: 1 EiB (260 bytes) |
|||||
Remarks:
- The maximum file size above can be larger than the filesystem's actual size due to usage of sparse blocks. It should also be noted that unless a filesystem comes with large file support (LFS), the maximum file size on a 32-bit system is 2 GiB (231 bytes). Currently all of our standard filesystems (including ext3 and ReiserFS) have LFS, which gives a maximum file size of 263 bytes in theory. The numbers given in the above table assume that the filesystems are using 4 KiB block size. When using different block sizes, the results are different, but 4 KiB reflects the most common standard.
- The rationale for the use of theoretical vs. certified in the following tables is as follows: theoretical means that's what should work, at least theoretically, while certified describes something which Novell and our Partners have tested and certified to work on existing machines in real life scenarios. With this explanation, the values for the x86, i.e. 32-bit bigsmp kernels should have been 64 GiB in the first place, but everyone knows that would just be too theoretical as it doesn't really work (and if it did in older kernels, only for very special configurations and workloads).
- In this document: 1024 Bytes = 1 KiB; 1024 KiB = 1 MiB; 1024 MiB = 1 GiB; 1024 GiB = 1 TiB; 1024 TiB = 1 PiB; 1024 PiB = 1 EiB (see also http://physics.nist.gov/cuu/Units/binary.html)