tomponline
commented
4 days ago Hi, is this still an issue, have you tried using LXD 5.21 from 5.21/stable channel?
Support requests should generally go to the support forum https://discourse.ubuntu.com/c/lxd/126
Distribution: RHEL
Distribution version: 8.9
The output of "snap list --all lxd core20 core22 core24 snapd":
core20 20240416 2318 core22 20240488 1380 lxd 5.0.3.d921d2e 28373 snapd 2.62 21465
The output of "lxc info" or if that fails:
Issue description
Running/starting/install a fresh VM on a fresh lxd System not work It is loading very very long. I can not cancel/delete the Job in web Dashboard. After 1 Night it gets created but it not run/starting. Even when i try to run it.
running a normal Container works suddently.
First i tested this with the last lxd Version. Then i research a little bit and i try 5.0. Same Problem.
The Storage is an local Raid 6 with 7 Disks,
We want to run it on 4x Fujitsu RX2450m7 for run GPU (Nvidia A100) passthrough on Ubuntu VMs for an Kubernetes Cluster with Rancher.
Information to attach
dmesg)Just Infos about the tap Network Interfaces that gets created.
tapXXXXXX entered blocking state, entered disabled state and entered promiscuous mode
[ ] Container log (
lxc info NAME --show-log) The Logfile is not created. Error: open /var/snap/lxd/.....[ ] Container configuration (
lxc config show NAME --expanded)everything from default profile
[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
AppArmor support has been disabled. Disabled because lack of kernel Support Couldn'tfind the CGroup blkio.weight, disk priority will be ignored Failed to initialize fanotify, falling back to inotify" err="Failed to initialize fanotify: invalid argument"
[ ] Output of the client with --debug
It hanging on "Get response struct from LXD" ... Want to starting it... but it not continue.
No Errors
[ ] Output of the daemon with --debug (alternatively output of
lxc monitorwhile reproducing the issue)