Am Mon, 11 Oct 2021 13:25:20 -0600 schrieb Jim Fehlig <jfehlig@suse.com>:
I think it is wrong to use internal libvirt values for internal libxentoollog values. What is gained over the sparse mapping? Are values not covered actually useful in practice? Also, how are the values specified when using the xl tool? A quick peek at the code seems to imply using more 'v' options. E.g. 'xl -vvvv ...'.
Since libvirt has no control about what libxentoollog values the authors use, it should provide a simple way to request a specific loglevel. xl decided to use the number of v's for it.
If such a setting is actually needed, then the proper place would be /etc/libvirt/libxl.conf. And IMO we should avoid creating a new name that could potentially confuse users. If 'xentoollog_level' is the common jargon in xen, we should stick with the same name.
If that is an acceptable approach I will try to prepare a patch. Olaf