qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ajallooiean Hossein <hossein.ajallooiean@epfl.ch>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Looking for ideas: Single process vs multi process qemu instances
Date: Thu, 22 Jun 2017 10:45:45 +0100	[thread overview]
Message-ID: <87injotkxi.fsf@linaro.org> (raw)
In-Reply-To: <1498045580087.46004@epfl.ch>


Ajallooiean Hossein <hossein.ajallooiean@epfl.ch> writes:

> 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).

So you are talking about using TCG for simulation rather than KVM here?

>
>
> 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.

QEMU isn't really setup for multiple machine instances in the one
binary. If you are simulating a complex set of communicating machines
then you will need one QEMU instance per machine.

TCG can now use multiple threads (one per emulated vCPU) but this has
only been enabled for a subset of architectures so far. You don't say
what architecture your servers machines are.

>
>
> I am looking at this purely from a management/performance view.
>
>
> Any ideas/suggestions?
>
>
> Thanks
>
> Hoss


--
Alex Bennée

  reply	other threads:[~2017-06-22  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 11:46 [Qemu-devel] Looking for ideas: Single process vs multi process qemu instances Ajallooiean Hossein
2017-06-22  9:45 ` Alex Bennée [this message]
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=87injotkxi.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=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).