libvirt users - Dec 2014 - Bhyve drv creates duplicate tap0 references

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good morning,

I am not sure if this is a known issue or if I should raise as a bug.

When using libvirt 1.2.11 on FreeBSD 10.1-RELEASE with bhyve, I have notice that
a machine which defines:

    <interface type='bridge'>
      <mac address='52:54:00:88:44:08'/>
      <source bridge='bridge10'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00'
slot='0x02' function='0x0'/>
    </interface>
    <interface type='bridge'>
      <mac address='52:54:00:42:8f:c1'/>
      <source bridge='bridge11'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00'
slot='0x03' function='0x0'/>
    </interface>

Generates a bhyve command from domxml-to-native that contains the interfaces
such that:

- -s 2:0,virtio-net,tap0,mac=52:54:00:88:44:08 -s
3:0,virtio-net,tap0,mac=52:54:00:42:8f:c1

As a result, in this configuration, no network traffic works due to the
duplication of the tap0 device in each command.

When running two machines simultaneously, both are allocated to tap0, again
causing issues.

Is this a known issue?

Please include me in replies as I am offlist.


- -- 
Sincerely,

William Brown

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJUoeiHAAoJEO/EFteBqAmaA2EP/ixYU792vc4K41jnI2Z+cC11
PVMEI4YFiaBwU4xBE7FpOrgnz/oVOKE5r4/PYM+M+c460yJMeEHbUQ3haH0meciN
TuiOBB2uOx2mvaPBbOKL2Kd8u3poR7nBwwisDD6M81HhCGNan1uFoTzCXswZGlEn
C0EgXHh2wTUVl3HWYbKXW6WmuhYTn8IHuPFjWNKGwJdHOzVYOPfmIiMU/qLlNNG1
FEjf+FS9yjuzBFSa6QszQG10DSPNJ6KghDxCVj2hUl0FHHcYbukbHa4FGwc261i0
h6MII67/27ZIaYA+7yqL2A9pa4Pj1FQ/IWWzuemG4TAbETLIEps4PrFvXLHgX0l/
KYE/5vysYrWjNXs6RXQwEcRBPxOHxhrAdl2t6FkYDSGf27WIwEepSPlo3r/bCenZ
5z6RkIq3HRdZy4bnZPcy1hUOOKKDrq2PXRJ3DIWDktfmpHf+IyCBb7jEKUQU8cL8
4ODeHFrQ8RcvEmXvLHk8Gt1y5/cOhs2VI9JDf0IZLfPi3+OETDY54pI7PPkv8mya
LmDS9YdmDfAdks/wTX1a4F80g0m4qR5X9HvgUu0bGSq3k5mefRFzi3PLf45tiKXo
9kEYrq9wmd2b4YIdPzdANE/NAz9sLM/phJNqSoVbHhxgOtAMNr2XPs0l9J/e2cUa
OuFCyESOu2iKL3C5fCU1
=tL0W
-----END PGP SIGNATURE-----