There seems to have been some movement on this upstream:
https://lore.kernel<email address hidden>/T/#m4f61669a283a87623e4b8ce484e65c1bbaa76935
The exact commands we use typically are: lxc init ubuntu:22.04 testbed --vm # lxc config set testbed limits.cpu 1 lxc start testbed
and assume defaults on everything. (the commented config line was added in later as an experiement)
I don't have direct access to a system with that many cores, but I'll ask them to try all your suggestions and update the bug with results.
There seems to have been some movement on this upstream:
https:/ /lore.kernel<email address hidden> /T/#m4f61669a28 3a87623e4b8ce48 4e65c1bbaa76935
The exact commands we use typically are:
lxc init ubuntu:22.04 testbed --vm
# lxc config set testbed limits.cpu 1
lxc start testbed
and assume defaults on everything. (the commented config line was added in later as an experiement)
I don't have direct access to a system with that many cores, but I'll ask them to try all your suggestions and update the bug with results.