From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, hdegoede@redhat.com,
Hannes Reinecke <hare@suse.de>,
pbonzini@redhat.com, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] cross version compatibility and qemu version
Date: Sun, 04 Aug 2013 14:09:48 +0200 [thread overview]
Message-ID: <51FE448C.6070101@suse.de> (raw)
In-Reply-To: <CAFEAcA_3kBTn-_xb1dX36mYP+MRtns1pdQhy4XQMaeS1BEaqSA@mail.gmail.com>
Am 04.08.2013 12:25, schrieb Peter Maydell:
> On 4 August 2013 11:20, Michael S. Tsirkin <mst@redhat.com> wrote:
>> I was looking at cross-version migration issues, in the
>> hope that we can fix most of them for release 1.6.
>> I noticed that we still use QEMU_VERSION in hardware.
>
> We fixed most of these back in 2012, but I guess one or
> two slipped through the net.
>
>> hw/scsi/megasas.c: snprintf(info.package_version, 0x60, "%s-QEMU", QEMU_VERSION);
>> hw/usb/redirect.c:#define VERSION "qemu usb-redir guest " QEMU_VERSION
>>
>> These look like a bug that will break cross version
>> compatibility - I think need to change both instances
>> to qemu_get_version()?
[...]
>> megasas also includes the build date/time of QEMU - this
>> clearly removed any hope to be exactly compatible.
>> I'm not sure what to do with respect to this:
>> let's stop the clock at an arbitrary date?
>> Add property for management to control this as well?
>
> I would go for using an arbitrary (and preferably
> obviously wrong) date, or just dropping the fields
> altogether if the hardware format permits (it probably
> doesn't).
Let's simply CC Hannes and ask him. :)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-08-04 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 10:20 [Qemu-devel] cross version compatibility and qemu version Michael S. Tsirkin
2013-08-04 10:25 ` Peter Maydell
2013-08-04 12:09 ` Andreas Färber [this message]
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=51FE448C.6070101@suse.de \
--to=afaerber@suse.de \
--cc=hare@suse.de \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).