From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harper Subject: Re: Fwd: NetBSD xl core-dump not working... Memory fault (core dumped) Date: Tue, 10 Dec 2013 08:21:40 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B66BFFA30@BITCOM1.int.sbss.com.au> References: <52770EED.9090804@gmx.de> <52781C27.2040508@gmail.com> <1383820189.26213.152.camel@kazak.uk.xensource.com> <1383906558.3189.81.camel@kazak.uk.xensource.com> <5281F953.2060101@citrix.com> <1384250453.1883.37.camel@kazak.uk.xensource.com> <5281FE63.2060503@citrix.com> <5283730B.2020900@citrix.com> <529E1F9F.5040501@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <529E1F9F.5040501@gmail.com> Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Mike C." , =?utf-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= , Ian Campbell Cc: "xen-devel@lists.xensource.com" , "port-xen@netbsd.org" List-Id: xen-devel@lists.xenproject.org I've been working with Mike on this today. After he re-applied the patch (something must have gone wrong initially), an ioctl error is repeated constantly instead of SIGSEGV: xc: error: xc_map_foreign_range: ioctl failed (14 = Bad address): Internal error I dumped out some of the variables though, and: nr_memory_map = 1 pfn_start = 0, pfn_end = 1048575 this equates to 4GB of pfn's to be dumped on a vm with mem/maxmem = 256MB... is there code that skips empty pages? If not, that seems to be the explanation for the errors. James