From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39437) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up1gu-0004bA-4g for qemu-devel@nongnu.org; Tue, 18 Jun 2013 15:35:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Up1gs-000297-Hi for qemu-devel@nongnu.org; Tue, 18 Jun 2013 15:35:44 -0400 Received: from smtp.citrix.com ([66.165.176.89]:11490) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up1gs-00028w-CU for qemu-devel@nongnu.org; Tue, 18 Jun 2013 15:35:42 -0400 Date: Tue, 18 Jun 2013 20:35:29 +0100 From: Stefano Stabellini In-Reply-To: <51C0B119.8070704@redhat.com> Message-ID: References: <1371117054-5694-1-git-send-email-paul.durrant@citrix.com> <1371145442.6955.64.camel@zakaz.uk.xensource.com> <51BA0943.7050705@redhat.com> <9AAE0902D5BC7E449B7C8E4E778ABCD00394C5@LONPEX01CL01.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD0039637@LONPEX01CL01.citrite.net> <51BB1FB4.1030006@redhat.com> <9AAE0902D5BC7E449B7C8E4E778ABCD0039B3F@LONPEX01CL01.citrite.net> <51BB2F73.70902@redhat.com> <9AAE0902D5BC7E449B7C8E4E778ABCD0039C9E@LONPEX01CL01.citrite.net> <51C0B119.8070704@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] Remove hardcoded xen-platform device initialization List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Ian Campbell , Paul Durrant , "xen-devel@lists.xen.org" , "qemu-devel@nongnu.org" , Stefano Stabellini On Tue, 18 Jun 2013, Paolo Bonzini wrote: > Il 18/06/2013 20:56, Stefano Stabellini ha scritto: > >> > > >> > Ok. I guess we can have the ability to override the machine type in the VM config, so you could still kick off an older qemu with a newer libxl - but it sounds like the auto-discovery idea is a no-go then. > > xenfv-2.0 is a bad idea, like Paolo wrote, it should be possible to just > > use -M pc for HVM guests and retain -M xenpv for pv guests. > > > > However it seems to me that we also need a way in libxl to find out > > whether QEMU is new enough for us to be able to use -M pc. > > We can't just assume that users will be able to figure out the magic > > rune they need to write in the VM config file to solve their VM crash at > > boot problem. > > > > We could spawn an instance of QEMU just to figure out the QEMU version > > but we certainly cannot do that every time we start a new VM. > > Once we figure out the QEMU version the first time we could write it to > > xenstore so that the next time we don't have to go through the same > > process again. > > Can you just assume that 4.4 requires QEMU 1.6 or newer? I would rather not make that assumption because we cannot control what distro are going to package. I wouldn't want a distro to ship with Xen HVM guests broken because they choose the wrong QEMU version. Of course we could put that in the release notes, but there are lots of distros out there and I am pretty sure that at least one of them is not going to read them.