[libvirt] [PATCH] util: Force reading of meta data to get encryption capacity value

Michal Privoznik mprivozn at redhat.com
Fri Jun 23 09:23:31 UTC 2017

On 06/15/2017 09:31 PM, John Ferlan wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1371892
> As it turns out the volume create, build, and refresh path was not peeking
> at the meta data, so immediately after a create operation the value displayed
> for capacity was still incorrect. However, if a pool refresh was done the
> correct value was fetched as a result of a meta data peek.
> The reason is it seems historically if the file type is RAW then peeking
> at the file just took the physical value for the capacity. However, since
> we know if it's an encrypted file, then peeking at the meta data will be
> required in order to get a true capacity value.
> So check for encryption in the source and if present, use the meta data
> in order to fill in the capacity value and set the payload_offset.
> Signed-off-by: John Ferlan <jferlan at redhat.com>
> ---
>  src/util/virstoragefile.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)



More information about the libvir-list mailing list