On 11/04/2013 07:18 PM, Kevin Wolf wrote:
Am 04.11.2013 um 08:24 hat Fam Zheng geschrieben:
On Tue 29 Oct 2013 08:12:38 PM CST, Kevin Wolf wrote:
Am 29.10.2013 um 13:02 hat Paolo Bonzini geschrieben:
Il 29/10/2013 12:35, Kevin Wolf ha scritto:
The block layer generally keeps the size of an
Am 04.11.2013 um 08:24 hat Fam Zheng geschrieben:
>
>
> On Tue 29 Oct 2013 08:12:38 PM CST, Kevin Wolf wrote:
> >Am 29.10.2013 um 13:02 hat Paolo Bonzini geschrieben:
> >>Il 29/10/2013 12:35, Kevin Wolf ha scritto:
> >>>The block layer generally keeps the size of an image cached in
> >>>bs->total
On Tue 29 Oct 2013 08:12:38 PM CST, Kevin Wolf wrote:
Am 29.10.2013 um 13:02 hat Paolo Bonzini geschrieben:
Il 29/10/2013 12:35, Kevin Wolf ha scritto:
The block layer generally keeps the size of an image cached in
bs->total_sectors so that it doesn't have to perform expensive
operations to g
Am 29.10.2013 um 13:02 hat Paolo Bonzini geschrieben:
> Il 29/10/2013 12:35, Kevin Wolf ha scritto:
> > The block layer generally keeps the size of an image cached in
> > bs->total_sectors so that it doesn't have to perform expensive
> > operations to get the size whenever it needs it.
> >
> > Thi
Il 29/10/2013 12:35, Kevin Wolf ha scritto:
> The block layer generally keeps the size of an image cached in
> bs->total_sectors so that it doesn't have to perform expensive
> operations to get the size whenever it needs it.
>
> This doesn't work however when using a backend that can change its si
The block layer generally keeps the size of an image cached in
bs->total_sectors so that it doesn't have to perform expensive
operations to get the size whenever it needs it.
This doesn't work however when using a backend that can change its size
without qemu being aware of it, i.e. passthrough of
