Re: [PATCH] qemu: Fix qemuDomainGetBlockInfo allocation value setting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/06/2017 10:02 PM, John Ferlan wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1467826
> 
> Commit id 'b9b1aa639' was supposed to add logic to set the allocation
> for sparse files when wr_highest_offset was zero; however, an unconditional
> setting was done just prior. For block devices, this means allocation is
> always returning 0 since 'actual-size' will be zero.
> 
> Remove the unconditional setting and add the note about it being possible
> to still be zero for block devices. As soon as the guest starts writing to
> the volume, the allocation value will then be obtainable from qemu via
> the wr_highest_offset.
> 
> Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
> ---
>  src/qemu/qemu_driver.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

ACK

Michal

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]
  Powered by Linux