From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51451 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OCY8p-0007Sr-08 for qemu-devel@nongnu.org; Thu, 13 May 2010 09:07:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OCY8n-0001tS-10 for qemu-devel@nongnu.org; Thu, 13 May 2010 09:07:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:26657) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OCY8m-0001tA-Q4 for qemu-devel@nongnu.org; Thu, 13 May 2010 09:07:52 -0400 Message-ID: <4BEBF9A5.3070507@redhat.com> Date: Thu, 13 May 2010 15:07:49 +0200 From: Jes Sorensen MIME-Version: 1.0 References: <1273696161-14332-1-git-send-email-crobinso@redhat.com> <4BEB11DD.20601@redhat.com> <4BEB142F.2000002@redhat.com> <4BEBB9C2.3050302@redhat.com> <4BEBF8D1.7060401@redhat.com> In-Reply-To: <4BEBF8D1.7060401@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] Revive -version 'QEMU PC Emulator...' List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cole Robinson Cc: aliguori@us.ibm.com, clalance@redhat.com, qemu-devel@nongnu.org On 05/13/10 15:04, Cole Robinson wrote: > On 05/13/2010 04:35 AM, Jes Sorensen wrote: >> On 05/12/10 22:48, Cole Robinson wrote: >> I think rather than 1, it would be better to add a patch to libvirt to >> catch both formats. I know Chris Lalancette already cooked up a patch >> for this. Combined with the 2) patch I just posted, and 3) I think that >> should take care of the problems. > > It doesn't solve the problem for existing libvirt installations. It's > not uncommon for users to track just the latest kvm releases without > upgrading libvirt: any future qemu or kvm release will break every > version of libvirt that exists today. Given that unfortunate case, I > still recommend reverting the 'PC' change at least for long enough for a > few fixed libvirt releases to make it into the wild. But that is no different from what we have today. Users who update their qemu and see issues with libvirt can also be asked to update libvirt. I have already had several cases where I needed to do that anyway. I don't like reverting a change like this, just to schedule it to be reapplied again later. Cheers, Jes