Bug 1209891
| Summary: | changing the pinning with virsh setvcpupin does not work | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | libvirt | Assignee: | Peter Krempa <pkrempa> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.6 | CC: | dyuan, honzhang, jdenemar, jherrman, jsuchane, lhuang, mtessun, mzhan, pkrempa, pmanzell, pm-eus, rbalakri, rhodain, tscherf |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.10.2-46.el6_6.6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when the default CPU mask was specified while using Non-Uniform Memory Access (NUMA) pinning, virtual CPUs (vCPUs) could not be pinned to physical CPUs that were not contained in the default node mask. With this update, the control groups (cgroups) code correctly attaches only vCPU threads instead of the entire domain group, and using NUMA pinning with the default cpuset subsystem now works as expected.
|
Story Points: | --- |
| Clone Of: | 1198096 | Environment: | |
| Last Closed: | 2015-04-29 10:10:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1198096 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-04-08 12:27:46 UTC
The patch for this bug introduces a memory leak. Verify this bug with libvirt-0.10.2-46.el6_6.6.x86_64 : Steps: 1. # valgrind --leak-check=full libvirtd ==8417== Memcheck, a memory error detector ==8417== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==8417== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==8417== Command: libvirtd ==8417== 2. open another terminal and prepare a vm: # virsh dumpxml r6 ... <vcpu placement='static' cpuset='0-3'>4</vcpu> ... 3. start the vm: # virsh start r6 Domain r6 started 4. check cgroup settings: # cgget -g cpuset /libvirt/qemu/r6/vcpu3 |grep .cpus cpuset.cpus: 0-3 # cgget -g cpuset /libvirt/qemu/r6/vcpu2 |grep .cpus cpuset.cpus: 0-3 # cgget -g cpuset /libvirt/qemu/r6/vcpu1 |grep .cpus cpuset.cpus: 0-3 # cgget -g cpuset /libvirt/qemu/r6 |grep .cpus cpuset.cpus: 0-7 # cgget -g cpuset /libvirt/qemu/r6/emulator |grep .cpus cpuset.cpus: 0-3 5. change vcpupin: # virsh vcpupin r6 0 4-7 # virsh vcpupin r6 1 4-7 # virsh vcpupin r6 2 4-7 # virsh vcpupin r6 3 4-7 6. recheck cgroup # cgget -g cpuset /libvirt/qemu/r6/vcpu1 |grep .cpus cpuset.cpus: 4-7 # cgget -g cpuset /libvirt/qemu/r6/vcpu1 |grep .cpus cpuset.cpus: 4-7 # cgget -g cpuset /libvirt/qemu/r6/vcpu2 |grep .cpus cpuset.cpus: 4-7 # cgget -g cpuset /libvirt/qemu/r6/vcpu3 |grep .cpus cpuset.cpus: 4-7 # cgget -g cpuset /libvirt/qemu/r6/emulator |grep .cpus cpuset.cpus: 0-3 # cgget -g cpuset /libvirt/qemu/r6 |grep .cpus cpuset.cpus: 0-7 7. check valgrind no memory leak around this issue. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0916.html |