Hi All -

I am having trouble getting the x86 simulated full system to connect to the
network.  I have been trying for a few days now to get this to work, and I
have scoured the message lists, blog posts, FAQs, tutorials, etc. The most
useful document I have found is this:
https://www.mail-archive.com/[email protected]/msg00071.html

I think it would be useful to the community if there were a guide to
starting up an x86 multi-core full system simulation with gem5.

Some more specific questions follow...

Regarding simulated architecture: there is no longer an "X86_FS" config, so
which config should I use?  (is it X86_MESI_CMP_directory?)

Regarding the network, or lack thereof:  I compiled using the mesi/cmp
config mentioned above, obtained files as referred to by the message above,
namely the uncompressed linux kernel, x86_64-vmlinux-2.6.22.9.smp (very
old!!), and the files linux-bigswap2.img, and x86root.img.  After starting
the sim and connection in by telnet or m5term, I cannot ping anything and
other tools (i.e. ifconfig, etc) don't work because there is nothing in
/proc.  The meta question being, what else do I need to do... how do I get
to full system sim + network + ability to use wget, apt-get or yum, etc.

Regarding disk images: I have also tried making my own disk image, but
after reading several blog posts and message board replies, this has not
proved very fruitful (yet).  Perhaps this is the right path, but I'd like
some indication that it is (i.e. before investing time in this further).

Regarding feasibility:  is full system + server apps + network even
possible?  If yes, then I am willing to invest my time here, but of course
it would be good to know I am attempting something that is reasonably well
supported.

For context, I plan to extend the work of my Ph.D. thesis, namely
investigations into deduplicated memory systems.

Thank you,
Pete Stevenson
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to