From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39718) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d0Wli-0008Jy-DW for qemu-devel@nongnu.org; Tue, 18 Apr 2017 13:18:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d0Wle-00016O-FL for qemu-devel@nongnu.org; Tue, 18 Apr 2017 13:18:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46656) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1d0Wle-00015v-8l for qemu-devel@nongnu.org; Tue, 18 Apr 2017 13:18:18 -0400 References: <3d1c16a1-ec05-0367-e569-64a63b34f2e3@redhat.com> <4a56f716-3528-ddd4-f8c4-f3f6b23c469a@redhat.com> <20170327120148.GC26900@stefanha-x1.localdomain> <20170403141912.GA3539@stefanha-x1.localdomain> <87fuhf9kcz.fsf@dusky.pond.sub.org> <20170418095103.GF21261@stefanha-x1.localdomain> <1492516675.27392.45.camel@redhat.com> From: John Snow Message-ID: <7ae1e13f-b6a0-a735-3952-4e3833e34ad8@redhat.com> Date: Tue, 18 Apr 2017 13:18:14 -0400 MIME-Version: 1.0 In-Reply-To: <1492516675.27392.45.camel@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann , Stefan Hajnoczi Cc: Markus Armbruster , Peter Maydell , Thomas Huth , Jason Wang , QEMU Developers On 04/18/2017 07:57 AM, Gerd Hoffmann wrote: > Hi, > >>> Just like -device is a general way to plug in devices, replacing >>> multiple special ways (-net, -drive, -usb, ...), we could use a general >>> way to configure onboard devices. >> >> I looked at the -device implementation to see if the bus= parameter >> could be used to specify onboard device addresses, but I think you may >> be right that we need a separate command-line argument for onboard >> devices. > > I think so. > > There is -global, which is actually used by libvirt to configure > built-in floppy devices. But as the name suggests it sets properties > globally, i.e. for all instances. Which works in this specific use > case, as there can be only one floppy controller per machine, but I Spec-wise, Can't you have two? > don't think this is something we want build on. > > There is -set, but that works only for devices created via -device, > because it operates on QemuOpts, and we don't have QemuOpts for built-in > devices. > > We probably want something like > -qom-set-property {objpath|alias}.prop=value > > cheers, > Gerd >