3GB memory restriction for pv domU with NIC PCI Passthrough

3GB memory restriction for pv domU with NIC PCI Passthrough

[topperxin]

[-- Attachment #1.1: Type: text/plain, Size: 441 bytes --]

Hi list
     These I'm checking PCI Passthrough to PV domU, and I found when the memory larger than 3G, the PCI passthrough will not successfully. I got some information from the google. Some guys said it's a bug, and has already fixed, Why do I still meet this problem? What should I do?


please refer to :


http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1673
Bug 1673 - 3GB memory restriction for pv domU with PCI


Thanks a lot.

[-- Attachment #1.2: Type: text/html, Size: 708 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: 3GB memory restriction for pv domU with NIC PCI Passthrough

[George Dunlap]

On Tue, Apr 15, 2014 at 9:15 AM, topperxin <topperxin@126.com> wrote:
> Hi list
>      These I'm checking PCI Passthrough to PV domU, and I found when the
> memory larger than 3G, the PCI passthrough will not successfully. I got some
> information from the google. Some guys said it's a bug, and has already
> fixed, Why do I still meet this problem? What should I do?
>
> please refer to :
>
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1673
> Bug 1673 - 3GB memory restriction for pv domU with PCI

You need to do a proper bug report, or how can we know if it's even
the same bug?

 -George

Re: 3GB memory restriction for pv domU with NIC PCI Passthrough

[Konrad Rzeszutek Wilk]

On Tue, Apr 15, 2014 at 04:15:53PM +0800, topperxin wrote:
> Hi list
>      These I'm checking PCI Passthrough to PV domU, and I found when the memory larger than 3G, the PCI passthrough will not successfully. I got some information from the google. Some guys said it's a bug, and has already fixed, Why do I still meet this problem? What should I do?

It should be fixed. Did you find any issues when doing PCI passthrough?

> 
> 
> please refer to :
> 
> 
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1673
> Bug 1673 - 3GB memory restriction for pv domU with PCI
> 
> 
> Thanks a lot.

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

Re: 3GB memory restriction for pv domU with NIC PCI Passthrough

[topperxin]

[-- Attachment #1.1: Type: text/plain, Size: 2989 bytes --]



Hi
  I met the same problem that you have already talked about.
  I assigned 28 vCPUs , 4G memory, Intel 82599 VF to a PV domU VM.
  I can not see the intel 82599 VF from lspci.
 The xen version is 4.1.5
 please refer to the dmesg:
=========================================================
[    3.540273] pcifront pci-0: PCI host bridge to bus 0000:00
[    3.540280] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    3.540285] pci_bus 0000:00: root bus resource [mem 0x00000000-0x3fffffffffff]
[    3.540291] pci_bus 0000:00: root bus resource [bus 00-ff]
[    3.541343] pci 0000:00:00.3: [8086:10ed] type 00 class 0x020000
[    3.542147] pci 0000:00:00.3: reg 0x10: [mem 0xdf904000-0xdf907fff 64bit]
[    3.542816] pci 0000:00:00.3: reg 0x1c: [mem 0xdfa04000-0xdfa07fff 64bit]
[    3.545523] pcifront pci-0: New device on 0000:00:00.3 found.
[    3.551644] pcifront pci-0: claiming resource 0000:00:00.3/0
[    3.551657] pci 0000:00:00.3: address space collision: [mem 0xdf904000-0xdf907fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
[    3.551662] pcifront pci-0: Could not claim resource 0000:00:00.3/0! Device offline. Try using e820_host=1 in the guest config.
[    3.551682] pcifront pci-0: claiming resource 0000:00:00.3/3
[    3.551688] pci 0000:00:00.3: address space collision: [mem 0xdfa04000-0xdfa07fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
[    3.551692] pcifront pci-0: Could not claim resource 0000:00:00.3/3! Device offline. Try using e820_host=1 in the guest config.
[    3.743814] microcode: CPU19 sig=0x206d7, pf=0x1, revision=0x70a
[    3.750305] microcode: CPU20 sig=0x206d7, pf=0x1, revision=0x70a
[    3.756410] microcode: CPU21 sig=0x206d7, pf=0x1, revision=0x70a
[    3.761506] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.7.12-k
[    3.761513] ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
[    3.761650] ixgbevf 0000:00:00.3: device not available (can't reserve [mem 0xdf904000-0xdf907fff 64bit])
[    3.761684] ixgbevf: probe of 0000:00:00.3 failed with error -22
=========================================================


At 2014-04-15 18:43:30,"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
>On Tue, Apr 15, 2014 at 04:15:53PM +0800, topperxin wrote:
>> Hi list
>>      These I'm checking PCI Passthrough to PV domU, and I found when the memory larger than 3G, the PCI passthrough will not successfully. I got some information from the google. Some guys said it's a bug, and has already fixed, Why do I still meet this problem? What should I do?
>
>It should be fixed. Did you find any issues when doing PCI passthrough?
>
>> 
>> 
>> please refer to :
>> 
>> 
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1673
>> Bug 1673 - 3GB memory restriction for pv domU with PCI
>> 
>> 
>> Thanks a lot.
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 3978 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: 3GB memory restriction for pv domU with NIC PCI Passthrough

[Konrad Rzeszutek Wilk]

On Wed, Apr 16, 2014 at 10:55:18AM +0800, topperxin wrote:
> 
> 
> Hi
>   I met the same problem that you have already talked about.
>   I assigned 28 vCPUs , 4G memory, Intel 82599 VF to a PV domU VM.
>   I can not see the intel 82599 VF from lspci.
>  The xen version is 4.1.5

Right. This is fixed in Xen 4.3. Please try that.

>  please refer to the dmesg:
> =========================================================
> [    3.540273] pcifront pci-0: PCI host bridge to bus 0000:00
> [    3.540280] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
> [    3.540285] pci_bus 0000:00: root bus resource [mem 0x00000000-0x3fffffffffff]
> [    3.540291] pci_bus 0000:00: root bus resource [bus 00-ff]
> [    3.541343] pci 0000:00:00.3: [8086:10ed] type 00 class 0x020000
> [    3.542147] pci 0000:00:00.3: reg 0x10: [mem 0xdf904000-0xdf907fff 64bit]
> [    3.542816] pci 0000:00:00.3: reg 0x1c: [mem 0xdfa04000-0xdfa07fff 64bit]
> [    3.545523] pcifront pci-0: New device on 0000:00:00.3 found.
> [    3.551644] pcifront pci-0: claiming resource 0000:00:00.3/0
> [    3.551657] pci 0000:00:00.3: address space collision: [mem 0xdf904000-0xdf907fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
> [    3.551662] pcifront pci-0: Could not claim resource 0000:00:00.3/0! Device offline. Try using e820_host=1 in the guest config.
> [    3.551682] pcifront pci-0: claiming resource 0000:00:00.3/3
> [    3.551688] pci 0000:00:00.3: address space collision: [mem 0xdfa04000-0xdfa07fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
> [    3.551692] pcifront pci-0: Could not claim resource 0000:00:00.3/3! Device offline. Try using e820_host=1 in the guest config.
> [    3.743814] microcode: CPU19 sig=0x206d7, pf=0x1, revision=0x70a
> [    3.750305] microcode: CPU20 sig=0x206d7, pf=0x1, revision=0x70a
> [    3.756410] microcode: CPU21 sig=0x206d7, pf=0x1, revision=0x70a
> [    3.761506] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.7.12-k
> [    3.761513] ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
> [    3.761650] ixgbevf 0000:00:00.3: device not available (can't reserve [mem 0xdf904000-0xdf907fff 64bit])
> [    3.761684] ixgbevf: probe of 0000:00:00.3 failed with error -22
> =========================================================
> 
> 
> At 2014-04-15 18:43:30,"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
> >On Tue, Apr 15, 2014 at 04:15:53PM +0800, topperxin wrote:
> >> Hi list
> >>      These I'm checking PCI Passthrough to PV domU, and I found when the memory larger than 3G, the PCI passthrough will not successfully. I got some information from the google. Some guys said it's a bug, and has already fixed, Why do I still meet this problem? What should I do?
> >
> >It should be fixed. Did you find any issues when doing PCI passthrough?
> >
> >> 
> >> 
> >> please refer to :
> >> 
> >> 
> >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1673
> >> Bug 1673 - 3GB memory restriction for pv domU with PCI
> >> 
> >> 
> >> Thanks a lot.
> >
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xen.org
> >> http://lists.xen.org/xen-devel
> >

Re: 3GB memory restriction for pv domU with NIC PCI Passthrough

[topperxin]

[-- Attachment #1.1: Type: text/plain, Size: 3520 bytes --]

Hi 
     We have to use 4.1.5 now.
     Is it possible to fix in xen 4.1.5? 
     If possible, could you please tell me how to modify in xen 4.1.5?
     Thanks a lot.  
At 2014-04-16 21:08:14,"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
>On Wed, Apr 16, 2014 at 10:55:18AM +0800, topperxin wrote:
>> 
>> 
>> Hi
>>   I met the same problem that you have already talked about.
>>   I assigned 28 vCPUs , 4G memory, Intel 82599 VF to a PV domU VM.
>>   I can not see the intel 82599 VF from lspci.
>>  The xen version is 4.1.5
>
>Right. This is fixed in Xen 4.3. Please try that.
>
>>  please refer to the dmesg:
>> =========================================================
>> [    3.540273] pcifront pci-0: PCI host bridge to bus 0000:00
>> [    3.540280] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
>> [    3.540285] pci_bus 0000:00: root bus resource [mem 0x00000000-0x3fffffffffff]
>> [    3.540291] pci_bus 0000:00: root bus resource [bus 00-ff]
>> [    3.541343] pci 0000:00:00.3: [8086:10ed] type 00 class 0x020000
>> [    3.542147] pci 0000:00:00.3: reg 0x10: [mem 0xdf904000-0xdf907fff 64bit]
>> [    3.542816] pci 0000:00:00.3: reg 0x1c: [mem 0xdfa04000-0xdfa07fff 64bit]
>> [    3.545523] pcifront pci-0: New device on 0000:00:00.3 found.
>> [    3.551644] pcifront pci-0: claiming resource 0000:00:00.3/0
>> [    3.551657] pci 0000:00:00.3: address space collision: [mem 0xdf904000-0xdf907fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
>> [    3.551662] pcifront pci-0: Could not claim resource 0000:00:00.3/0! Device offline. Try using e820_host=1 in the guest config.
>> [    3.551682] pcifront pci-0: claiming resource 0000:00:00.3/3
>> [    3.551688] pci 0000:00:00.3: address space collision: [mem 0xdfa04000-0xdfa07fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
>> [    3.551692] pcifront pci-0: Could not claim resource 0000:00:00.3/3! Device offline. Try using e820_host=1 in the guest config.
>> [    3.743814] microcode: CPU19 sig=0x206d7, pf=0x1, revision=0x70a
>> [    3.750305] microcode: CPU20 sig=0x206d7, pf=0x1, revision=0x70a
>> [    3.756410] microcode: CPU21 sig=0x206d7, pf=0x1, revision=0x70a
>> [    3.761506] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.7.12-k
>> [    3.761513] ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
>> [    3.761650] ixgbevf 0000:00:00.3: device not available (can't reserve [mem 0xdf904000-0xdf907fff 64bit])
>> [    3.761684] ixgbevf: probe of 0000:00:00.3 failed with error -22
>> =========================================================
>> 
>> 
>> At 2014-04-15 18:43:30,"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
>> >On Tue, Apr 15, 2014 at 04:15:53PM +0800, topperxin wrote:
>> >> Hi list
>> >>      These I'm checking PCI Passthrough to PV domU, and I found when the memory larger than 3G, the PCI passthrough will not successfully. I got some information from the google. Some guys said it's a bug, and has already fixed, Why do I still meet this problem? What should I do?
>> >
>> >It should be fixed. Did you find any issues when doing PCI passthrough?
>> >
>> >> 
>> >> 
>> >> please refer to :
>> >> 
>> >> 
>> >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1673
>> >> Bug 1673 - 3GB memory restriction for pv domU with PCI
>> >> 
>> >> 
>> >> Thanks a lot.
>> >
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> >

[-- Attachment #1.2: Type: text/html, Size: 6853 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: 3GB memory restriction for pv domU with NIC PCI Passthrough

[Konrad Rzeszutek Wilk]

On Thu, Apr 17, 2014 at 10:11:09AM +0800, topperxin wrote:
> Hi 
>      We have to use 4.1.5 now.
>      Is it possible to fix in xen 4.1.5? 

No.
>      If possible, could you please tell me how to modify in xen 4.1.5?

You would need to backport the 'e820_hole' patches. I did post on the xen-devel
at some point an version of them: see

http://lists.xen.org/archives/html/xen-devel/2012-03/msg02134.html
and
http://lists.xen.org/archives/html/xen-devel/2012-03/msg02131.html

>      Thanks a lot.  
> At 2014-04-16 21:08:14,"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
> >On Wed, Apr 16, 2014 at 10:55:18AM +0800, topperxin wrote:
> >> 
> >> 
> >> Hi
> >>   I met the same problem that you have already talked about.
> >>   I assigned 28 vCPUs , 4G memory, Intel 82599 VF to a PV domU VM.
> >>   I can not see the intel 82599 VF from lspci.
> >>  The xen version is 4.1.5
> >
> >Right. This is fixed in Xen 4.3. Please try that.
> >
> >>  please refer to the dmesg:
> >> =========================================================
> >> [    3.540273] pcifront pci-0: PCI host bridge to bus 0000:00
> >> [    3.540280] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
> >> [    3.540285] pci_bus 0000:00: root bus resource [mem 0x00000000-0x3fffffffffff]
> >> [    3.540291] pci_bus 0000:00: root bus resource [bus 00-ff]
> >> [    3.541343] pci 0000:00:00.3: [8086:10ed] type 00 class 0x020000
> >> [    3.542147] pci 0000:00:00.3: reg 0x10: [mem 0xdf904000-0xdf907fff 64bit]
> >> [    3.542816] pci 0000:00:00.3: reg 0x1c: [mem 0xdfa04000-0xdfa07fff 64bit]
> >> [    3.545523] pcifront pci-0: New device on 0000:00:00.3 found.
> >> [    3.551644] pcifront pci-0: claiming resource 0000:00:00.3/0
> >> [    3.551657] pci 0000:00:00.3: address space collision: [mem 0xdf904000-0xdf907fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
> >> [    3.551662] pcifront pci-0: Could not claim resource 0000:00:00.3/0! Device offline. Try using e820_host=1 in the guest config.
> >> [    3.551682] pcifront pci-0: claiming resource 0000:00:00.3/3
> >> [    3.551688] pci 0000:00:00.3: address space collision: [mem 0xdfa04000-0xdfa07fff 64bit] conflicts with System RAM [mem 0x00100000-0xffffffff]
> >> [    3.551692] pcifront pci-0: Could not claim resource 0000:00:00.3/3! Device offline. Try using e820_host=1 in the guest config.
> >> [    3.743814] microcode: CPU19 sig=0x206d7, pf=0x1, revision=0x70a
> >> [    3.750305] microcode: CPU20 sig=0x206d7, pf=0x1, revision=0x70a
> >> [    3.756410] microcode: CPU21 sig=0x206d7, pf=0x1, revision=0x70a
> >> [    3.761506] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.7.12-k
> >> [    3.761513] ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
> >> [    3.761650] ixgbevf 0000:00:00.3: device not available (can't reserve [mem 0xdf904000-0xdf907fff 64bit])
> >> [    3.761684] ixgbevf: probe of 0000:00:00.3 failed with error -22
> >> =========================================================
> >> 
> >> 
> >> At 2014-04-15 18:43:30,"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
> >> >On Tue, Apr 15, 2014 at 04:15:53PM +0800, topperxin wrote:
> >> >> Hi list
> >> >>      These I'm checking PCI Passthrough to PV domU, and I found when the memory larger than 3G, the PCI passthrough will not successfully. I got some information from the google. Some guys said it's a bug, and has already fixed, Why do I still meet this problem? What should I do?
> >> >
> >> >It should be fixed. Did you find any issues when doing PCI passthrough?
> >> >
> >> >> 
> >> >> 
> >> >> please refer to :
> >> >> 
> >> >> 
> >> >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1673
> >> >> Bug 1673 - 3GB memory restriction for pv domU with PCI
> >> >> 
> >> >> 
> >> >> Thanks a lot.
> >> >
> >> >> _______________________________________________
> >> >> Xen-devel mailing list
> >> >> Xen-devel@lists.xen.org
> >> >> http://lists.xen.org/xen-devel
> >> >