From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Biweekly VMX status report. Xen: #21438 & Xen0: #a3e7c7... Date: Wed, 2 Jun 2010 10:41:17 +0100 Message-ID: References: <789F9655DD1B8F43B48D77C5D30659731E7ECF2E@shsmsx501.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731E7ECF2E@shsmsx501.ccr.corp.intel.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: "Jiang, Yunhong" , "Xu, Jiajun" , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 02/06/2010 10:24, "Jiang, Yunhong" wrote: > (XEN) Pagetable walk from ffff83022fe1d000: > (XEN) L4[0x106] = 00000000cfc8d027 5555555555555555 > (XEN) L3[0x008] = 00000000cfef9063 5555555555555555 > (XEN) L2[0x17f] = 000000022ff2a063 5555555555555555 > (XEN) L1[0x01d] = 000000022fe1d262 5555555555555555 > > I really can't imagine how this can happen considering the vmx_alloc_vmcs() is > so straight-forward. My test machine is really magic. Not at all. The free-memory pool was getting spiked with guarded (mapped not-present) pages. The later unlucky allocator is the one that then crashes. I've just fixed this as xen-unstable:21504. The bug was a silly typo. Thanks, Keir