From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: hdegoede@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] cross version compatibility and qemu version
Date: Sun, 4 Aug 2013 13:20:34 +0300 [thread overview]
Message-ID: <20130804102034.GA31756@redhat.com> (raw)
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.
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?
We also probably want to fix this in -stable versions.
next reply other threads:[~2013-08-04 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 10:20 Michael S. Tsirkin [this message]
2013-08-04 10:25 ` [Qemu-devel] cross version compatibility and qemu version Peter Maydell
2013-08-04 12:09 ` Andreas Färber
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=20130804102034.GA31756@redhat.com \
--to=mst@redhat.com \
--cc=hdegoede@redhat.com \
--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).