Simon Deziel

@tomponline it took me a bit of fiddling with a fresh VM to reproduce but I still can: ``` $ lxc shell v3 root@v3:~# snap install lxd --channel latest/edge 2025-07-02T16:29:02Z...

> Yes the profile config is stored in the instance's backup.yaml file, but modifying the server's existing profile with settings from (potentially multiple conflicting) instance backup.yaml files seems problematic and...

> I think that's to be expected because its for instance recovery not server recovery. Yeah, that's probably the key distinction here. I've always been using `lxd recovery` to recover...

Could this be due to having to update the instance's `backup.yaml` that resides in the instance's volume?

Here's a quick script to reproduce the issue (needs 2 terminals): ``` #!/bin/bash for driver in dir lvm zfs; do lxc storage create "${driver}" "${driver}" lxc launch ubuntu-minimal-daily:24.04 c-"${driver}" -d...

For what it's worth, I'm still able to reproduce this with: ``` $ snap list lxd Name Version Rev Tracking Publisher Notes lxd git-1292962 34947 latest/edge canonical✓ in-cohort ```

> @cole-miller pointed me to https://pkg.go.dev/crypto/tls#ClientSessionCache which might be useful in reducing the TLS connection overhead that contributes to the `go-dqlite` performance issues that we see. Speeding up the TLS...

> > I don't believe LXD uses persistent connections for dqlite either, though I'm not sure if that's the reason or something else. > > I have the impression is...

@manztihagi based on https://github.com/canonical/multipass/issues/3528#issuecomment-2196019823, it seems the problem is that `lxc list --project=multipass` is able to pull the instance's IP but not `multipass list`. If so, you could try to...

> Container information: In those `lxc info`/`lxc config show`, it seems you were missing the needed `--project=multipass` bit.