From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37977) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMwKb-0006tr-MU for qemu-devel@nongnu.org; Thu, 28 Aug 2014 05:49:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XMwKS-0002j6-MB for qemu-devel@nongnu.org; Thu, 28 Aug 2014 05:49:25 -0400 Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:60985) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMwKS-0002ir-Ep for qemu-devel@nongnu.org; Thu, 28 Aug 2014 05:49:16 -0400 Received: by mail-wi0-f169.google.com with SMTP id n3so300727wiv.4 for ; Thu, 28 Aug 2014 02:49:14 -0700 (PDT) Date: Thu, 28 Aug 2014 10:49:11 +0100 From: Stefan Hajnoczi Message-ID: <20140828094911.GA26741@stefanha-thinkpad.redhat.com> References: <1407488118-11245-1-git-send-email-david.marchand@6wind.com> <1407488118-11245-3-git-send-email-david.marchand@6wind.com> <20140808150202.GD13382@stefanha-thinkpad.redhat.com> <53FC2D9C.8020804@6wind.com> <53FC69BE.7010100@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <53FC69BE.7010100@redhat.com> Subject: Re: [Qemu-devel] [PATCH v3 2/2] docs: update ivshmem device spec List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, claudio.fontana@huawei.com, armbru@redhat.com, David Marchand , jani.kokkonen@huawei.com, cam@cs.ualberta.ca --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 26, 2014 at 01:04:30PM +0200, Paolo Bonzini wrote: > Il 26/08/2014 08:47, David Marchand ha scritto: > >=20 > > Using a version message supposes we want to keep ivshmem-server and QEMU > > separated (for example, in two distribution packages) while we can avoid > > this, so why would we do so ? > >=20 > > If we want the ivshmem-server to come with QEMU, then both are supposed > > to be aligned on your system. >=20 > What about upgrading QEMU and ivshmem-server while you have existing > guests? You cannot restart ivshmem-server, and the new QEMU would have > to talk to the old ivshmem-server. Version negotiation also helps avoid confusion if someone combines ivshmem-server and QEMU from different origins (e.g. built from source and distro packaged). It's a safeguard to prevent hard-to-diagnose failures when the system is misconfigured. Stefan --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJT/vsXAAoJEJykq7OBq3PIRtMH/iBkIqLnTLKr7no5X8/zokYV 1uoCJyl4W1BBGgvIFqaT/X9WtAk+3+fi9KU7PqL2LiDD8XC4m29BEie6h0iPzui0 mG1EEQIfkOfByvGfMntlISW69bsM4Mrms8+HRLG7CWkaCf2JLTaelD9ZuPm/XOCs gvLspGRRVa00tE1UYY+n/VVNANz0ucx/P6jlVJ8anVhQnQn13GSg2/Zblf78YjvN xQbIz3al51Q+nlExYjhFCXuSnmxMjibwwYbArdnYR4l2+b7CDYHm6WqdIsumi10f o/nBt2iiWyP0qrdaoVfMwdqo7cMeiMlmRQfJZVJK3CssilXIGOBYpw1b8HaT1P0= =VsW5 -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--