From: Anthony Liguori <anthony@codemonkey.ws>
To: Ian Molton <ian.molton@collabora.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Socket reconnection.
Date: Mon, 30 Nov 2009 11:18:30 -0600 [thread overview]
Message-ID: <4B13FE66.2080401@codemonkey.ws> (raw)
In-Reply-To: <4B0DCC45.5080308@collabora.co.uk>
Ian Molton wrote:
> Hi folks,
>
> I need my source of data for virtio-rng to be reliable - IOW. if the
> server dies and comes back up, I want qemu to reconnect and suck down
> fresh entropy, rather than hand the rngd process on the guest.
>
> I'm using the chardev 'socket' type to make the connection to the host.
>
> Would a patch adding (optional) auto-reconnect (with a back-off delay)
> to the socket chardev be acceptable ?
>
> If not, I'll have to cook up a thread to handle EGD requests, but that
> seems perverse...
>
Hrm, I'm not sure. What are the circumstances that this connection
would die? What happens while the connection is dead?
Regards,
Anthony Liguori
> -Ian
>
>
>
next prev parent reply other threads:[~2009-11-30 17:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 0:31 [Qemu-devel] Socket reconnection Ian Molton
2009-11-26 9:21 ` Gerd Hoffmann
2009-11-27 9:01 ` Jamie Lokier
2009-12-01 11:55 ` Ian Molton
2009-12-06 14:32 ` Jamie Lokier
2009-12-06 16:33 ` Ian Molton
2009-12-07 2:29 ` Jamie Lokier
2009-12-07 9:29 ` Ian Molton
2009-11-30 17:18 ` Anthony Liguori [this message]
2009-12-01 11:54 ` Ian Molton
2009-12-01 14:38 ` Krumme, Chris
2009-12-01 18:29 ` Ian Molton
2009-12-01 18:54 ` Anthony Liguori
2009-12-02 10:40 ` Ian Molton
2009-12-02 12:04 ` [Qemu-devel] " Jan Kiszka
2009-12-02 19:56 ` [Qemu-devel] " Anthony Liguori
2009-12-02 22:35 ` Krumme, Chris
2009-12-03 10:04 ` Ian Molton
2009-12-03 10:23 ` Kevin Wolf
2009-12-03 14:22 ` Anthony Liguori
2009-12-03 18:37 ` [Qemu-devel] [PATCH]Socket reconnection Ian Molton
2009-12-05 22:03 ` Ian Molton
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=4B13FE66.2080401@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=ian.molton@collabora.co.uk \
--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).