WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have
preserved to ensure that existing links to archives are not broken.
The live archive, which contains the latest emails, can be found at
http://lists.xen.org/

You should be at update 4, or switch directly to RHEL 5 or CentOS 5.
Seriously, it's a big improvement in running Xen.

If you *HAVE* to run Xen on RHEL 4 as Dom0, use Xen 3.1.0 from Xensource
or something more up to date. Don't consult from sources unless you have
to, and unless you feel like upgrading these things yourself all the time.

What? OK, shut *down* the DomU. Use kpartx to split the file or
partition into the filesystems that are on it, if necessary, then mount
them directly on the Dom0 to examine. And run fsck on those enabled
partitions, as needed.

Does everybody encounters this problem before ?
Do you think that should be caused by using an ext3 (with logging) for
vm's filesystem (wich are using .img files) ?

Unlikely. But why are you doing this instead of using LVM partitions
directly, and mounting those either as /dev/sda or as /dev/sda1?

Any suggestions about using caches management for DomU and Dom0 ? (do we
need to delete cache and ext3 logging on DomUs)

It sounds like you need to run fsck.ext3 on the partitions. But do it
from Dom0.