Public bug reported:
With libvirt 11.0.0-2ubuntu6, `virsh start` on a fresh instance / fresh
libvirt installation will fail due to the default libvirt network not
being started by default on Plucky.
This is easily worked around by running `virsh net-autostart default`
and `virsh net-start default` - but relative to libvirt's behavior on
prior Ubuntu releases, this could be considered a regression.
Steps to reproduce:
1. Attempt to do a fresh virt-install on Plucky
2. Observe that the VM fails to start with a message about the network not
being started
This can be seen via
ubuntu@buzzsaw:/vms$ virsh net-list --all
Name State Autostart Persistent
----------------------------------------------
default inactive yes yes
<to fix the issue>
1. Run `virsh net-autostart default` and `virsh net-start default`
2. Attempt to do a fresh virt-install on Plucky
3. Observe that the VM starts successfully
ubuntu@buzzsaw:/vms$ virsh net-list --all
Name State Autostart Persistent
--------------------------------------------
default active yes yes
I would mark this as a low severity item since it has a simple
workaround
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2115222
Title:
Default network not started in Plucky libvirt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2115222/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
