From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1I90Gg-0001fo-Dw
	for qemu-devel@nongnu.org; Thu, 12 Jul 2007 11:07:46 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1I90Ge-0001f4-Rk
	for qemu-devel@nongnu.org; Thu, 12 Jul 2007 11:07:46 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1I90Ge-0001ex-Lt
	for qemu-devel@nongnu.org; Thu, 12 Jul 2007 11:07:44 -0400
Received: from nz-out-0506.google.com ([64.233.162.237])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mikeonthecomputer@gmail.com>) id 1I90Ge-0001aG-AK
	for qemu-devel@nongnu.org; Thu, 12 Jul 2007 11:07:44 -0400
Received: by nz-out-0506.google.com with SMTP id f1so368092nzc
	for <qemu-devel@nongnu.org>; Thu, 12 Jul 2007 08:07:43 -0700 (PDT)
From: Mike Swanson <mikeonthecomputer@gmail.com>
Subject: Re: [Qemu-devel] Crash: When Host HDD is full
Date: Thu, 12 Jul 2007 08:07:40 -0700
References: <7fac565a0707110819k635d398fl273d8d5a0afd2d3f@mail.gmail.com>
In-Reply-To: <7fac565a0707110819k635d398fl273d8d5a0afd2d3f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200707120807.41162.mikeonthecomputer@gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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. Besides, most 
filesystems reserve some space for the superuser, now unless there's a 
cross-platform way to figure out just how much space that is, you'd still be 
getting errors despite having 5~10% of the filesystem technically free.