On Mon, May 5, 2008 at 8:42 PM, snowcrash+openfiler <[EMAIL PROTECTED]> wrote: > hi, > > > What version of Xen? > > in my DomO (fedora8), > > uname -a > Linux server.loc 2.6.21.7-3.fc8xen #1 SMP Thu Mar 20 14:58:12 EDT > 2008 x86_64 x86_64 x86_64 GNU/Linux > > where, > > yum list | grep -i xen | grep installed > kernel-xen.x86_64 2.6.21.7-3.fc8 > installed > kernel-xen-devel.x86_64 2.6.21.7-3.fc8 > installed > xen.x86_64 3.1.2-2.fc8 > installed > xen-libs.x86_64 3.1.2-2.fc8 > installed > > and, in the OF DomU, the kernel's bundled in the appliance, of course, > > Linux openfiler.server.loc 2.6.16.29-0.11.smp.gcc3.4.x86_64.xen.domU > #1 SMP Wed Dec 6 02:05:30 EST 2006 x86_64 x86_64 x86_64 GNU/Linux > > > > I think I have seen this problem (or a similar one) before, but it was > > a long time ago. I think it had something to do with xvd* disks. > > i _am_ able to export/use Dom0-created LV's to _other_ DomU's as > xvd*'s with no problems. > > in the OF case, the xvda1 obviously is recognized, as i can boot ... > just that the xvdb is not seen by the OF gui 'app'. >
It still sounds familiar, maybe it was tap:aio vs. file:? Although that doesn't seem like your problem since you are using phy: Maybe the problem was fixed in a newer version of openfiler? As I recall, there is a way to trace through manually with openfiler manually with commands, maybe there are also log files on the openfiler server? _______________________________________________ Openfiler-users mailing list [email protected] https://lists.openfiler.com/mailman/listinfo/openfiler-users
