search for: virdomainruncommand

...est 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 --  Andrea Bolognan...

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. Kind regards patrick On , Michal Privoznik wrote: > On 08.08.2016 09:33, Patrick PICHON wrote: >> Hello, >> >> >> All my VMs are using LVs created on the host

...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. Michal