Description of problem: pygrub in RHEL 5.4 doesn't support ext4, which is the default fs type for /boot in Fedora 12. Version-Release number of selected component (if applicable): xen-3.0.3-94.el5_4.2 How reproducible: always Steps to Reproduce: 1. Install RHEL 5.4 dom0 host 2. Install Fedora 12 (rawhide) PV guest with the default options 3. F12 guest fails to start after installation Actual results: Guest fails to start with error message - bootloader didn't return any data Expected results: Guest starts normally Additional info: Running pygrub from the cmdline for F12 guest with ext4 /boot gives this: # pygrub --output=/tmp/foo/pygrub-output /dev/vg00/f12test Traceback (most recent call last): File "/usr/bin/pygrub", line 677, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported While pygrub works OK for guests with ext3 /boot. xen.spec is missing BuildRequires: e2fsprogs-devel ?
*** This bug has been marked as a duplicate of bug 524611 ***
Any particular reason that 524611 needs to be private? Also, just did a rawhide (F13) domU install on CentOS 5.4 dom0 with: part /boot --size=100 --type=ext3 part / --size=3000 --grow part swap --recommended but getting the above pygrub error. I have a F11 domU guest with the same config, so not sure what is up yet.
Please check whether /boot is really ext3. I'm not sure, but I think F13 anaconda overrides it to ext4.
F12 does override to ext4, should be fixed in F13, but no install images at the moment. Sorry about the noise.
Workaround until RHEL5 Xen pygrub supports ext4 is to use Fedora 12 updates.img to fix the F12 installer allowing you to create ext3 /boot for real. updates.img available here: https://bugzilla.redhat.com/show_bug.cgi?id=529846