When you are back verifying this @Lukas, could you please check if the
following is due to the very same or if it is yet another rough edge
that needs a bug on its own?
IN P/Q I see after install in the second level guest that the default-
network-ip-detection worked:
$ ip a show dev enc2
2: enc2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 52:54:00:b0:4b:3f brd ff:ff:ff:ff:ff:ff
altname enx525400b04b3f
inet 192.168.122.154/24 metric 100 brd 192.168.122.255 scope global dynamic
en
So the network is not conflicting
$ virsh net-dumpxml default
<network>
<name>default</name>
<uuid>5ed7b38c-025a-4bd4-871b-a96700f1d6ca</uuid>
<forward mode='nat'/>
<bridge name='virbr0' stp='on' delay='0'/>
<mac address='52:54:00:cb:4e:95'/>
<ip address='192.168.123.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.123.2' end='192.168.123.254'/>
</dhcp>
</ip>
</network>
This works:
$ virsh net-start default
Network default started
But why didn't it start it automatically?
Is that due to the same or something else?
Your new solution in questing needs to have that working anyway - and then we
need to look what Plucky needs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107448
Title:
libvirt-daemon-driver-qemu fails to install (--configure) due to
.postinst issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2107448/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
