From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen pciback not working: "address space collision: [mem ...] conflicts with System RAM [mem ...]" Date: Fri, 2 Aug 2013 08:44:09 -0400 Message-ID: <20130802124409.GL24540@konrad-lan.dumpdata.com> References: <20130726103211.GB7269@cab.unipd.it> <1375088523.14896.23.camel@kazak.uk.xensource.com> <20130729175516.GP5848@phenom.dumpdata.com> <20130802090735.GE12938@cab.unipd.it> <4078b6f7c87fda2adaa7b11f7d10ab6c@mail.shatteredsilicon.net> <20130802120559.GG24540@konrad-lan.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Gordan Bobic Cc: Xen Developers , Ian Campbell , Andrea Brugiolo List-Id: xen-devel@lists.xenproject.org > >>>>The RAM region is pretty much all of the memory. This looks like > >>>>the 'e820_hole' > >>>>parameter is not being used? (It only works for xl btw). > >> > >>Where is the e820_hole option documented and what does it do? > > > >It should be in the manpage (man xl.cfg). Here is a copy-n-paste: > > e820_host=BOOLEAN .. snip.. > > Ah, so this was a typo above. s/e820_hole/e820_host/ Yes. It is suppose to be 'e820_host=1'. Thank you for helping me realize my mistake.