Tom Parrott

Similar to https://github.com/lxc/incus/issues/2314#issuecomment-3129918070 and https://github.com/canonical/lxd/issues/11636

We should figure out why these checks are being done at all during `activateifneeded` stage, as I think they are unnecessary and undesirable at this stage. There may be other...

I suspect its the calls to `lxd.ConnectLXDUnix(` in `cmdActivateifneeded) Run` which in turn hit `/1.0` (because `args.SkipGetServer` is not true) in order to start the LXD server once its ascertained...

@simondeziel does this still occur for you on latest/edge btw? I couldnt re-create it.

Whilst I couldn't re-create it but I can see the problem. In `cmdActivateIfNeeded.run` there are 2 calls to `d.State()`: ```go instance.LoadNodeAll(d.State(), instancetype.Any) d.State().DB.Cluster.Transaction(context.TODO(), func(ctx context.Context, tx *db.ClusterTx) ``` Aside from...

> Just went through a `lxd recover` (see #14753) and the `default` profile obtained in the end lacked all the configs it initially had. > > Initially, the `default` profile...

> > 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...

@roosterfish this might be worth considering whilst you are looking into `lxd recover`. Can I assign this to you?

@roosterfish is this covered by one of your recent PRS?

Thanks for your detailed report! Yeah this was an area of concern originally: > Note: On systems that have mixed performance and efficiency cores (P+E) you may find that VM...