WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH] Introduce dom0-min-space configuration option

To: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] Introduce dom0-min-space configuration option
From: Michal Novotny <minovotn@xxxxxxxxxx>
Date: Mon, 26 Jul 2010 14:48:45 +0200
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Mon, 26 Jul 2010 05:50:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C4D7E4B.4060201@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C3B59FE.2060201@xxxxxxxxxx> <19516.43557.723062.885082@xxxxxxxxxxxxxxxxxxxxxxxx> <4C3D9E22.3030302@xxxxxxxxxx> <19526.62789.227136.192517@xxxxxxxxxxxxxxxxxxxxxxxx> <4C47F857.4060606@xxxxxxxxxx> <19529.48273.52500.896247@xxxxxxxxxxxxxxxxxxxxxxxx> <4C4D314A.7080605@xxxxxxxxxx> <4C4D5C7D.3030302@xxxxxxxxxx> <4C4D6529.3090409@xxxxxxxxxx> <4C4D6F06.6090509@xxxxxxxxxx> <4C4D6FBB.6040703@xxxxxxxxxx> <4C4D71FB.6020806@xxxxxxxxxx> <4C4D7601.7010503@xxxxxxxxxx> <4C4D7E4B.4060201@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4
On 07/26/2010 02:23 PM, Paolo Bonzini wrote:
On 07/26/2010 01:48 PM, Michal Novotny wrote:

Well, the root cause is insufficient disk space since without
insufficient disk space issue we won't be running into those issues. In
fact there are 2 points of view on this one:

  1) implement a check for enough disk space (this is what I did)
  2) implement the proper error message saying there is not enough space
to extract it (ENOSPC) - this is what you and Ian suggest

I am not telling any of those options is bad, nevertheless it's based
just on the point of view. So, is option 2 better  and worth
implementing rather than limiting the domain run only to case with
enough space on dom0?

Yes, definitely.

Option 1 wouldn't work, initrd and kernel files have all sort of sizes.

Paolo
Ok, this way it makes sense, however when setting dom0-min-space to 100 (MiB) there's no such kernel/initrd that big but I'm not saying this is bad. Somewhat better error reporting will be the right way to go after all.

Michal

--
Michal Novotny<minovotn@xxxxxxxxxx>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel