From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51063) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpZQo-0004WK-S5 for qemu-devel@nongnu.org; Tue, 05 May 2015 05:46:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YpZQk-0003ek-VD for qemu-devel@nongnu.org; Tue, 05 May 2015 05:46:26 -0400 Date: Tue, 5 May 2015 10:46:06 +0100 From: Stefan Hajnoczi Message-ID: <20150505094606.GB29818@stefanha-thinkpad.redhat.com> References: <1426791801-9042-1-git-send-email-mreitz@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wzJLGUyc3ArbnUjN" Content-Disposition: inline In-Reply-To: <1426791801-9042-1-git-send-email-mreitz@redhat.com> Subject: Re: [Qemu-devel] [PATCH v2 0/3] block: Warn about usage of growing formats over non-growable protocols List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: Kevin Wolf , Stefan Hajnoczi , qemu-devel@nongnu.org, qemu-block@nongnu.org --wzJLGUyc3ArbnUjN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 19, 2015 at 03:03:18PM -0400, Max Reitz wrote: > Some image formats (e.g. qcow2) require the underlying file to grow on > write accesses, but this is in fact not supported by all protocols (e.g. > nbd does not). If such a format requiring file growth is used > non-read-only over a protocol which does not support this, a warning > should be issued. >=20 > This warning is issued for example whenever one tries to export a qcow2 > image over nbd-server and use the export from qemu. The warning implies that the user should switch to read-only or a different protocol, but this configuration is perfectly normal. For example, oVirt uses qcow2 on LVM volumes. Introducing a warning for a normal QEMU invocation is a bit weird. What is the point of this series? Were users confused that they hit ENOSPC? Stefan --wzJLGUyc3ArbnUjN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVSJFeAAoJEJykq7OBq3PI/B8IAMSZd6CoENBoQ4nGkECyMUCP fv1xhtBR+qmqCi/NmdEcmUeM8ge+qxcCVs1x4eu6FsGvem5Vcd9xixHRM6x5zJPI NL2OUPO2TWV+46gyRfrCMGDfoU2KN8sOw1y0S+faLg1QE51f8mLlSJoak16jxV35 0dPmtuQniG/RQxRZEW5tRg40cZV82d6ikM8Uy9dITxHCvive0eS2jWoCLHIDsRaA afeKbnSpi1qA2FFhK3vPD9l2QmiW7j+9YMgJ0H5LYQ5o5N0Gfh2qHx5PcVJlHYfo TjAvZR4vxhBzPpyUIq9tVdsMmJiPx+o8UjRpdbKTvYjcX83YTfGizqyC+Z8KkG4= =0XtT -----END PGP SIGNATURE----- --wzJLGUyc3ArbnUjN--