From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Xen pciback not working: "address space collision:
 [mem ...] conflicts with System RAM [mem ...]"
Date: Fri, 23 Aug 2013 14:54:30 -0400
Message-ID: <20130823185430.GA14338@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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <20130820145607.GD16567@cab.unipd.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>, Xen Developers <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

> > 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? What does your guest config look like and
if you do 'xl -vvvv create ' can you attach the output?

Also can you provide the full guest bootup log (xl console output).

> 
> > [  152.098815] pcifront pci-0: Installing PCI frontend
> > [  152.099141] pcifront pci-0: Creating PCI Frontend Bus 0000:09
> > [  152.100134] pci 0000:09:08.0: [1000:0030] type 0 class 0x000100
> > [  152.100666] pci 0000:09:08.0: reg 10: [io  0x5000-0x50ff]
> > [  152.101055] pci 0000:09:08.0: reg 14: [mem 0xf9e00000-0xf9e1ffff 64bit]
> > [  152.101465] pci 0000:09:08.0: reg 1c: [mem 0xf9e20000-0xf9e3ffff 64bit]
> > [  152.103112] pci 0000:09:08.0: supports D1 D2
> > [  152.109991] pcifront pci-0: claiming resource 0000:09:08.0/0
> > [  152.110002] pcifront pci-0: claiming resource 0000:09:08.0/1
> > [  152.110010] pci 0000:09:08.0: address space collision: [mem 0xf9e00000-0xf9e1ffff 64bit] conflicts with System RAM [mem 0x00100000-0x4007fffff]

So a 16GB guest right?

> > [  152.110023] pcifront pci-0: Could not claim resource 0000:09:08.0/1! Device offline. Try using e820_host=1 in the guest config.
> > [  152.110032] pcifront pci-0: claiming resource 0000:09:08.0/3
> > [  152.110040] pci 0000:09:08.0: address space collision: [mem 0xf9e20000-0xf9e3ffff 64bit] conflicts with System RAM [mem 0x00100000-0x4007fffff]
> > [  152.110051] pcifront pci-0: Could not claim resource 0000:09:08.0/3! Device offline. Try using e820_host=1 in the guest config.
> > [  152.110359] mptspi 0000:09:08.0: device not available (can't reserve [mem 0xf9e00000-0xf9e1ffff 64bit])
> > [  152.110370] mptbase: ioc0: ERROR - pci_enable_device_mem() failed
> 
> Is there anything else I should provide (again)?

I am still puzzled why the 'e820_host=1' option did not trigger for you.
Did you also have 'pci=[blabla]' in your guest config or did you do
it via pci hotplugging?

Thanks.