Description of problem: Right now, after a user kickstarts a machine to be a paravirtualization host they need to modify the /etc/grub.conf file so that the Xen kernel is used by default. We should do this automatically as part of the paravirtualization host kickstart process, preferably in the %post section of the kickstart.
*** Bug 208590 has been marked as a duplicate of this bug. ***
Fixed in SVN. Test Plan. 1. On a 500-beta satellite, sync the beta channels (if necessary). 2. Subscribe a suitable virt-host to the satellite. 3. If necessary, create a virtualization-host kickstart profile. 4. Kickstart the system to the virtualization-host kickstart profile. 5. After the kickstart, check /etc/grub.conf and make sure that default=0 and that the first entry is the xen kernel.
Verified. Grub file now looks like: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Red Hat Enterprise Linux Server (2.6.18-1.2747.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-1.2747.el5 module /vmlinuz-2.6.18-1.2747.el5xen ro root=/dev/myvg/rootvol module /initrd-2.6.18-1.2747.el5xen.img
Closed for RHN 500 Beta.