From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I91if-0002lJ-A7 for qemu-devel@nongnu.org; Thu, 12 Jul 2007 12:40:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I91ie-0002l7-Su for qemu-devel@nongnu.org; Thu, 12 Jul 2007 12:40:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I91ie-0002l0-Q9 for qemu-devel@nongnu.org; Thu, 12 Jul 2007 12:40:44 -0400 Received: from il.qumranet.com ([82.166.9.18]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I91id-0008OE-VH for qemu-devel@nongnu.org; Thu, 12 Jul 2007 12:40:44 -0400 Message-ID: <46965993.5050701@qumranet.com> Date: Thu, 12 Jul 2007 19:40:51 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Crash: When Host HDD is full References: <7fac565a0707110819k635d398fl273d8d5a0afd2d3f@mail.gmail.com> <200707120807.41162.mikeonthecomputer@gmail.com> <4696530A.2010000@qumranet.com> <20070712162236.GE20008@redhat.com> In-Reply-To: <20070712162236.GE20008@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" , qemu-devel@nongnu.org Daniel P. Berrange wrote: > On Thu, Jul 12, 2007 at 07:12:58PM +0300, Avi Kivity wrote: > >> Mike Swanson wrote: >> >>> On Wednesday 11 July 2007 08:19:48 Alexey Eremenko wrote: >>> >>> >>>> Problem 1: >>>> When Host HDD is full, all guests simply crash. Tried with dynamically >>>> growing .VMDK hard disk. >>>> >>>> It shouldn't happen. For example, both VirtualPC and VirtualBox pause >>>> all VMs, and gray their displays when something like that happens. >>>> >>>> >>> IMO, it's a non-issue; you probably shouldn't be letting your filesystems >>> to become full in the first place, much less running VMs on it. >>> >> Well, he shouldn't, but neither should qemu crash or corrupt data. >> > > It should be propagating any IO errors in the host back up to the guest > OS as IDE errors. The guest OS will see these and (in the case of Linux) > take the filesystem offline. There should be no crash or data corruption. > While any outstanding writes will not have been flushed with any reasonable > filesystem it will recover upon reboot, either by fsck, or trivially > recovering the journal & maintaining filesystem integrity. > > Potentially ENOSPC could be handled as a special case by pausing the > guest, but in general I/O errors can be propagated back to guest for > handling (even if the guest merely takes things ofline). > I agree about general I/O errors. However ENOSPC cannot happen for disks and should not be converted into an I/O error. -- error compiling committee.c: too many arguments to function