From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Qemu-devel] [PATCH v3 2/2] docs: update ivshmem device spec Date: Tue, 26 Aug 2014 13:04:30 +0200 Message-ID: <53FC69BE.7010100@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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, claudio.fontana@huawei.com, armbru@redhat.com, jani.kokkonen@huawei.com, cam@cs.ualberta.ca To: David Marchand , Stefan Hajnoczi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:9024 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755724AbaHZLFQ (ORCPT ); Tue, 26 Aug 2014 07:05:16 -0400 In-Reply-To: <53FC2D9C.8020804@6wind.com> Sender: kvm-owner@vger.kernel.org List-ID: Il 26/08/2014 08:47, David Marchand ha scritto: > > 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 ? > > If we want the ivshmem-server to come with QEMU, then both are supposed > to be aligned on your system. 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. Paolo > If you want to test local modifications, then it means you know what you > are doing and you will call the right ivshmem-server binary with the > right QEMU binary. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44853) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMEZ1-0004Pz-Py for qemu-devel@nongnu.org; Tue, 26 Aug 2014 07:05:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XMEYu-0000f3-BS for qemu-devel@nongnu.org; Tue, 26 Aug 2014 07:05:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52218) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMEYu-0000e2-3O for qemu-devel@nongnu.org; Tue, 26 Aug 2014 07:05:16 -0400 Message-ID: <53FC69BE.7010100@redhat.com> Date: Tue, 26 Aug 2014 13:04:30 +0200 From: Paolo Bonzini MIME-Version: 1.0 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> In-Reply-To: <53FC2D9C.8020804@6wind.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: David Marchand , Stefan Hajnoczi Cc: kvm@vger.kernel.org, claudio.fontana@huawei.com, qemu-devel@nongnu.org, armbru@redhat.com, jani.kokkonen@huawei.com, cam@cs.ualberta.ca Il 26/08/2014 08:47, David Marchand ha scritto: > > 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 ? > > If we want the ivshmem-server to come with QEMU, then both are supposed > to be aligned on your system. 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. Paolo > If you want to test local modifications, then it means you know what you > are doing and you will call the right ivshmem-server binary with the > right QEMU binary.