Just gave this a quick try, and xmvapich seems to run MPI apps compiled with mpich2 without any issues.
$ xmvapich -a ./mpihello blender: Hello World from process 0 of 1 eregion: Hello World from process 0 of 1 Hope that helps, -- Abhishek On Tue, 2008-09-30 at 17:02 +0200, Stefan Boresch wrote: > Thanks for the quick reply! > > On Tue, Sep 30, 2008 at 07:34:37AM -0700, ron minnich wrote: > > > > On Tue, Sep 30, 2008 at 1:57 AM, stefan <[EMAIL PROTECTED]> wrote: > > > > > > the state of xcpu support with MPI libraries -- either of the common > > > free ones > > > is fine (e.g., openmpi, mpich2) > > > > > > > there is now support for mpich2. openmpi is not supported as openmpi > > is (once again) in flux. it has been supported numerous times and has > > changed out from under us numerous times. I no longer use openmpi if I > > have a working mvapich or mpich available. > > > > I am slightly confused. I guess I had inferred the openmpi issues from > the various mailing lists. But I just looked at the latest mpich2 > prerelease and found no mentioning of (s)xcpu(2). I thought that some > patches/support on the side of the mpi library are necessary (as, e.g., > openmpi provides for bproc ...) Or am I completely misunderstanding > something here, and this is somehow handled by xcpu itself ... > I guess there is some difference between > > xrx 192.168.19.2 /bin/date > > and > > xrx 192.168.19.2 <pathto>/mpiexec ... > > and the latter seems too magic to me to run out of the box (it sure > would be nice though ...) > > Sorry for making myself a nuisance -- thanks, > > Stefan Boresch > > >
