uvt-kvm wait doesn't take network parameter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
uvtool |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
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/
Then wait would know the correct lease file to watch for newly created leases.
summary: |
- uvt-kvm wait should take network parameter + uvt-kvm wait doesn't take network parameter |
affects: | uvtool (Ubuntu) → uvtool |
Changed in uvtool: | |
importance: | Undecided → Wishlist |
status: | Confirmed → Triaged |
Status changed to 'Confirmed' because the bug affects multiple users.