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

RE: [Xen-devel] Error getting mfn for PCI SR-IOV device?



>>> On 26.05.10 at 11:19, "Fischer, Anna" <anna.fischer@xxxxxx> wrote:
>>  Subject: Re: [Xen-devel] Error getting mfn for PCI SR-IOV device?
>> 
>> >>> On 25.05.10 at 15:58, "Fischer, Anna" <anna.fischer@xxxxxx> wrote:
>> > (XEN) mm.c:859:d0 Error getting mfn 40300 (pfn 5555555555555555) from
>> L1
>> > entry 8000000040300473 for l1e_owner=0, pg_owner=32753
>> >...
>> > entry 800000004037e473 for l1e_owner=0, pg_owner=32753
>> > (XEN) mm.c:859:d0 Error getting mfn 4037f (pfn 5555555555555555) from
>> L1
>> > entry 800000004037f473 for l1e_owner=0, pg_owner=32753
>> >
>> > I boot Xen with 'dom0_mem=max:1024M iommu=0' set in GRUB. The system
>> > supports VT-d, but I am disabling it.
>> 
>> Would seem like the kernel assigns I/O memory space to the device,
>> based on the physical (not machine) memory map it gets (making the
>> assumption that there is RAM at 0x40000000 aka 1Gb). Does the
>> behavior change if you remove the dom0_mem= option?
> 
> Yes, thanks, I was going to post to the list that the problem is solved, and 
> the issue was that the PCI BARs were allocated > 1G while I was only making 
> 1024MB visible to Dom0. Now it works.

But it's a kernel side bug nevertheless...

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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