From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [Qemu-devel] [PATCH] rev5: support colon in filenames Date: Thu, 16 Jul 2009 17:12:01 +0200 Message-ID: <4A5F4341.2070409@redhat.com> References: <1245862739.6278.7.camel@localhost> <1246063310.6278.115.camel@localhost> <1246511321.6429.31.camel@localhost> <4A4C754D.10109@redhat.com> <4A4CAD86.9020607@us.ibm.com> <4A4CB39F.5070506@redhat.com> <1247041831.6297.12.camel@localhost> <1247644283.14246.3.camel@localhost> <4A5DF252.50408@us.ibm.com> <4A5DF875.2020808@us.ibm.com> <87y6qoaglc.fsf@pike.pond.sub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Blue Swirl , Kevin Wolf , kvm-devel , linuxram@us.ibm.com, qemu-devel@nongnu.org, Jan Kiszka , Paul Brook To: Markus Armbruster Return-path: Received: from mx2.redhat.com ([66.187.237.31]:36669 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756536AbZGPPOO (ORCPT ); Thu, 16 Jul 2009 11:14:14 -0400 In-Reply-To: <87y6qoaglc.fsf@pike.pond.sub.org> Sender: kvm-owner@vger.kernel.org List-ID: On 07/16/09 15:43, Markus Armbruster wrote: > Why "-drive.ID.NAME VALUE", "-net.ID.NAME VALUE" and so forth, i.e. one > option per object with parameters? Assuming the ID name space is flat, > a single option suffices. What about "-set ID.NAME=VALUE"? Hmm, I think we will have multiple namespaces. At least one for guest devices and one for host backends. Probably also different namespaces for different kinds of host backends (disk / net / char / ...). -set or maybe -drive-set id.name= should be easier to handle then -drive.id.name with qemu's command line option parser. cheers, Gerd