Description of problem: NUMA support in VDSM is fragile, as it leverages internal and private data from libvirt, and as it does expensive scan of procfs entries. This bug tracks improvement to that code to make it more robust and fast. How reproducible: 100% Steps to Reproduce: 1. run VDSM 2. 3. Actual results: VDSM uses internal data from libvirt: /var/run/libvirt/qemu/$VM_NAME.xml Expected results: VDSM uses public and stable APIs and does that in an efficient manner. Additional info: Most likely, patches to libvirt will be needed.
The most compelling performance issues are been addressed by patches from msivak: https://gerrit.ovirt.org/#/c/36906/ https://gerrit.ovirt.org/#/c/38564/ The pending issue is how to avoid to mess with libvirt internal representation, but for that we need new libvirt APIs.
moving to SLA to let them figure what to ask to libvirt to better support NUMA.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.