Public bug reported:
1) vivid
2) 0~bzr99-0ubuntu1
3) uvt-kvm wait --insecure vm1 waits till the VM is up
4) times out but VM is up due to creating with a separate bridge:
I've created new bridges via virsh net-define scaling-1.xml, virsh net-
start scaling-1 which creates a new bridge device (scaling-1) with a new
network.
I can create a VM and use this newly defined bridge with uvt-kvm create ....
--bridge scaling-1
This all works fine, however, uvt-kvm wait only looks at the 'default' libvirt
network.
Ideally I can pass the network name (which may not be the bridge name,
like default -> virbr0) and uvtool should look up the network conf file
(/var/lib/libvirt/dnsmasq/$NETWORK.conf; and extract the interface=
value and then use that to specify the status and conf file to the
LeaseWait notifier.
Then wait would know the correct lease file to watch for newly created
leases.
** Affects: uvtool (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/1454476
Title:
uvt-kvm wait should take network parameter
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1454476/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
