KR> I think using a libvirt dir is less obvious than using a KR> libvirt-cim named one. However, I think it's silly to have a KR> directory with just one file. Do you anticipate the need for KR> other config files? Well, we don't even need this one, except for libvirt<=0.4.0. Having a config directory all to ourselves for a single config file and only in the legacy support case seems overkill :) KR> I'm not sure if we'll need a way to persist data in the future (we KR> haven't had such a need so far..). Well, we will for some of the processor scheduling stuff, but that should probably be in /var/lib somewhere (although I guess the qemu driver puts its configs in /etc). -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com