Thanks, Jakub !

Are you sure sire ASPM is needed ?

For me,
lspci -nvvvs 04:00.0| grep ASPM | grep Enabled
returns nothing.
And:
lspci -nvvvs 04:00.0 | grep ASPM | grep -i disabled
returns:
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

04:00.0  is the BDF I use.

And I am using 04:00.0 for SRIOV with Qemu.

I don't think I have "Enable ASPM in BIOS".

Are you sure ASPM is needed ? or maybe this is for very specific
configurations ?

Also dmesg shows that ASPM is disabled:

$dmesg | grep  ASPM
[    0.114703] ACPI FADT declares the system doesn't support PCIe
ASPM, so disable it
[    0.135999] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM
ClockPM Segments MSI]
[    0.136237] acpi PNP0A08:00: FADT indicates ASPM is unsupported,
using BIOS configuration
[    0.222695] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM
ClockPM Segments MSI]
[    0.223101] acpi PNP0A08:01: FADT indicates ASPM is unsupported,
using BIOS configuration
[    0.226173] acpi PNP0A08:02: _OSC: OS supports [ExtendedConfig ASPM
ClockPM Segments MSI]
[    0.226573] acpi PNP0A08:02: FADT indicates ASPM is unsupported,
using BIOS configuration


Regards,
Kevin

On Sun, Feb 19, 2017 at 2:10 PM, Jakub Pavlik <[email protected]> wrote:
> Yes,
>
> do not forget to check following parameters on compute nodes:
>
> Enable VT-d in BIOS
>
> check:
> # dmesg | grep -e DMAR -e IOMMU
>
>
> Enable ASPM in BIOS
>
> check:
> # lspci -vvv | grep ASPM | grep Enabled
>
>
>
> nova.conf on controller
>
> scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter,
> DiskFilter,
>
>                                    ComputeFilter, ComputeCapabilitiesFilter,
> ImagePropertiesFilter,
>
>                                    ServerGroupAntiAffinityFilter,
> ServerGroupAffinityFilter, PciPassthroughFilter
>
> scheduler_available_filters = nova.scheduler.filters.all_filters
>
> scheduler_available_filters =
> nova.scheduler.filters.pci_passthrough_filter.PciPassthroughFilter
>
>
>
> nova.conf on compute node
> pci_passthrough_whitelist = { "devname": "eth1", "physical_network":
> "physnet1"}
>
> On Mon, Feb 13, 2017 at 11:24 AM, Kevin Wilson <[email protected]> wrote:
>>
>> Hello, OpenContrail experts,
>>
>> I found the following in the "Contrail Feature Guide",
>>
>> https://www.juniper.net/techpubs/en_US/contrail3.0/information-products/pathway-pages/contrail-feature-guide-pwp.pdf
>>
>> It says:
>>
>> ...........
>> Overview: Configuring SR-IOV
>> ...
>> Configuring SR-IOV Features Without env.sriov in testbed.py
>> ...
>> In the Nova compute config file, configure a Nova Scheduler filter
>> based on the new
>> PCI configuration, as in the following example:
>> /etc/nova/nova.conf
>> [default]
>> scheduler_default_filters = PciPassthroughFilter
>> scheduler_available_filters = nova.scheduler.filters.all_filters
>> scheduler_available_filters =
>> nova.scheduler.filters.pci_passthrough_filter.PciPassthroughFilter
>> 6. Restart Nova Scheduler.
>> service nova-scheduler restart
>>
>> It seems to me that there is an error here: it says to make the
>> changes in the Nova compute config file and
>> then restart nova-scheduler. However, there is no nova-scheduler
>> service in the Nova compute node
>> at all:
>> service nova-scheduler status
>> nova-scheduler: unrecognized service
>>
>> So it seems to me that this change, of adding
>> scheduler_default_filters/scheduler_default_filters/... settings,
>> should be done in /etc/nova/nova.conf of the *control* node and *not*
>> /etc/nova/nova.conf of the compute node.
>>
>> Does this sounds reasonable ?
>>
>> Kevin
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
>
>
>
>
> --
> Jakub Pavlik
> +420 602 177 027
> [email protected]

_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Reply via email to