From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZ4Lk-0005Wn-Bm for qemu-devel@nongnu.org; Sun, 24 Jan 2010 10:26:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZ4Lf-0005Sq-Oc for qemu-devel@nongnu.org; Sun, 24 Jan 2010 10:26:03 -0500 Received: from [199.232.76.173] (port=45911 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZ4Lf-0005Sh-Dl for qemu-devel@nongnu.org; Sun, 24 Jan 2010 10:25:59 -0500 Received: from mail-yw0-f176.google.com ([209.85.211.176]:56650) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZ4Lf-0005gt-FD for qemu-devel@nongnu.org; Sun, 24 Jan 2010 10:25:59 -0500 Received: by ywh6 with SMTP id 6so2461022ywh.4 for ; Sun, 24 Jan 2010 07:25:58 -0800 (PST) Message-ID: <4B5C6684.3060403@codemonkey.ws> Date: Sun, 24 Jan 2010 09:25:56 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/4] Introduce global config (v3) References: <1264342938-7363-1-git-send-email-aliguori@us.ibm.com> <4B5C6186.8090806@redhat.com> In-Reply-To: <4B5C6186.8090806@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: John Cooper , Paolo Bonzini , Anthony Liguori , qemu-devel@nongnu.org, Gerd Hoffman On 01/24/2010 09:04 AM, Avi Kivity wrote: > On 01/24/2010 04:22 PM, Anthony Liguori wrote: >> This series introduces global config files stored in /etc/qemu. >> There is both >> a common config (qemu.conf) and a per-target config >> (target-.conf). >> >> I've removed the default device bits from the series as it requires >> some more >> thought on how to best integrate it. That makes this series rather >> simple. > > btw, what does the corresponding patch to our imaginary management > tool author guide read? Do we recommend -nodefconfig or not? I think > we should, since otherwise qemu behaviour can be completely unexpected > by the management tool. It depends. I think there are two classes of management tools. The first class, like libvirt, completely hides the details of QEMU from the user. For libvirt, it should definitely use -nodefconfig because a user should not be encouraged to tweak bits without libvirt knowing about it. A second class of management tools would work with QEMU and basically extend what we currently expose. IOW, guest's would be represented through our native config file, full access would be provided to monitor/QMP commands. For this class of tools, a user should be encouraged to use the default configuration files to make global changes to a particular node. Regards, Anthony Liguori