Specifying --bridge mode makes wait fail with "has no NIC MACs available" error

Bug #1640332 reported by Will Bryant
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
uvtool
Triaged
Medium
Unassigned

Bug Description

We are creating our VMs using:

  sudo uvt-kvm create --bridge br0 --cpu 8 --memory 2048 --disk 8 --ssh-public-key-file ~/.ssh/authorized_keys myhostname release=xenial arch=amd64

which works, but when we do:

  sudo uvt-kvm wait --insecure myhostname

We get "uvt-kvm: error: libvirt domain 'myhostname' has no NIC MACs available."

  sudo uvt-kvm ip myhostname

Has the same problem.

The MAC address is available in the libvirt domain definition:

$ sudo grep -A2 interface /etc/libvirt/qemu/myhostname.xml
    <interface type='bridge'>
      <mac address='52:54:00:d5:77:0e'/>
      <source bridge='br0'/>

This was previously commented on by another uvt-kvm user posting on the mailing list: https://www.redhat.com/archives/libvirt-users/2014-August/msg00021.html

Tags: patch
Revision history for this message
Connor Newton (phyrwork) wrote :

get_domain_macs() only retrieves the MAC addresses from 'network' type interfaces.

I've attached a patch which addresses this by also getting addresses from 'bridge' type interfaces.

Revision history for this message
Robie Basak (racb) wrote :

Thank you for the patch! I've added it to my TODO.

Changed in uvtool:
status: New → Triaged
importance: Undecided → Medium
tags: added: patch
Revision history for this message
Piotr Morgwai Kotarbiński (morgwai) wrote :

any news on this?

Revision history for this message
Piotr Morgwai Kotarbiński (morgwai) wrote :

the patch from #1 does not work for me: instead of getting an error `uvt-kvm wait` time-outs:
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:bf:69:10.

in the gui it seems like if the network was not selected: see screenshot.

in spite of this the vm seems to go up correctly and i can login to it via console and ssh to it successfully.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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