Check the output. 3456 is the default port for terminal connections, but obviously if you're simulating multiple systems on the same host (in the same or separate instances of gem5) they can't all use the same port, so they'll increment the port number until they find a free one. The output will tell you which port number(s) is/are being used.
Steve On Mon, Apr 16, 2012 at 7:50 AM, Anirudh Sivaraman <[email protected]>wrote: > Hi > > I have been trying to modify twosys-tsunami-simple-atomic to work with > EtherTap instead of EtherLink. I have connected the TCP listener port > on the GEM5 end to a tap interface using socat. I have also checked > that if I inject packets into the tap interface, GEM5 is able to see > them. I now want to ping one GEM5 instance from another using a tap > interface. > > So, after running : > build/ALPHA/gem5.opt tests/run.py > > build/ALPHA/tests/opt/quick/fs/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic > > I run m5term localhost 3456 so that I can interact with the simulated > system. This returns immediately and doesn't open a shell as it > usually does. As far as I know, this is the only way to get a shell on > GEM5. Is there a better way ? > > Anirudh > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
