https://bugzilla.suse.com/show_bug.cgi?id=1215636 https://bugzilla.suse.com/show_bug.cgi?id=1215636#c1 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.szczepaniak.000@gmail.com Flags| |needinfo?(m.szczepaniak.000 | |@gmail.com) --- Comment #1 from James Fehlig <jfehlig@suse.com> --- (In reply to Michał Szczepaniak from comment #0)
Hello, since couple of updates I've been having issue with lxd containers in libvirt/virtmanager. At random times, previously once per day now even more often, they're being killed for no reason. No significant errors in logs whatsoever. While investigating i came across virtlxcd and noticed it has 2 hour timeout, and every time the service dies it takes all containers with it. I don't know why it has timeout, but I think it's intentional what I don't think is intentional is killing all containers so please advise
The default timeout is 2 minutes, not 2 hours. Regardless, virtlxcd should not terminate when it is managing active "VMs". The timeout should be inhibited in that case. I've stared at the inhibition code for quite some time and it looks correct. I'll need to reproduce the issue myself and poke around with gdb. In the meantime, you can override the timeout with 'systemctl edit --full virtlxcd.service`, and remove the '--timeout 120' from VIRTLXCD_ARGS. This will prevent the daemon from terminating. Can you check if your containers are fine when virtlxcd is started without the timeout option? -- You are receiving this mail because: You are on the CC list for the bug.