Jamie Lokier wrote:
Anthony Liguori wrote:
block-qcow2: keep highest allocated byte (Uri Lublin)
We want to know the highest written offset for qcow2 images.
This gives a pretty good (and easy to calculate) estimation to how
much more allocation can be done for the block device.
It
Avi Kivity wrote:
Anthony Liguori wrote:
Scanning the file at startup is slow. We need to find a better way.
Any quick ideas? Seems like this is broken by design.
I agree.
Unless we can find a quick fix, I'm going to revert this in the
stable tree.
We could cache the value in some u
Anthony Liguori wrote:
> > block-qcow2: keep highest allocated byte (Uri Lublin)
> > We want to know the highest written offset for qcow2 images.
> > This gives a pretty good (and easy to calculate) estimation to how
> > much more allocation can be done for the block device.
> > It ca
Anthony Liguori wrote:
Scanning the file at startup is slow. We need to find a better way.
Any quick ideas? Seems like this is broken by design.
I agree.
Unless we can find a quick fix, I'm going to revert this in the stable
tree.
We could cache the value in some unused area. Set it
