yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #68760
[Bug 1726356] [NEW] NOVA/CPU Pinning not working with xen
Public bug reported:
Hi,
CPU Pinning or NUMA doesn't seem to work with xen hypervisor:
I used the following guide:
https://docs.openstack.org/nova/latest/contributor/testing/libvirt-numa.html.
Xen version: 4.4.4
Nova 9.1.0
libvirt 1.2.14-12
After creating new instance
```
mysql> select numa_topology from compute_nodes;
+---------------+
| numa_topology |
+---------------+
| NULL |
| NULL |
+---------------+
$ sudo virsh dumpxml instance-00000009
...
<vcpu placement='static'>1</vcpu>
...
No vcpupin written to the instance
But NUMA is available
[root@ca-ostest459 ~]# virsh nodeinfo
CPU model: x86_64
CPU(s): 32
CPU frequency: 2593 MHz
CPU socket(s): 1
Core(s) per socket: 8
Thread(s) per core: 2
NUMA cell(s): 2
Memory size: 134158412 KiB
Regards
** 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/1726356
Title:
NOVA/CPU Pinning not working with xen
Status in OpenStack Compute (nova):
New
Bug description:
Hi,
CPU Pinning or NUMA doesn't seem to work with xen hypervisor:
I used the following guide:
https://docs.openstack.org/nova/latest/contributor/testing/libvirt-numa.html.
Xen version: 4.4.4
Nova 9.1.0
libvirt 1.2.14-12
After creating new instance
```
mysql> select numa_topology from compute_nodes;
+---------------+
| numa_topology |
+---------------+
| NULL |
| NULL |
+---------------+
$ sudo virsh dumpxml instance-00000009
...
<vcpu placement='static'>1</vcpu>
...
No vcpupin written to the instance
But NUMA is available
[root@ca-ostest459 ~]# virsh nodeinfo
CPU model: x86_64
CPU(s): 32
CPU frequency: 2593 MHz
CPU socket(s): 1
Core(s) per socket: 8
Thread(s) per core: 2
NUMA cell(s): 2
Memory size: 134158412 KiB
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1726356/+subscriptions
Follow ups