> On 16 Nov 2018, at 11:22, Tomasz Barański <[email protected]> wrote:
> 
> Hello, wise people!
> 
> As a part of BZ1615830[1] I want to add information about qemu guest agent
> to engine's DB. I have some trouble figuring out some details.
> 
> 1. VDSM seems to be using QGA, but it does not report any information about
>   it. Am I right?

what do you mean to report any information? There are guest agent reported 
fields which are either there or not
One such field is appsList which returns the agent itself (well, it’s fake for 
qemu-ga, but the agent string is always put there)

>   I only found a mention about it in `xml` field in JSON returned by
>   `VM.getInfo` (and `Host.getVMFullList`): a `virtio` channel as
>   documented in libvirt.

virtio channels are always there for both agents

> 
> 2. How does the engine puts data into `vm_dynamic` table? I can't find any
>   usage for `InsertVmDynamic` procedure.

app_list

> 
> 3. Also, it's not clear to me how (whether?) the engine consumes output of
>   VM.getInfo/Host.getVMFullList.

it does not in 4.2+ clusters, see FullListAdapter::getVmFullList()

HTH,
michal

> Any pointers to relevant code appreciated.
> 
> 
> Tomo
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1615830
> _______________________________________________
> Devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/[email protected]/message/DASVREOUEKMRWGQ4IBGHFSBTF2XMBF3C/
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/JQCUX6W5PUZCA4K3SV5H2XZOIXRZK3SW/

Reply via email to