On Wed, Jul 27, 2016 at 08:50:42AM +0200, Erik Skultety wrote:
Since commit c4bdff19, the path to the configuration file has been constructed
in the following manner:
- if no config filename was passed to virConfLoadConfigPath, libvirt.conf was
used as default
- otherwise the filename was concate
On 27/07/16 11:21, Andrea Bolognani wrote:
> On Wed, 2016-07-27 at 08:50 +0200, Erik Skultety wrote:
>> Since commit c4bdff19, the path to the configuration file has been
>> constructed
>> in the following manner:
>> - if no config filename was passed to virConfLoadConfigPath, libvirt.conf
>> w
On Wed, 2016-07-27 at 08:50 +0200, Erik Skultety wrote:
> Since commit c4bdff19, the path to the configuration file has been constructed
> in the following manner:
> - if no config filename was passed to virConfLoadConfigPath, libvirt.conf was
> used as default
> - otherwise the filename was con
Since commit c4bdff19, the path to the configuration file has been constructed
in the following manner:
- if no config filename was passed to virConfLoadConfigPath, libvirt.conf was
used as default
- otherwise the filename was concatenated with
"/libvirt/libvirt%s%s.conf" which in admin case re