Container start fails after upgrade to 7.0 (kernel does not support core scheduling)

Incus
1

After upgrading to 7.0.0 incus containers fail to start under Arch Linux ARM.

The error I get is:

1 root@rve ~ # incus info --show-log proxy
Name: proxy
Description: HTTPs Proxy server
Status: STOPPED
Type: container
Architecture: aarch64
Created: 2025/10/27 23:23 CET
Last Used: 2026/05/27 22:54 CEST

Log (lxc.log):

lxc proxy 20260527205437.701 ERROR    start - ../src/lxc/start.c:core_scheduling:1793 - Invalid argument - The kernel does not support core scheduling
lxc proxy 20260527205437.702 ERROR    lxccontainer - ../src/lxc/lxccontainer.c:wait_on_daemonized_start:837 - Received container state "ABORTING" instead of "RUNNING"
lxc proxy 20260527205437.707 ERROR    start - ../src/lxc/start.c:__lxc_start:2288 - Failed to spawn container "proxy"
lxc proxy 20260527205437.707 WARN     start - ../src/lxc/start.c:lxc_abort:1229 - No such process - Failed to send SIGKILL via pidfd 17 for process 1475
lxc 20260527205437.892 ERROR    af_unix - ../src/lxc/af_unix.c:lxc_abstract_unix_recv_fds_iov:218 - Connection reset by peer - Failed to receive response
lxc 20260527205437.892 ERROR    commands - ../src/lxc/commands.c:lxc_cmd_rsp_recv_fds:128 - Failed to receive file descriptors for command "get_init_pid"

Is there a configuration option to mitigate this?

Thanks for helping :slight_smile:

2

No configuration. We’ve added logic to correctly handle this shortly after the 7.0 release. Those changes have been cherry-picked into some of the packages, but apparently not the Arch Linux ones.

3

Thank you for pointing this out.

I have built the Arch Linux Incus package with your changes cherry-picked and it works now.