I am able to reproduce an issue I am experiencing with spinning up the daily Ubuntu 22.04 image in a VM (using multipass 1.12.2 and LXD 5.15 installed via snap revision 25086 on Ubuntu 20.04.6 with a 5.15.78 kernel).
I receive the following error message when attempting to shell into the VM.
Error: LXD VM agent isn’t currently running
Running top shows qemu-system-x86 constantly running at 106.2% (and this never resolves).
VM instance is created via multipass (connected with lxd) and includes a bridge network along with larger settings for CPU, memory and disk (ie. 16 to 66 cpu’s, 66GB to 736GB of memory, and 1300GB disk).
Running with lxd 5.0.2 and lxd 5.11 works fine.
Running with lxd 5.15 (ie. lxd >= 5.12) fails to bring the LXD VM agent online.
lxc info reports -1 processes (consistent with being unable to connect to the LXD VM agent).
Attempting with a smaller CPU count of 12 works with lxd 5.15 when requesting specific combinations of lower resource counts (ie. 12 cpus, 40GB of memory, 30GB disk).
Attempting the same combination with 13 cpus fails with the same LXD VM agent issue.
I have tried reporting some of the standard logging outputs below.
- lxc info --project <instance_project> --show-log
Summary
Name: gaeam01-w4
Status: RUNNING
Type: virtual-machine
Architecture: x86_64
PID: 22664
Created: 2023/08/21 18:59 AEST
Last Used: 2023/08/21 18:59 AEST
Resources:
Processes: -1
Network usage:
eth0:
Type: broadcast
State: UP
Host interface: tap84d93e33
MAC address: 52:54:00:61:0d:5e
MTU: 1500
Bytes received: 1.11kB
Bytes sent: 164B
Packets received: 9
Packets sent: 2
IP addresses:
inet6: fd42:76bf:550c:7fee:5054:ff:fe61:d5e/64 (global)
eth1:
Type: broadcast
State: UP
Host interface: tapb3238b31
MAC address: 52:54:00:54:db:7a
MTU: 1500
Bytes received: 8.68kB
Bytes sent: 164B
Packets received: 138
Packets sent: 2
IP addresses:
Log:
- sudo lxd.buginfo
[ 8945.831422] perf: interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
Are you able to advise the best next steps for debugging and resolving this issue?