From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58506) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dpZum-00072e-20 for qemu-devel@nongnu.org; Wed, 06 Sep 2017 08:58:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dpZui-0000qd-6j for qemu-devel@nongnu.org; Wed, 06 Sep 2017 08:58:44 -0400 Date: Wed, 6 Sep 2017 14:58:25 +0200 From: Kevin Wolf Message-ID: <20170906125825.GH3753@dhcp-200-186.str.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 0/3] Live block optional disable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jeff Cody Cc: qemu-devel@nongnu.org, ehabkost@redhat.com, qemu-block@nongnu.org, dgilbert@redhat.com, peterx@redhat.com, mrezanin@redhat.com Am 30.08.2017 um 19:01 hat Jeff Cody geschrieben: > This series adds a configurable option to disable live block operations. > > The default is that live block operations are 'enabled'. Let me play dumb: Who would ever want to disable these? Is there a legitimate reason to do this except artificially making qemu less capable than it really is? Kevin