From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aIfHM-0007r4-DK for qemu-devel@nongnu.org; Mon, 11 Jan 2016 11:25:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aIfHL-0003kg-OR for qemu-devel@nongnu.org; Mon, 11 Jan 2016 11:25:12 -0500 Date: Mon, 11 Jan 2016 17:25:03 +0100 From: Kevin Wolf Message-ID: <20160111162503.GH9454@noname.redhat.com> References: <1450802786-20893-1-git-send-email-kwolf@redhat.com> <567AB8FD.2080600@parallels.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 00/10] qcow2: Implement image locking List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vasiliy Tolstov Cc: mreitz@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org, "Denis V. Lunev" Am 23.12.2015 um 16:11 hat Vasiliy Tolstov geschrieben: > 2015-12-23 18:08 GMT+03:00 Denis V. Lunev : > > you should do this by asking running QEMU not by > > qemu-img, which is badly wrong. > > > > Den > > > Ok, if this is possible via qmp/hmp qemu, no problem. It's not only possible, but it's the only correct way. If you use qemu-img, you're bound to corrupt your images sooner or later. This is exactly what this series wants to protect you against. Kevin