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

[Andrea Brugiolo <andrea@xxxxxxxxxxxx>]

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)

> 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).

Please find attached:

 - domU configuration -> efferax.cfg
 - output of `xl -vvvv create' (dom0 console) -> xl-vvvv-create.log
 - output of `dmesg' in domU -> domU-dmesg.log

Recall:

 - dom0 is Debian GNU/Linux 7.1 with Debian kernel 3.2.0-4-amd64
   (3.2.46-1) and Xen 4.1.4-3+deb7u1 machinery

 - domU is Debian GNU/Linux 6.0.7 with the same kernel 
 
> > > [  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?

Right, as you can see it in the domU config:

    maxmem      = '16384'
    memory      = '2048'

but the 'conflict' is still there even if I set maxmem to 2048 or
leave it unset.

> 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?

I tried both and got the same result.

This last time I set the pci=[...] option in the domU config (just for
the scsi controller, as you can see).

Thank you very much for your attention, I really don't have a clue!

Andrea

Attachment: efferax.cfg
Description: Text document

Attachment: xl-vvvv-create.log
Description: Text document

Attachment: domU-dmesg.log
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel