From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH 1/2] PV hugepages - Xen patch Date: Thu, 09 Oct 2008 17:05:38 -0700 Message-ID: <48EE9C52.4020704@goop.org> References: <48ED3950.1080605@goop.org> <20081009083848.GB26108@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20081009083848.GB26108@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: "Daniel P. Berrange" Cc: xen-devel@lists.xensource.com, Ian Pratt , Dave McCracken , Keir Fraser List-Id: xen-devel@lists.xenproject.org Daniel P. Berrange wrote: > Or you could just take the view this is a pre-migration capability check, > and that admin (or mgmt app) must ensure sufficient free hugepages on the > destination before attempting migration. If this isn't satisfied then > XenD can just fail / abort the migration op and leave it running on original > host. > And do something to prevent new hugepages from being allocated during the dirty logging phase? J