This is an open question to OMPI developers...
It looks like RHEL (and maybe others?) adds the "virbr0" IP interface when Xen
is activated. This IP interface is only used to communicate with the local Xen
instance(s); it is not used to communicate over the real network.
In a case that I saw,
On Feb 10, 2012, at 9:50 AM, Jeff Squyres wrote:
> This is an open question to OMPI developers...
>
> It looks like RHEL (and maybe others?) adds the "virbr0" IP interface when
> Xen is activated. This IP interface is only used to communicate with the
> local Xen instance(s); it is not used t
On 2/10/2012 11:50 AM, Jeff Squyres wrote:
This is an open question to OMPI developers...
It looks like RHEL (and maybe others?) adds the "virbr0" IP interface when Xen
is activated. This IP interface is only used to communicate with the local Xen
instance(s); it is not used to communicate
On Feb 10, 2012, at 1:00 PM, TERRY DONTJE wrote:
>> Should we add "virbr0" to the default value for [btl|oob]_tcp_if_exclude?
>>
> What happens to that value if you then set btl_tcp_if_exclude to some value
> on the mpirun command line?
It works just fine. I.e., if you
mpirun --mca bt
On 2/10/2012 10:38 AM, Jeff Squyres wrote:
On Feb 10, 2012, at 1:00 PM, TERRY DONTJE wrote:
>> Should we add "virbr0" to the default value for [btl|oob]_tcp_if_exclude?
>>
> What happens to that value if you then set btl_tcp_if_exclude to some value
on the mpirun command line?
It works
On Feb 10, 2012, at 1:44 PM, Paul H. Hargrove wrote:
> Since the situation described is one where the user didn't know they
> could/should disable xen, it is reasonable to think they ALSO don't know they
> need to exclude virbr0.
That's what I'm thinking.
> So, I read the question as meaning
On 2/10/2012 12:03 PM, Jeff Squyres wrote:
On Feb 10, 2012, at 1:44 PM, Paul H. Hargrove wrote:
Since the situation described is one where the user didn't know they
could/should disable xen, it is reasonable to think they ALSO don't know they
need to exclude virbr0.
That's what I'm thinkin
On Feb 10, 2012, at 3:14 PM, Paul H. Hargrove wrote:
> + User knows nothing about xen, and thus nothing about virbr0
> + User has a local-only interface (eth8 in my made up example)
> + User reads FAQ entry "220. How do I tell Open MPI which TCP networks to
> use?"
> + User follows instructions g
On 2/10/2012 12:21 PM, Jeff Squyres wrote:
On Feb 10, 2012, at 3:14 PM, Paul H. Hargrove wrote:
+ User knows nothing about xen, and thus nothing about virbr0
+ User has a local-only interface (eth8 in my made up example)
+ User reads FAQ entry "220. How do I tell Open MPI which TCP networks t
This topic has gotten a *lot* of off-list discussion. :-)
Just to tie up the thread for the web archives: this topic will be discussed on
the Tuesday teleconf next week. Terry: please add this to the Tuesday agenda.
On Feb 8, 2012, at 9:53 PM, Ralph Castain wrote:
> I agree - we do have bet
On Feb 10, 2012, at 3:32 PM, Paul H. Hargrove wrote:
> The point of the question isn't related to WHY eth8 is useless - just assume
> it is.
> Assume it is UP, but useless for whatever reasons motivated writing FAQ #220.
> It could be Terry's example of a port connected to the service processor.
Check out #220 now; I updated it.
Sent from my phone. No type good.
On Feb 10, 2012, at 4:46 PM, "Jeff Squyres" wrote:
> On Feb 10, 2012, at 3:32 PM, Paul H. Hargrove wrote:
>
>> The point of the question isn't related to WHY eth8 is useless - just assume
>> it is.
>> Assume it is UP, but u
Much better - at least to the extent that users actually read FAQs :-)
-Paul
On 2/10/2012 5:01 PM, Jeff Squyres (jsquyres) wrote:
Check out #220 now; I updated it.
--
Paul H. Hargrove phhargr...@lbl.gov
Future Technologies Group
HPC Research Department
FWIW: google analytics indicates that the FAQ and the mailing list archives are
among the most heavily used sections of the web site. :-)
On Feb 10, 2012, at 8:09 PM, Paul H. Hargrove wrote:
> Much better - at least to the extent that users actually read FAQs :-)
> -Paul
>
> On 2/10/2012 5:01
That's probably a reflection of the status of the "Open MPI User
Documentation" sub-project :-)
On 2/10/2012 5:12 PM, Jeff Squyres wrote:
FWIW: google analytics indicates that the FAQ and the mailing list archives are
among the most heavily used sections of the web site. :-)
--
Paul H. Harg
On Feb 7, 2012, at 4:25 PM, Paul H. Hargrove wrote:
> + I can't build w/ the PGI compilers on MacOS Lion.
> This was previously reported in
> http://www.open-mpi.org/community/lists/devel/2012/01/10258.php
I'm officially pushing this to v1.6. See
https://svn.open-mpi.org/trac/ompi/ticket/3011.
On Feb 10, 2012, at 8:57 PM, Jeff Squyres wrote:
> 1.5.5rc2 coming soon.
I should qualify that statement: many things have been resolved, but there's a
few more things to go. A new rc will come when they have been resolved:
https://svn.open-mpi.org/trac/ompi/report/15
--
Jeff Squyres
jsquy
Usual location:
http://www.open-mpi.org/software/ompi/v1.4/
Changes since rc5:
- document LD_LIBRARY_PATH for -m32 with Ubuntu/Sun compilers
- refuse to configure with gccffs
- LANL TLCC2 platform files
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.ci
18 matches
Mail list logo
