On 08.08.2016 13:23, Andrea Bolognani wrote:
On Mon, 2016-08-08 at 10:37 +0200, Michal Privoznik wrote:
> On 08.08.2016 10:23, Patrick PICHON wrote:
>>
>> hello Michal,
>>
>> That was my worries as well, and I think that your advice is probably
>> the right one. Or even, I'm might request an enhancement to the collect
>> libvirt plugin to report also FS information.
>
> What I'd like to see is libvirt's ability to spawn commands inside
> guest. But it is not that simple. I mean, the hardest part is to design
> public libvirt API. For instance, we'd have to deal with both blocking &
> non-blocking (i.e. long-running) commands; then we would need to give
> users possibility to read command's output (possibly asynchronously).
>
> With this, you'd just: virDomainRunCommand(dom, 'df', '-h',
NULL); or
> something and you'd be good.
Not as straightforward as you'd like, but if you use QEMU you
can already achieve something similar via qemu-guest-agent.
https://www.redhat.com/archives/libvir-list/2016-August/msg00339.html
This is exactly what I had in mind when writing those lines above. It is
not very convenient for user I'd say. Anyway, it shows that we should
start discussing the design for our virDomainCommand* API - users would
benefit from it.
Michal