uvt-kvm wait doesn't take network parameter

Bug #1454476 reported by Ryan Harper
10
This bug affects 2 people
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/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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in uvtool (Ubuntu):
status: New → Confirmed
Robie Basak (racb)
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.