| 30 Apr 2026 |
 adamcstephens | hence why i was waiting before adding the option ;) | 20:34:16 |
 Tom | yeah, we'll see wheter it even reaches unstable before 7.0 🙃 | 20:34:50 |
| Tom | the s3 commit is merged and it looks like there will be security stuff included with 7.0 https://github.com/lxc/incus/pull/3273 | 22:37:31 |
| Tom | * the s3 pr is merged and it looks like there will be security stuff included with 7.0 https://github.com/lxc/incus/pull/3273 | 22:37:41 |
| Tom | i count 9 CVEs | 22:39:16 |
| 1 May 2026 |
| adamcstephens | https://github.com/lxc/incus/milestone/35 | 14:17:32 |
| Tom | Quite a sprint that happened there | 14:34:14 |
| 2 May 2026 |
| Tom | https://github.com/lxc/incus/releases/tag/v7.0.0 | 05:56:56 |
| Tom | https://github.com/NixOS/nixpkgs/pull/515853 | 11:47:03 |
| Tom changed their profile picture. | 18:41:08 |
| 3 May 2026 |
| Tom | I just noticed that /var/log/incus/*/{qemu.log,qemu.early.log} is rather empty for me. qemu.log is the file incus info --show-log $INSTANCE_NAME will look at (one of the commands to run when opening an issue in the incus repo.)
Haven't looked into it deeper.
| 12:10:57 |
| 4 May 2026 |
| adamcstephens | https://github.com/lxc/incus/issues/3304#issuecomment-4373128957 | 17:41:15 |
| adamcstephens | who needs VMs with more than one CPU? | 17:41:42 |
| Tom | i mean, we also only test it in the regard wheter hotpluging works, so .... i guess not many 🙃 | 18:15:54 |
| Tom | i'm really not sure of what to do at this point. 26.05 is right around the corner and i don't think the issues (haven't looked too much into what else has popped up as i'm rather short on time currently) will be addressed in time
Especially if we want to have some amount of confidence that it won't cause everyone relying on incus headaches | 18:34:53 |
| Tom | I'm already thinking about wheter we could somehow do a form of "mkRename" with incus-lts to incus-lts6 or wheter we'll introduce the new one as incus-lts7 (opt-out of the update vs. opt-in) or whatever | 18:35:20 |
| Tom | I think there is a strong case for us wanting to have 7.0 with how security patches have been handled on 6 (them not beeing tagged as a release) and the whole minio situation but if 7.0 isn't ready we somehow have to deal with that :/ | 18:35:52 |
| adamcstephens | i'm still planning on pushing v7 out for 26.05. Hopefully 7.0.1 will fix this bug and we can move forward. | 19:31:28 |
| adamcstephens | sounds like it's a problem with both 6.12 kernels, and nested virtualization. | 19:31:44 |
| adamcstephens | if we're not comfortable shipping it to 26.05, then we can leave v6 as LTS. it still has three more years of "support" | 19:34:20 |
| Tom | just not sure when 7.0.1 is going to happen at this point | 19:36:55 |
| Tom | https://github.com/lxc/incus/milestone/36 | 19:37:02 |
| Tom | (that's for 7.1.0) | 19:37:10 |
 hexa | we're like a month away from release | 19:38:49 |
| adamcstephens | sorry, i meant 7.1. | 19:40:03 |
| adamcstephens | to reword, i'd rather hold off on updating this release (if necessary) over supporting both LTS releases. | 19:41:06 |
| hexa | we should absolutely have 7.0 LTS in 26.05 | 19:42:04 |
| hexa | regressions like that will get fixed | 19:42:13 |
| hexa | what I'm saying is … there's like four more weeks until it starts mattering | 19:42:47 |
| hexa | Redacted or Malformed Event | 19:42:54 |
