From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1O5FCz-0002xZ-ET
	for qemu-devel@nongnu.org; Fri, 23 Apr 2010 05:30:01 -0400
Received: from [140.186.70.92] (port=41706 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1O5FCv-0002r8-1I
	for qemu-devel@nongnu.org; Fri, 23 Apr 2010 05:30:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <ian.molton@collabora.co.uk>) id 1O5FCt-000273-2v
	for qemu-devel@nongnu.org; Fri, 23 Apr 2010 05:29:56 -0400
Received: from bhuna.collabora.co.uk ([93.93.128.226]:47358)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <ian.molton@collabora.co.uk>) id 1O5FCs-00026p-U2
	for qemu-devel@nongnu.org; Fri, 23 Apr 2010 05:29:55 -0400
Message-ID: <4BD16845.9090001@collabora.co.uk>
Date: Fri, 23 Apr 2010 10:28:37 +0100
From: Ian Molton <ian.molton@collabora.co.uk>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 2/2] VirtIO RNG
References: <4BB2053C.6000701@collabora.co.uk>	<201004031606.26893.paul@codesourcery.com>	<4BC482A6.4040504@collabora.co.uk>	<201004131632.25820.paul@codesourcery.com>	<4BCDC51F.2030205@collabora.co.uk>	<20100420161302.GA11723@shareable.org>	<4BCE061B.2030506@collabora.co.uk>	<20100420205654.GI11723@shareable.org>	<4BCE1D3B.7000306@collabora.co.uk>
	<4BCEAC99.8000206@redhat.com>
	<20100421094007.GC13114@shareable.org>
	<4BCEF0B9.2050704@collabora.co.uk> <4BCF03D2.5000307@redhat.com>
	<4BD09E3F.7070605@collabora.co.uk> <4BD15A0D.6090801@redhat.com>
In-Reply-To: <4BD15A0D.6090801@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
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: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org

Gerd Hoffmann wrote:
>   Hi,
> 
>> Im not sure I agree there... surely there are other things which would
>> benefit from generic socket reconnection support (virtio-rng cant be the
>> only driver that might want to rely on a reliable source of data via a
>> socket in a server-farm type situation?)
> 
> Usually qemu takes the server part, i.e. for serial ports you usually do
> '-serial telnet::$port,server,nowait', then 'telnet $host $port' to
> connect to your virtual serial line.  When the connection drops, just
> re-run telnet.
>
> In my usage of qemu I didn't came across a use case which needs qemu
> reconnecting yet.

You're comparing apples with oranges :-)

That example is the opposite of whats happening in my case - qemu must
act as a client in order to connect to an EGD daemon. There is not other
choice. I'm sure one could come up with any number of cases where qemu
as a client might want to reconnect to the host.

Seriously, if virtio-rng is the only thing on qemu that acts as a socket
*client* I'd be amazed.

And really, is having the ability to reconnect to a service so terrible?

-Ian