Description of problem: Created a rawhide virtual machine using a kickstart. The kickstart contained the line part /boot --fstype=ext3 --size=400 but the /boot fs was still created as ext4.
This is by design - anaconda checks to make sure that /boot is of a certain type and if not, corrects the request to be of that type. This is to make sure people don't do anything crazy like put /boot on vfat or something else that we won't be able to boot from later.
I really think that kickstart files should be honored. It seems strange to me that I'm allowed to do a kickstart install without a /boot file system, or, if I install manually, I can select ext3 for /boot, but I can't kickstart it that way. If a person doing manual partition table management can be trusted to select an appropriated fs, then I think the person writing a kickstart should be trusted as well. Besides that, some boot loaders (xen pygrub, for example) lag behind a bit, and when you override the /boot fs to a newer, still not supported fs, then the new system is unbootable. Reopenning for the arguments above.
This should be fixed in the next build of anaconda for Rawhide, but not for F12.
*** Bug 531951 has been marked as a duplicate of this bug. ***
So how to I kickstart my F12 Xen domU installs for my RHEL5.4 dom0 if this has been pushed to rawhide?
Created attachment 373556 [details] updates.img to allow setting /boot fstype in kickstart See https://fedoraproject.org/wiki/Anaconda/Updates for how to use.