From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M5haI-0002yu-6l
	for qemu-devel@nongnu.org; Sun, 17 May 2009 10:43:26 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M5haC-0002yi-QR
	for qemu-devel@nongnu.org; Sun, 17 May 2009 10:43:24 -0400
Received: from [199.232.76.173] (port=41451 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M5haC-0002yf-Js
	for qemu-devel@nongnu.org; Sun, 17 May 2009 10:43:20 -0400
Received: from smtp136.mail.mud.yahoo.com ([209.191.107.119]:33384)
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <fcarrijo@yahoo.com.br>) id 1M5haC-0003Xy-5S
	for qemu-devel@nongnu.org; Sun, 17 May 2009 10:43:20 -0400
Subject: Re: [Qemu-devel] How does a system call work on QEMU?
From: Fernando Carrijo <fcarrijo@yahoo.com.br>
In-Reply-To: <4A0FCED5.6070005@yahoo.it>
References: <877930.94637.qm@web28603.mail.ukl.yahoo.com>
	<200905141119.01914.paul@codesourcery.com>	<4A0C184D.3030307@yahoo.it>
	<4A0C496B.3080601@redhat.com> <4A0C50D4.9020803@yahoo.it>
	<4A0C5985.6020206@redhat.com>  <4A0FCED5.6070005@yahoo.it>
Content-Type: text/plain
Date: Sun, 17 May 2009 11:41:35 -0300
Message-Id: <1242571295.4839.21.camel@pc-fernando>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Heli <helicoterus-elih@yahoo.it>
Cc: qemu-devel@nongnu.org

On Sun, 2009-05-17 at 10:46 +0200, Heli wrote:
> So it this the architecture of qemu, emulator version?
> QEMU is a process that gives to o.s.guest a virtual hw
> layer.
> Every guest will be run by a QEMU instance.
> 
> See picture schema I prepaired: http://yfrog.com/7gqemulayersj
> 
> So system calls go from a guest application to its
> operating system that communicates with its virtual
> hardware. QEMU receives a system call and software emulator
> QEMU performs a system call in O.S. host.
> It is right?

I'm not a virtualization person myself, so other people might offer you
more convenient sugestions but, with the due respect, I think you might
be better served by an introductory text on operating systems. The 3rd
edition of Andrew Tanenbaum's Modern Operating Systems, for instance,
has a short section specifically devoted to virtualization which is
clear enough to non-experienced readers and, I guess, answers most of
your questions.

Fernando Carrijo.