From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
claudio.fontana@huawei.com, armbru@redhat.com,
David Marchand <david.marchand@6wind.com>,
jani.kokkonen@huawei.com, cam@cs.ualberta.ca
Subject: Re: [Qemu-devel] [PATCH v3 2/2] docs: update ivshmem device spec
Date: Thu, 28 Aug 2014 10:49:11 +0100 [thread overview]
Message-ID: <20140828094911.GA26741@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <53FC69BE.7010100@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Tue, Aug 26, 2014 at 01:04:30PM +0200, Paolo Bonzini wrote:
> 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.
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
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-08-28 9:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 8:55 [Qemu-devel] [PATCH v3 0/2] ivshmem: update documentation, add client/server tools David Marchand
2014-08-08 8:55 ` [Qemu-devel] [PATCH v3 1/2] contrib: add ivshmem client and server David Marchand
2014-08-08 14:51 ` Stefan Hajnoczi
2014-08-18 12:09 ` David Marchand
2014-08-10 3:57 ` Gonglei
2014-08-18 12:19 ` David Marchand
2014-08-08 8:55 ` [Qemu-devel] [PATCH v3 2/2] docs: update ivshmem device spec David Marchand
2014-08-08 9:04 ` Claudio Fontana
2014-08-08 9:32 ` David Marchand
2014-08-08 15:02 ` Stefan Hajnoczi
2014-08-26 6:47 ` David Marchand
2014-08-26 11:04 ` Paolo Bonzini
2014-08-28 9:49 ` Stefan Hajnoczi [this message]
2014-09-01 9:52 ` David Marchand
2014-09-09 19:04 ` Eric Blake
2014-08-08 9:30 ` [Qemu-devel] [PATCH v3 0/2] ivshmem: update documentation, add client/server tools Gonglei (Arei)
2014-08-08 9:54 ` David Marchand
2014-08-08 10:26 ` Gonglei (Arei)
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=20140828094911.GA26741@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=cam@cs.ualberta.ca \
--cc=claudio.fontana@huawei.com \
--cc=david.marchand@6wind.com \
--cc=jani.kokkonen@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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).