On 11/24/14 15:58, Adam Litke wrote:
> On 21/11/14 23:03 -0700, Eric Blake wrote:
...
>> The problem is that once we have a domain with more than one , and
>> where one or all disks have more than one , then how
>> should virDomainListBlockStats represent that?
>>
>> One idea I have is to just ex
On 21/11/14 23:03 -0700, Eric Blake wrote:
Based on Dan's recommendation [1], I'm looking at enhancing
virDomainListBlockStats to report the allocation numbers of a backing
file during a virDomainBlockCommit operation. Getting the information
from qemu is not difficult, but the question is how s
On 11/22/14 07:03, Eric Blake wrote:
> Based on Dan's recommendation [1], I'm looking at enhancing
> virDomainListBlockStats to report the allocation numbers of a backing
> file during a virDomainBlockCommit operation. Getting the information
> from qemu is not difficult, but the question is how s
Based on Dan's recommendation [1], I'm looking at enhancing
virDomainListBlockStats to report the allocation numbers of a backing
file during a virDomainBlockCommit operation. Getting the information
from qemu is not difficult, but the question is how should it be
represented to the end user. See
