Description of problem: When choosing virtualization support in a rhel5beta1 client install, there is no Xen hypervisor and Xen-enabled kernel installed *but* grub contains (as default entry) the non-existing Xen-enabled kernel! /etc/grub.conf: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Red Hat Enterprise Linux Client (2.6.17-1.2519.4.21.el5xen) root (hd0,0) kernel /xen.gz-2.6.17-1.2519.4.21.el5 module /vmlinuz-2.6.17-1.2519.4.21.el5xen ro root=/dev/hda6 rhgb quiet title Red Hat Enterprise Linux Client-up (2.6.17-1.2519.4.21.el5) root (hd0,0) kernel /vmlinuz-2.6.17-1.2519.4.21.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.17-1.2519.4.21.el5.img Contents of /boot: config-2.6.17-1.2519.4.21.el5 message.ja grub symsets-2.6.17-1.2519.4.21.el5.tar.gz initrd-2.6.17-1.2519.4.21.el5.img symvers-2.6.17-1.2519.4.21.el5.gz lost+found System.map-2.6.17-1.2519.4.21.el5 message vmlinuz-2.6.17-1.2519.4.21.el5 rpm -qa | grep kernel: kernel-2.6.17-1.2519.4.21.el5 kernel-headers-2.6.17-1.2519.4.21.el5 kernel-devel-2.6.17-1.2519.4.21.el5
Additional comment: /etc/sysconfig/kernel contains DEFAULTKERNEL=kernel-xen, while kernel-xen is not installed!
Can you attach /var/log/anaconda* and /root/install.log?
Created attachment 137090 [details] /root/install.log
Created attachment 137091 [details] /var/log/anaconda.log
Created attachment 137092 [details] /var/log/anaconda.syslog
requested by Jams Antill
Is this bug still a problem? If not, can we close it out? Thanks, Chris Lalancette
Feel free to reopen this bug if you continue to experience this problem in RHEL5.1 or 5.2. Thanks.