I can reproduce the issue on Questing. The libvirt default network is
not started at runtime right after installation, but the autostart
symlink is properly installed. A restart of libvirtd.service does not
help, a reboot of the VM OTOH makes the virbr0 come up.
$ uvt-kvm create --password=ubuntu
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Also affects: libvirt (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Questing)
Importance: High
Assignee: Lukas Märdian (slyon)
Status: In Progress
--
You received th
Note: we should also double-check how this behaves on
Noble/Oracular/Plucky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2093864
Title:
default network no more configured in 10.10
To manage notif
This might be related to
https://code.launchpad.net/~slyon/ubuntu/+source/libvirt/+git/libvirt/+merge/484578
Going forward, we might need to install libvirt-daemon-config-network to set up
the default network.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
