Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35867 - [virtinst] NUMA not detected
Attached to Project:
Community Packages
Opened by Andrej Podzimek (andrej) - Thursday, 20 June 2013, 20:43 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 26 July 2013, 15:31 GMT
Opened by Andrej Podzimek (andrej) - Thursday, 20 June 2013, 20:43 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 26 July 2013, 15:31 GMT
|
DetailsDescription:
When trying to generate the guest's CPU pinning based on host's NUMA configuration in virt-manager, I get this error message: Capabilities only show <= 1 cell. Not NUMA capable This only happens on an ArchLinux physical host, Fedora and Ubuntu physical hosts don't have this bug on the same hardware. Additional info: * package version(s) virt-manager 0.9.5-1 virtinst 0.600.4-1 numactl 2.0.8-2 * config and/or log files etc. # numactl --hardware available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 node 0 size: 24576 MB node 0 free: 9528 MB node 1 cpus: 1 3 5 7 9 11 13 15 node 1 size: 24563 MB node 1 free: 11201 MB node distances: node 0 1 0: 10 20 1: 20 10 Steps to reproduce: Try to auto-generate CPU pinning in virt-manager on a NUMA physical host. |
This task depends upon
Comment by Sergej Pupykin (sergej) -
Friday, 21 June 2013, 10:50 GMT
should be fixed in libvirt-1.0.6-2.
Comment by Andrej Podzimek (andrej) -
Sunday, 23 June 2013, 12:09 GMT
- Field changed: Percent Complete (100% → 0%)
With libvirt 1.0.6-3, I'm getting "Could not find any usable NUMA cell/cpu combinations.". So this time there's a different issue.
Comment by Sergej Pupykin (sergej) -
Wednesday, 03 July 2013, 10:58 GMT
latest virt-manager replaces virtinst, could you please try it? (will come to repo soon)