qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/4] Introduce global config (v3)


From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH 0/4] Introduce global config (v3)
Date: Sun, 24 Jan 2010 09:25:56 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Lightning/1.0pre Thunderbird/3.0

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-<TARGET_NAME>.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






reply via email to

[Prev in Thread] Current Thread [Next in Thread]