From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35373) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V5vP2-0005wx-R8 for qemu-devel@nongnu.org; Sun, 04 Aug 2013 06:19:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V5vOw-0002gb-QZ for qemu-devel@nongnu.org; Sun, 04 Aug 2013 06:19:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:12404) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V5vOw-0002gA-J4 for qemu-devel@nongnu.org; Sun, 04 Aug 2013 06:19:02 -0400 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r74AJ0LS020176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 4 Aug 2013 06:19:00 -0400 Date: Sun, 4 Aug 2013 13:20:34 +0300 From: "Michael S. Tsirkin" Message-ID: <20130804102034.GA31756@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] cross version compatibility and qemu version List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: hdegoede@redhat.com, pbonzini@redhat.com 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.