Re: [libvirt PATCH 00/16] expose tainting and deprecations in public API

2021-02-03 Thread Daniel P . Berrangé
On Mon, Jan 25, 2021 at 11:26:08AM +0100, Ján Tomko wrote: > On a Friday in 2021, Daniel P. Berrangé wrote: > > Libvirt has a notion of "tainting" which we use to mark a guest which > > has some undesirable configuration or behaviour from libvirt's POV. > > This ends up in the libvirtd logs and in

Re: [libvirt PATCH 00/16] expose tainting and deprecations in public API

2021-01-26 Thread Daniel P . Berrangé
On Mon, Jan 25, 2021 at 02:41:06PM -0500, Eduardo Habkost wrote: > Related question: does libvirt generate any kind of structured > log records, or all log examples below are going to be stored in > plain text only? Log files are plain text. The API proposals here are what provide any formal data

Re: [libvirt PATCH 00/16] expose tainting and deprecations in public API

2021-01-25 Thread Eduardo Habkost
Related question: does libvirt generate any kind of structured log records, or all log examples below are going to be stored in plain text only? On Fri, Jan 22, 2021 at 05:18:20PM +, Daniel P. Berrangé wrote: [...] > We can use the deprecation info from QMP to add tainting to the > domain

Re: [libvirt PATCH 00/16] expose tainting and deprecations in public API

2021-01-25 Thread Ján Tomko
On a Friday in 2021, Daniel P. Berrangé wrote: Libvirt has a notion of "tainting" which we use to mark a guest which has some undesirable configuration or behaviour from libvirt's POV. This ends up in the libvirtd logs and in the per-VM log file, but is not exposed to management applications