From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ht2BM-0006lq-FE
	for qemu-devel@nongnu.org; Tue, 29 May 2007 09:56:16 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ht2BL-0006le-4X
	for qemu-devel@nongnu.org; Tue, 29 May 2007 09:56:15 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ht2BK-0006lb-Tt
	for qemu-devel@nongnu.org; Tue, 29 May 2007 09:56:14 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <clemens.kol@gmx.at>) id 1Ht2BK-0006yK-AJ
	for qemu-devel@nongnu.org; Tue, 29 May 2007 09:56:14 -0400
Message-ID: <465C30F5.40307@gmx.at>
Date: Tue, 29 May 2007 15:56:05 +0200
From: Clemens Kolbitsch <clemens.kol@gmx.at>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Accepting socket connections in qemu (not the
	client... the emulator)
References: <20070528160302.540gmx1@mx058.gmx.net> <465C219F.2040206@gmx.at>
	<465C2C2F.5000600@gmx.at>
	<Pine.LNX.4.64.0705291444080.4648@racer.site>
In-Reply-To: <Pine.LNX.4.64.0705291444080.4648@racer.site>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org

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.