yahoo-eng-team team mailing list archive

[Satish Patel <satish.txt@xxxxxxxxx>]

Public bug reported:

Folks,

I'm building SR-IOV supported compute node on HP 360g8 hardware and i
have Qlogic interface card, my compute node has 32 core & 32GB memory.

Problem:

when i launch vm-1 (with flavor 16 vCPU core) on openstack it launch
successful on numa0 node and working great. but when i launch vm-2
same flavor it start and then shutdown itself in few second, in-short
i am not able launch instance on numa1 node because my PCIe attach to
numa0node which i can see in lstopo command.

so at present i am going to lose half compute capacity if this is real
problem because i can't use numa1 to launch SR-IOV supported instance.

after google i found this link
https://blueprints.launchpad.net/nova/+spec/share-pci-device-between-numa-nodes

and according this link if i can set
hw:pci_numa_affinity_policy=preferred in flavor it will allow me to
spin up instance across the numa node but somehow its not working and
still i am not able to spin up instance, (it start instance but then
shutdown itself)

Any idea what is wrong here?


--------------


If i remove aggregate_instance_extra_specs:pinned='true', hw:cpu_policy='dedicated', hw:pci_numa_affinity_policy='preferred' from my flavor then it allowing me to spin up machine across NUMA. 

How do i make SR-IOV work with pinning with shared PCI NUAM bus?

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1795920

Title:
  SR-IOV shared PCI numa not working

Status in OpenStack Compute (nova):
  New

Bug description:
  Folks,

  I'm building SR-IOV supported compute node on HP 360g8 hardware and i
  have Qlogic interface card, my compute node has 32 core & 32GB memory.

  Problem:

  when i launch vm-1 (with flavor 16 vCPU core) on openstack it launch
  successful on numa0 node and working great. but when i launch vm-2
  same flavor it start and then shutdown itself in few second, in-short
  i am not able launch instance on numa1 node because my PCIe attach to
  numa0node which i can see in lstopo command.

  so at present i am going to lose half compute capacity if this is real
  problem because i can't use numa1 to launch SR-IOV supported instance.

  after google i found this link
  https://blueprints.launchpad.net/nova/+spec/share-pci-device-between-numa-nodes

  and according this link if i can set
  hw:pci_numa_affinity_policy=preferred in flavor it will allow me to
  spin up instance across the numa node but somehow its not working and
  still i am not able to spin up instance, (it start instance but then
  shutdown itself)

  Any idea what is wrong here?


  
  --------------

  
  If i remove aggregate_instance_extra_specs:pinned='true', hw:cpu_policy='dedicated', hw:pci_numa_affinity_policy='preferred' from my flavor then it allowing me to spin up machine across NUMA. 

  How do i make SR-IOV work with pinning with shared PCI NUAM bus?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1795920/+subscriptions