As promised yesterday, I publish the results of a brief test of RHEL6 Beta 1 and the most important findings. It is my point of view as a system guys daily business. If not stated, this overview is based on a default installation with no customization.
- There are new package groups such as “Minimal” with 228 Packages and “Basic Server” with 523 Packages. “Basic Server” is the default installation, which means the default click trough installation compared to RHEL5 is much less bloated.
- The versions of the most important software is quite up-to-date but as expected not on the bleeding edge.
- ext4 is the default file system. Hopefully the fsync issues are solved. See more here: http://lwn.net/Articles/322823/
- Postfix is the default MTA. Finally Red Hat managed to switch away from sendmail like other distributions did it years ago.
- Bye bye SysV init: As I guesstimated in october 2009 RHEL6 comes with upstart instead of traditional SysV init. (See http://blog.delouw.ch/2009/10/31/ready-to-upstart/). The boot process is much faster compared to RHEL5. Upstart comes with legacy support for traditional runcontrol scripts in /etc/init.d.
- Still too many services enabled after default install. Generally unneeded services like avahi/mDNS and NFS-related daemons such as portmap are still enabled by default.
As expected, Xen was removed completely from RHEL6. These is being discussed controversial. Why not providing both virtualization solutions as before? Recently Citrix released Xen4 which works well together with Kernel 2.6.32, the same version as used by RHEL6.
KVM and its friends made a huge step forward. lib-virt, virt-manager and stuff is nearly up-to-date with the upstream versions. Means: The virtualization infrastructure made a lot of progress. Installing RHEL6 as a KVM guest works great. All drivers needed (virtio) are automatically installed.
A major good message to people which are using VMware vPhere 4 is that RHEL 6 comes which native support of vmxnet3 which was obviously backported from Kernel 2.6.33. Vmxnet3 is the driver for VMware’s para-virt NIC which brings quite some performance enhancements and lower CPU usage on the ESX host.
Certifications from ISVs
A quick check (not actually tested) for the requirements for SAP and Oracle shows that those are fulfilled already. We can expect the certification quite soon after GA of RHEL6. [update] Some compatibility RPMs from the mid 1990’s disappeared. I now need to figure out if they are *really* needed by Oracle and/or SAP[/update]
Integration with Cobbler
Integration with cobbler works like expected, cobbler import –path=/mnt –name=rhel6 and you are done. For a quick test I just copied the kickstart template from RHEL5 and I’m not sure if this is a good method. A test-install on ESX4 failed, the system hung at the creating of the root-VG. Not sure yet if it is a bug or something is incompatible in the kickstart. [update] The system hung was because of out-of-memory. The test-installation was on a ESX guest with 384Mbyte of memory which is enough according to the documentation but too little in real life. Growing the RAM of the test system to 512Mybte helped, but some packages needed by for SAP have changes names or disappeared. After changing/removing those RPMs, the installation went smoothly[/update]
Bugs or features?
I detected some oddities where I’m not sure if it is a bug or a feature. We will see whats going on on http://bugzilla.redhat.com.
- No network configured after default install. At the moment you need to configure it manually (considered a Bug)
- I detected a major security issue during install, I’m not going to disclose it before a patch is available or more information from Red Hat is made available. I reported it 2010-04-23 ~12:00 on Red Hats bugzilla bugtracker. [update] The bug gots assigned to a Red Engineer after three hours, seems like Red Hat is acting very professional on the case[/update]
After this brief test one can say that RHEL6 will be a really great Linux Distribution for enterprise servers. The beta is already very stable with few bugs detected from my side. My guesstimate is that mid of May 2010 there will be a second public beta released, lets stay tuned, I’ll keep you up-to-date with further findings.
3 thoughts on “A brief test of RHEL 6 Beta 1”
Thanks for your report.
And you probably mean May 2010, you wrote 2009.
Corrected, thanks for reporting.
Network Icon’s on the top right hand corner say “Wired Network (Broadcom NetXtreme II Gigabit Ethernet) device not managed. Boot messages the only failure is “Bringing up Interface Wired_connection_1: Device does not seem to be present, delaying initialization. [FAILED]. I’m using a Dell PowerEdge 2950. Does this have to do with the configure manually settings. Can you please show an example.