[pve-devel] qemu : systemd cgroup scope already exist bug
Alexandre DERUMIER
aderumier at odiso.com
Thu Apr 21 04:23:52 CEST 2016
we can test if scope still exist here:
/sys/fs/cgroup/systemd/qemu.slice/vmid.scope
if exist, systemctl stop vmid.scope , before doing the system-run
----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 21 Avril 2016 03:17:47
Objet: [pve-devel] qemu : systemd cgroup scope already exist bug
Hi,
I have seen some users on the forum having a bug with systemd scope bug.
https://forum.proxmox.com/threads/qm-start-failed-to-create-message-input-output-error.25903/
http://permalink.gmane.org/gmane.linux.pve.user/5301
I have hit this bug sometimes too.
after a vm shutdown , the scope is still see has running by systemd.
And when you try to start the vm, you can't because systemd-run will say that the scope already exist.
In this case, we need to run "systemctl stop vmid.scope".
I have seen exactly same bug report on docker with no fix.
https://github.com/docker/docker/issues/7015
They workaround is to call systemctl stop vmid.scope, before launching systemd-run.
Maybe could be do the same ?
_______________________________________________
pve-devel mailing list
pve-devel at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
More information about the pve-devel
mailing list