Hi,
most likely something on your device isn't ready yet to be started.
As an initial suggestion I'd recommend to enable debugging of libvirtd [1] via the config files.
And then do a full reboot.
The log file should then contain some info about trying to auto-start this but failing.
You can then grab the same log from the when you later manually start the pool and compare it.
That should already give you a good idea what might be wrong.
The two questions you need to answer with those logs as a first step are:
1. Is it even trying to enable it on boot time (is the actication or the trigger to activate broken)?
2. If it is trying to start it at boot, what is different to the same that works later.
Hi,
most likely something on your device isn't ready yet to be started.
As an initial suggestion I'd recommend to enable debugging of libvirtd [1] via the config files.
And then do a full reboot.
The log file should then contain some info about trying to auto-start this but failing.
You can then grab the same log from the when you later manually start the pool and compare it.
That should already give you a good idea what might be wrong.
The two questions you need to answer with those logs as a first step are:
1. Is it even trying to enable it on boot time (is the actication or the trigger to activate broken)?
2. If it is trying to start it at boot, what is different to the same that works later.
[1]: https:/ /libvirt. org/kbase/ debuglogs. html#turning- on-debug- logs