From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55566) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yivx2-0004bI-QM for qemu-devel@nongnu.org; Thu, 16 Apr 2015 22:24:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yivwz-00073d-LG for qemu-devel@nongnu.org; Thu, 16 Apr 2015 22:24:16 -0400 Received: from e23smtp05.au.ibm.com ([202.81.31.147]:34973) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yivwz-000732-0p for qemu-devel@nongnu.org; Thu, 16 Apr 2015 22:24:13 -0400 Received: from /spool/local by e23smtp05.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 17 Apr 2015 12:24:01 +1000 Received: from d23relay06.au.ibm.com (d23relay06.au.ibm.com [9.185.63.219]) by d23dlp02.au.ibm.com (Postfix) with ESMTP id 676CA2BB0051 for ; Fri, 17 Apr 2015 12:23:58 +1000 (EST) Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.234.96]) by d23relay06.au.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t3H2Nnw648496876 for ; Fri, 17 Apr 2015 12:23:57 +1000 Received: from d23av01.au.ibm.com (localhost [127.0.0.1]) by d23av01.au.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id t3H2NN93019376 for ; Fri, 17 Apr 2015 12:23:23 +1000 Message-ID: <55306E81.9000604@linux.vnet.ibm.com> Date: Fri, 17 Apr 2015 10:22:57 +0800 From: chenxg MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qcow2 problem: while a qcow2 image run out of disk space the guest paused. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: kwolf@redhat.com, stefanha@redhat.com, mimu@linux.vnet.ibm.com, tubo@cn.ibm.com, borntraeger@de.ibm.com, Holger.Wolf@de.ibm.com, qemu-devel@nongnu.org Hi Kevin, While installing a guest into a qcow2 image if the qcow2 image run out of disk space, the guest will stop work and change state to paused without messages. When we tried to free up disk space in the host and the virsh resume to work. The guest then got I/O errors but later on QEMU also crashed. A guest in paused state is certainly not the best result. Probably good way to react are: - return I/O errors to the guest and the let the guest handle those (Linux file system code might just crash) - allow resume only when disk is free again. What's your opinion?