[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen pciback not working: "address space collision: [mem ...] conflicts with System RAM [mem ...]"

On Fri, 2 Aug 2013 11:07:35 +0200, Andrea Brugiolo <andrea@xxxxxxxxxxxx> wrote:
On Mon, Jul 29, 2013 at 01:55:16PM -0400, Konrad Rzeszutek Wilk wrote:
On Mon, Jul 29, 2013 at 10:02:03AM +0100, Ian Campbell wrote:
> On Fri, 2013-07-26 at 12:32 +0200, Andrea Brugiolo wrote:
> > Good Morning
> >
> > I cannot do pciback anymore for both my second scsi controller and my > > second network card: when I try to pass the device to the domU I get
> > this error in system logs:
> >
> > ... address space collision: [mem ...] conflicts with System RAM [mem ...]
> By eliding the actually addresses you've omitted something which I think
> might be interesting:
> [mem 0xf9e00000-0xf9e1ffff 64bit] conflicts with System RAM [mem 0x00100000-0x4007fffff]
> Note that there is not any actual overlap in those two sets of addresses...

I think it is:
mem 0xf9e00000-0xf9e1ffff
mem 0x00100000-0x4007fffff

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?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.