Auto start vm's does not start under 25.10

Apps and Virtualization
1

Hi

Vm’s under containers set to auto start does not automatically start when rebooting 25.10

2

That’s not correct. At least not for me - my VM does start automatically - and probably most others as such a bug would’ve been noticed at least in beta if it was very widespread.

Could you elaborate more on what exactly happens? Have you looked into some log files?

3

ok, what logs would you check?

this is a vm that was created originally under virtual machines

4

In /var/log, more specifically in messages, error, middlewared.log but especially in /var/log/libvirt/qemu/<your-vm>.log

5

/var/log/libvirt/qemu/ is empty

already looked at messages,

yes i have escalated to root

6

Incus vms and lxc do not Autostart on 25.10

7

Damn I overlooked the “under containers” part of the initial question xD

That makes sense now.

@erlend_oyen can you migrate the VM back to classic virtual machines?

8
  1. the vm starts just fine under containers, when i start it manually
  2. the vm is still present under virtual machines (auto start not enabled)
    i never removed it from virtual machines, after it was auto migrated over to containers
9

You probably chose the linked clone option when asked how to migrate the VM disk.

This means the VM under virtual machines is probably still in the state before the migration and you’d need to basically merge the changes done to the clone back to the original (probably via promotion of the clone, then you can delete the original and clone the current state back to a new zvol).

10

hm, i don’t think so, but how can that be verified?

anyway it’s been working fine right upon til 25.10 i have been using the vm with autostart under containers for a while.

11

I do believe that @LarsR is right and Incus VMs/containers now just don’t autostart anymore. I would very much advise you not to you Incus VMs anymore as they won’t be supported in the future as it seems.

To verify if the zvol is a linked clone, check if it has a “promote” button under datasets or run zfs get origin <zvol> - if it has an origin (not just “-”) it is a linked clone.

12

I know that they don’t autostart anymore, but i can’t remember where it was mentioned anymore…
Edit:
Found it

2 Likes
13

thank you, vm backup in virtual machines.

14

I know I’m little late, but i find a workaround how you can still make “auto” (as much as possible). Use cron job with command incus start <instance_name>. If there’s a way to make cron job after boot, we can have similiar effect (my server wakes up at specific time, so normal cron job is enough for me)

Edit: but to make it work good you also need to turn off VNC option (you can add it inside container instead of outside, I know the best would be if they bring back this feature, but it’s better than nothing)

Edit2: There’s a way to make it run after reboot, but stil after vnc (or at least i’m too green to figure it out) In shell use command crontab -e, choose preferred text editor and write on the bottom of the file “@reboot incus start <container_name>”. And it will automatically start your container after boot (But you still need to turn off VNC in option, because password file is only regenerating after CLI turn on and i don’t know how change location to not be temporary)

15

What a load of crap, especially since I manually created and dd migrated the zvols for these new Incus VMs. Would have been better if you hadn’t bothered to make that an option in the first place.