From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: dom0 linux 3.6.0-rc4, crash due to ballooning althoug dom0_mem=X, max:X set Date: Tue, 4 Sep 2012 12:33:47 -0400 Message-ID: <20120904163347.GH23361@phenom.dumpdata.com> References: <1136369816.20120904183757@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1136369816.20120904183757@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sander Eikelenboom Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, Sep 04, 2012 at 06:37:57PM +0200, Sander Eikelenboom wrote: > Hi Konrad, > > This seems to happen only on a intel machine i'm trying to setup as a development machine (haven't seen it on my amd). > It boots fine, i have dom0_mem=1024M,max:1024M set, the machine has 2G of mem. Is this only with Xen 4.2? As, does Xen 4.1 work? > > Dom0 and guest kernel are 3.6.0-rc4 with config: If you back out: f393387d160211f60398d58463a7e65 Author: Konrad Rzeszutek Wilk Date: Fri Aug 17 16:43:28 2012 -0400 xen/setup: Fix one-off error when adding for-balloon PFNs to the P2M. Do you see this bug? (Either with Xen 4.1 or Xen 4.2)? > [*] Xen memory balloon driver > [*] Scrub pages before returning them to system > > From http://wiki.xen.org/wiki/Do%EF%BB%BFm0_Memory_%E2%80%94_Where_It_Has_Not_Gone , I thought this should be okay > > But when trying to start a PV guest with 512MB mem, the machine (dom0) crashes with the stacktrace below (complete serial-log.txt attached). > > From the: > "mapping kernel into physical memory > about to get started..." > > I would almost say it's trying to reload dom0 ? > > > [ 897.161119] device vif1.0 entered promiscuous mode > mapping kernel into physical memory > about to get started... > [ 897.696619] xen_bridge: port 1(vif1.0) entered forwarding state > [ 897.716219] xen_bridge: port 1(vif1.0) entered forwarding state > [ 898.129465] ------------[ cut here ]------------ > [ 898.132209] kernel BUG at drivers/xen/balloon.c:359! > [ 898.132209] invalid opcode: 0000 [#1] PREEMPT SMP