<mailto:
minovotn@xxxxxxxxxx>>> wrote:
On 06/19/2010 06:07 PM, Pasi Kärkkäinen wrote:
On Sat, Jun 19, 2010 at 05:00:57PM +0100, David Markey
wrote:
XCP pygrub should have ext4 support.
It currently doesn't because the libfsimage
ext2fs-lib
module is linked
against libext2fs, which doesnt have ext4
support in XCP.
Instead, XCP should use the ext2fs module that comes
with libfsimage,
which has ext4 support.
Most new releases of distributions has it as their
default filesystem.
Most notably, Ubuntu 10.04
Also Fedora 12, Fedora 13, upcoming Debian 6.0
("Squeeze") and
RHEL6.
-- Pasi
Well, this is not the Xen issue here. We're having this
fixed in
RHEL-5 by simply reinstalling the e2fsprogs package to the
latest
one, although in case of RHEL-5 it's been renamed to e4fsprogs.
The simplest thing you can do about this is to reinstall the
e2fsprogs package on the host machine and it will be
working fine
- at least it was when I did test it on RHEL-5 some time ago.
Simply put, reinstalling the e2fsprogs to the latest
version will
do the job and allow ext4 functionality to pygrub.
Michal
An easy way for the build to use ext2fs instead of
ext2fs-lib, is to not
have ext2fs/ext2fs.h present.
Alternatively this patch hard codes it.
(From 4.0)
--- a/tools/libfsimage/Makefile 2010-06-19
16:52:04.231221516
+0100
+++ b/tools/libfsimage/Makefile 2010-06-19
16:52:08.803250922
+0100
@@ -1,8 +1,7 @@
XEN_ROOT = ../..
include $(XEN_ROOT)/tools/Rules.mk
-SUBDIRS-y = common ufs reiserfs iso9660 fat zfs
-SUBDIRS-y += $(shell env CC="$(CC)"
./check-libext2fs)
+SUBDIRS-y = common ufs reiserfs iso9660 fat zfs
ext2fs
.PHONY: all clean install
all clean install: %: subdirs-%
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
<mailto:
Xen-devel@xxxxxxxxxxxxxxxxxxx>
<mailto:
Xen-devel@xxxxxxxxxxxxxxxxxxx
<mailto:
Xen-devel@xxxxxxxxxxxxxxxxxxx>>
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
<mailto:
Xen-devel@xxxxxxxxxxxxxxxxxxx>
<mailto:
Xen-devel@xxxxxxxxxxxxxxxxxxx
