[libvirt] [PATCH 0/8] Fix cgroups regresion when default cpuset is specified
John Ferlan
jferlan at redhat.com
Fri Mar 27 16:19:45 UTC 2015
On 03/27/2015 11:13 AM, Eric Blake wrote:
> On 03/27/2015 07:12 AM, Peter Krempa wrote:
>> Since commit a39f69d2b libvirt would fail to start a VM if the default cpu set
>> was specified and individual vcpus were pinned to cpus outside of that cpuset.
>>
>> Peter Krempa (8):
>> qemu: cgroup: Store auto cpuset instead of re-creating it on demand
>> qemu: cgroup: Refactor setup for IOThread cgroups
>> qemu: cgroup: Properly set up vcpu pinning
>> qemu: cgroup: Use priv->autoCpuset instead of using
>> qemuPrepareCpumap()
>> qemu: cgroup: Rename qemuSetupCgroupEmulatorPin to
>> qemuSetupCgroupCpusetCpus
>> qemu: cgroup: Kill qemuSetupCgroupIOThreadsPin()
>> qemu: cgroup: Kill qemuSetupCgroupVcpuPin()
>> qemu: Copy bitmap in a sane way
>
> Not a review of this series, but related to cgroups so also needs fixing:
>
> Running ./autobuild.sh currently fails on the mingw-cross-compilation
> section, due to:
>
> CCLD libvirt.la
> Cannot export virCgroupDetectMountsFromFile: symbol not defined
> Cannot export virCgroupGetCpusetMemoryMigrate: symbol not defined
> Cannot export virCgroupSetCpusetMemoryMigrate: symbol not defined
>
>
>
I "think" the following will resolve that (but I have no empirical
evidence since I don't have a cross-mingw environment to test this on)...
http://www.redhat.com/archives/libvir-list/2015-March/msg01480.html
John
More information about the libvir-list
mailing list