Re: [libvirt PATCH 00/16] expose tainting and deprecations in public API
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 to apps.
On Fri, Jan 22, 2021 at 05:18:20PM +0000, Daniel P. Berrangé wrote:
[...]
> We can use the deprecation info from QMP to add tainting to the
> domain too. This will appear in the pre-VM log file again:
>
> 2021-01-22 12:22:53.492+0000: Domain id=3D2 is tainted: deprecated-configurat=
> ion (machine type 'pc-1.3')
> 2021-01-22 12:22:53.492+0000: Domain id=3D2 is tainted: deprecated-configurat=
> ion (CPU model 'Icelake-Client')
>
> and more usefully in the libvirtd log
>
> 2021-01-22 13:18:09.619+0000: 3299849: warning :
> qemuDomainObjTaintMsg:6208 :
> Domain id=3D3 name=3D'demo' uuid=3Deadf8ef0-bf14-4c5f-9708-4a19bacf9e81
> is tainted: deprecated-configuration (machine type 'pc-1.3')
>
> 2021-01-22 13:18:09.619+0000: 3299849: warning :
> qemuDomainObjTaintMsg:6208 :
> Domain id=3D3 name=3D'demo' uuid=3Deadf8ef0-bf14-4c5f-9708-4a19bacf9e81
> is tainted: deprecated-configuration (CPU model 'Icelake-Client')
>
[...]
--
Eduardo
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|