From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ht2FD-0000Tl-8K
	for qemu-devel@nongnu.org; Tue, 29 May 2007 10:00:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ht2FB-0000TW-Nn
	for qemu-devel@nongnu.org; Tue, 29 May 2007 10:00:13 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ht2FB-0000TT-Fd
	for qemu-devel@nongnu.org; Tue, 29 May 2007 10:00:13 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <Johannes.Schindelin@gmx.de>) id 1Ht2FA-0007ik-RC
	for qemu-devel@nongnu.org; Tue, 29 May 2007 10:00:13 -0400
Date: Tue, 29 May 2007 14:59:58 +0100 (BST)
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [Qemu-devel] Re: Accepting socket connections in qemu (not the
	client... the emulator)
In-Reply-To: <465C30F5.40307@gmx.at>
Message-ID: <Pine.LNX.4.64.0705291458520.4648@racer.site>
References: <20070528160302.540gmx1@mx058.gmx.net> <465C219F.2040206@gmx.at>
	<465C2C2F.5000600@gmx.at> <Pine.LNX.4.64.0705291444080.4648@racer.site>
	<465C30F5.40307@gmx.at>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: qemu-devel@nongnu.org
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: Clemens Kolbitsch <clemens.kol@gmx.at>
Cc: qemu-devel@nongnu.org

Hi,

On Tue, 29 May 2007, Clemens Kolbitsch wrote:

> Johannes Schindelin wrote:
> > Hi,
> > 
> > On Tue, 29 May 2007, Clemens Kolbitsch wrote:
> > 
> >   
> > > Clemens Kolbitsch wrote:
> > > 
> > >     
> > > > my virtual device inside qemu (a pci device) is listening for
> > > > socket-(tcp)-connections.
> > > > 
> > > > however, accept() always fails (code works fine if not executed inside
> > > > the qemu-process)... now i'm wondering if qemu interferes somehow...
> > > > 
> > > > is that possible?
> > > > 
> > > > frustrated.... *gg*
> > > > 
> > > >       
> > > ok.... i found an answer to it.
> > > 
> > > obviously, qemu has to handle interrupt-signals (e.g. from its
> > > client-os). this interrupts accepting connections.
> > > 
> > > very bad for me, but at least a logical reason :-/
> > >     
> > 
> > I guess that you use the Slirp device. This device is masqueraded to the
> > outside, so unless you use something different, like VLAN or TAP, you can
> > only make it work using a tunnel.
> > 
> >   
> no... i think you misunderstand...
> 
> I'm trying to accept a socket inside the qemu-emulation-process. not inside
> the simulated operating system.

Ah, sorry.

I cannot think of anything which could trigger that, except what you 
suggested (interrupts are in the way), or maybe timing problems.

Sorry,
Dscho