On Tue, Mar 31, 2015 at 16:14:53 +0200, Ján Tomko wrote:
On Fri, Mar 27, 2015 at 02:12:04PM +0100, 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
On Fri, Mar 27, 2015 at 02:12:04PM +0100, 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
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
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
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
