Hi,
since it is essentially split feature of libvirt I'd assume it is only detected
when libvirt restarts.
virt-manager only asked libvirt what it can provide, and that hasn't been
changed.
Could you check if - instead of a hard reboot - a restart of libvirtd would
re-detect it as well?
If so we might need to balance the risk of restarting that service vs
the comfort of any sich split out features to be detected right on
install. I say balance as these packages could restart libvirtd on
install to trigger it being detected.
For now, I'd appreciate if you could check if
$ systemctl restart libvirtd.service
Would make it be detected in your case
P.S. An alternative is to check with upstream if there is any intent for
runtime detection of new features. Now that we split out more (split daemons in
25.04) this might be even more worth to sort out.
P.P.S. and maybe mention which release you are on, as even if it helps
and we make the change it likely will only change (as behavior changes)
in new releases and for old ones (to avoid regression) might be better
as documentation entry.
** Changed in: virt-manager (Ubuntu)
Status: New => Incomplete
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092350
Title:
virt-manager does not notice libvirt-daemon-driver-lxc being installed
until reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2092350/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
