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, 30 Aug 2013 12:08:05 -0400 Message-ID: <20130830160805.GB25009@phenom.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> <20130802120409.GF24540@konrad-lan.dumpdata.com> <20130820145607.GD16567@cab.unipd.it> <20130823185430.GA14338@phenom.dumpdata.com> <20130827210302.GA877@cab.unipd.it> <20130828154501.GC16368@phenom.dumpdata.com> <20130828164450.GG6321@cab.unipd.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20130828164450.GG6321@cab.unipd.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: Ian Campbell , Xen Developers List-Id: xen-devel@lists.xenproject.org On Wed, Aug 28, 2013 at 06:44:50PM +0200, Andrea Brugiolo wrote: > On Wed, Aug 28, 2013 at 11:45:01AM -0400, Konrad Rzeszutek Wilk wrote: > > On Tue, Aug 27, 2013 at 11:03:02PM +0200, Andrea Brugiolo wrote: > > > On Fri, Aug 23, 2013 at 02:54:30PM -0400, Konrad Rzeszutek Wilk wrote: > > > > > > Awaiting your response with the usage of 'xl'. > > > > > > > > > > Now I am using `xl' and the > > > > > > > > > > e820_host = 1 > > > > > > > > > > option in the domU configuration but I get the same result as before > > > > > and no device attached: > > > > > > > > And this is with Xen 4.2 I presume? > > > > > > No, Xen 4.1 (Debian 4.1.4-3+deb7u1 Xen hypervisor and libs) > > > > OK, Xen 4.1 did not have the code to handle the e820_host so hence the > > reason for this not working :-(. > > > > You will need to upgrade to Xen 4.2 at least. I don't know how that > > is done under Debian. > > Argh... the 4.2 hypervisor is still in the Debian unstable release so > I am not sure about how I could put that into production without > relevant breaks. > > As a last resort, would you suggest tecniques other than pciback to > delegate a device to a guest in Xen 4.1? The other option is to limit the amount of memory the guest will use from 16GB to say 2GB. That would work as well. > > Thank you very much for your attention and the time you dedicated do > this issue Sure thing. Sadly the patch did not make Xen 4.1 hence the need to use a more modern version of Xen stack. > > Andrea