On Mon, Sep 29, 2014 at 02:48:34PM +0530, Kashyap Chamarthy wrote:
On Mon, Sep 29, 2014 at 08:17:11AM +0200, Guido Günther wrote:
[. . .]
> An alternative to rebooting is to remove related processes
manually, see:
>
>
http://bugs.debian.org/761521
I don't see x2d<$vmname>.scope under machine.slice (mostly as the
guests are all off, but I can't start them anyhow):
$ tree /sys/fs/cgroup/cpuset/machine.slice
/sys/fs/cgroup/cpuset/machine.slice
├── cgroup.clone_children
├── cgroup.procs
├── cpuset.cpu_exclusive
├── cpuset.cpus
├── cpuset.mem_exclusive
├── cpuset.mem_hardwall
├── cpuset.memory_migrate
├── cpuset.memory_pressure
├── cpuset.memory_spread_page
├── cpuset.memory_spread_slab
├── cpuset.mems
├── cpuset.sched_load_balance
├── cpuset.sched_relax_domain_level
├── notify_on_release
└── tasks
And, the 'tasks' file is empty:
$ cat /sys/fs/cgroup/cpuset/machine.slice/tasks
Is there anything else that I can clean up manually here?
I just quickly rebooted the machine, as I was testing something else,
and stumbled on this. But I must say, that's a very unhelpful error
message from systemd.
Thanks again, I now know what to look for.
--
/kashyap