From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XYUzK-00019M-4W for qemu-devel@nongnu.org; Mon, 29 Sep 2014 03:03:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XYUzF-00052l-0s for qemu-devel@nongnu.org; Mon, 29 Sep 2014 03:03:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:25994) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XYUzE-00050K-QC for qemu-devel@nongnu.org; Mon, 29 Sep 2014 03:03:08 -0400 From: Markus Armbruster References: <1411414496-46245-1-git-send-email-alex@alex.org.uk> <1411414496-46245-2-git-send-email-alex@alex.org.uk> <20140928153058.GA4994@redhat.com> Date: Mon, 29 Sep 2014 09:02:43 +0200 In-Reply-To: (Alex Bligh's message of "Sun, 28 Sep 2014 21:33:08 +0100") Message-ID: <87fvfavrho.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Bligh Cc: Ryan Harper , Serge Hallyn , "quintela@redhat.com" , Libvirt , Serge Hallyn , "qemu-devel@nongnu.org" , Alexander Graf , "Michael S. Tsirkin" , Cole Robinson , Amit Shah , Bruce Rogers , Andreas =?utf-8?Q?F=C3=A4rber?= , "Serge E. Hallyn" Alex Bligh writes: [...] >>> +/* NB cirrus-vga default value is 8MB anyway, save if we >>> + * monkey patch it to change the default when the qemu-kvm-migration >>> + * machine parameter is selected >>> + */ >>> + >> >> This is too hacky for my taste. >> How about creating a new machine e.g. pc-qemu-kvm-1.0 and in >> pc_early_init_pci_1_0, changing compat_props for pc-1.0 to point to the >> compat_props of pc-qemu-kvm-1.0? > > Hang on a second! v2 of this patch DID use a new virtual machine, > called exactly that. I thought you were objecting to that and > wanting a machine parameter instead! It's far easier with a new > machine type, and I'd far prefer a new machine type. > > If you were just objecting to the fact that pc-1.0 was made to > be an alias of either one or the other at compile time, simply > drop the second patch of the v2 patchset. > > If we have a new machine type, I don't /think/ I need the early_init > thing at all (I may be wrong about that). I also prefer a new machine type. Ideally, the management application understands that there are two incompatibile versions QEMU (upstream and old qemu-kvm), and how to map their machine types to current QEMU's. If that's not practical, then downstream can still alias the machine types around to make things just work in the most important downstream scenarios. The most important upstream scenario is QEMU <-> QEMU, of course.