Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] qemu-img: Let "info" warn and go ahead without -U

On Tue, Jan 9, 2018 at 10:11 PM, Eric Blake wrote: > On 01/09/2018 01:58 PM, Ala Hino wrote: > > >>> I know this is debatable but I think the #1 purpose of image locking is > >> to > >>> prevent data corruption; > >> > >> Isn

Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] qemu-img: Let "info" warn and go ahead without -U

On Tue, Jan 9, 2018 at 11:58 AM, Kevin Wolf wrote: > Am 09.01.2018 um 07:24 hat Fam Zheng geschrieben: > > On Mon, 01/08 18:57, Kevin Wolf wrote: > > > I'm not sure if going back to the old behaviour for a while now would > be > > > helpful, you'd just end up with an even more confusing set of qe

Re: [Qemu-devel] [Qemu-block] Question regarding qemuimg check

Thanks for the detailed reply, Stefan. Can we always run qemu-img check with -r leaks option, even if there are no leaks? On Tue, Oct 24, 2017 at 3:06 PM, Stefan Hajnoczi wrote: > On Mon, Oct 23, 2017 at 03:38:40PM +0300, Ala Hino wrote: > > I have a question regarding qemuimg chec

[Qemu-devel] Question regarding qemuimg check

Hi, I have a question regarding qemuimg check. We use qemuimg check in order to get the offset of image. we need the offset to reduce the size of the image to optimal. In BZ 1502488 , we are encountering a use case where a leaked cluster error when executing q

[Qemu-devel] Supporting unsafe create when backing file is not accessible

Hi, We encountered a performance issue when creating a volume for a running VM and we'd like to share the info with you. The root cause of the issue is in our code but we found a workaround that relies on qemu-img create undocumented behavior. During our tests, we found that in order to create a