From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH] Introduce dom0-min-space configuration option Date: Fri, 23 Jul 2010 17:00:17 +0100 Message-ID: <19529.48273.52500.896247@mariner.uk.xensource.com> References: <4C3B59FE.2060201@redhat.com> <19516.43557.723062.885082@mariner.uk.xensource.com> <4C3D9E22.3030302@redhat.com> <19526.62789.227136.192517@mariner.uk.xensource.com> <4C47F857.4060606@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C47F857.4060606@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Michal Novotny Cc: "'xen-devel@lists.xensource.com'" , Ian Jackson List-Id: xen-devel@lists.xenproject.org Michal Novotny writes ("Re: [Xen-devel] [PATCH] Introduce dom0-min-space configuration option"): > Well, there's no other way to fix it than to implement a check for > enough space on dom0 for extracting vmlinuz and initrd files from the > image file. If it's partially extracted it's understandable that the > data are not valid input for zStream processing and therefore it runs > into Z_BUF_ERROR (-5) during the process. No, it is not understandable that the system should continue to try to execute a partially-extracted kernel. This needs to be fixed. > Why do you think my patch is entirely wrong? Because you are treating the symptoms but not addressing the cause. Ian.