From: Ajallooiean Hossein <hossein.ajallooiean@epfl.ch>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Looking for ideas: Single process vs multi process qemu instances
Date: Wed, 21 Jun 2017 11:46:20 +0000 [thread overview]
Message-ID: <1498045580087.46004@epfl.ch> (raw)
Hi All,
we are trying to do server simulation and for that purpose we need to have multiple Qemu instances (each can have a different spec) that are part of a virtual network (ns-3 in our case).
Now for the Qemu implementation part: would it be easier/better to have all the Qemu instances under a single process or multiple processes? i am assuming if one single process is used, there will be a threading conflict that would probably need to be looked at.
I am looking at this purely from a management/performance view.
Any ideas/suggestions?
Thanks
Hoss
next reply other threads:[~2017-06-21 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 11:46 Ajallooiean Hossein [this message]
2017-06-22 9:45 ` [Qemu-devel] Looking for ideas: Single process vs multi process qemu instances Alex Bennée
2017-06-24 9:57 ` Ajallooiean Hossein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1498045580087.46004@epfl.ch \
--to=hossein.ajallooiean@epfl.ch \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).