There seem to be a couple of assumptions here that would be worth examining further.
My first thought is that running Lustre under something like Xen might be very usefull for virtualization, failover, and load balancing. If there is some potential resource deadlock that could occur, there ought to be some diagram or documentation of what deadlocks are possible. It would be a lot of work to conclusively figure out what the potential deadlocks actually are.. But it seems like a worthwhile excercise, and running Lustre in a VM would be a good way to do QA testing so that new deadlocks are not added by code changes. On Fri, Aug 15, 2008 at 03:17:39PM -0700, Klaus Steden wrote: > > Hi Robert, > > You're likely to find that performance will suffer when run under a VM. > Lustre makes pretty extensive use of all the resources at its disposal, and > having to compete with physical devices under a VM that runs as an ordinary > user process is more than likely going to lead to resource deadlocks. > > I wouldn't suggest running Lustre under VMs. > > cheers, > Klaus > _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
