From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nc51h-0006G6-AS for qemu-devel@nongnu.org; Mon, 01 Feb 2010 17:45:49 -0500 Received: from [199.232.76.173] (port=57898 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nc51h-0006Fp-0i for qemu-devel@nongnu.org; Mon, 01 Feb 2010 17:45:49 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nc51f-0004ZF-MT for qemu-devel@nongnu.org; Mon, 01 Feb 2010 17:45:48 -0500 Received: from bhuna.collabora.co.uk ([93.93.128.226]:35460) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Nc51f-0004Z1-AW for qemu-devel@nongnu.org; Mon, 01 Feb 2010 17:45:47 -0500 Message-ID: <4B675967.1060503@collabora.co.uk> Date: Mon, 01 Feb 2010 22:44:55 +0000 From: Ian Molton MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 2/5] socket: Add a reconnect option. References: <1265031265-14717-1-git-send-email-ian.molton@collabora.co.uk> <1265031265-14717-2-git-send-email-ian.molton@collabora.co.uk> <1265031265-14717-3-git-send-email-ian.molton@collabora.co.uk> <4B66F267.3040103@codemonkey.ws> In-Reply-To: <4B66F267.3040103@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, Luiz Capitulino Anthony Liguori wrote: > I went back and looked at the last series and found my feedback. I had > suggested that instead of automatically reconnecting, a mechanism should > be added for a user to initiate a reconnect. This sounds useful > Additionally, we should emit events upon disconnect through QMP (now > that we have that functionality). This also. > The main reason I dislike automatic reconnecting is that there is no > correct way to handle the period of time while the VM is disconnected. This is fine for egd protocol, the guest will just run low on entropy in the meantime. Nothing should break. > Auto reconnecting is implementing a policy to handle the failure within > QEMU which is not universally the correct choice. This isn't so bad > except for the fact that you aren't providing the mechanisms for users > to implement other policies which means they're stuck with this > particular policy. Perhaps this feature could be added if needed in future? It seems a bit ambitious to get all this 'right' with no use cases to test against. -Ian