Comment # 4 on bug 1215636 from James Fehlig
(In reply to MichaƂ Szczepaniak from comment #3)
> cgroup_enable=memory
> systemd.unified_cgroup_hierarchy=0 isolcpus=1,2,3,4,5,7,8,9,10,11

I don't have any of these in the kernel command line of my Tumbleweed host.

> I'm including this because previously I had
> systemd.unified_cgroup_hierarchy=1 and recently i had to switch it off and
> enable the memory cgroup or the containers wouldn't start so maybe there are
> other cgroups i need to enable?

Interesting. Can you start your containers if you remove the above kernel
options, but enable DefaultMemoryAccounting as described in the following bug
comment?

https://bugzilla.suse.com/show_bug.cgi?id=1214845#c7

BTW, I reproduced virtlxcd terminating after 2 minutes even with a running
container. I'll need to investigate further. However, in my case the container
did continue to run, although it's quite simple

<domain type='lxc'>
  <name>vm1</name>
  <memory>500000</memory>
  <os>
    <type>exe</type>
    <init>/bin/sh</init>
  </os>
  <vcpu>1</vcpu>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
  <emulator>/usr/libexec/libvirt_lxc</emulator>
    <interface type='network'>
      <source network='default'/>
    </interface>
    <console type='pty' />
  </devices>
</domain>


You are receiving this mail because: