Hi Adam, the ID seems to be the MAC address.
In our experience, at first boot the VM brings up the interfaces in the order they are in the XML file. After that it remembers the MAC-IFName binding - which can create "gaps" in your interface name order if you delete a port, then add another (as it will get a new random MAC from the hypervisor). Our IF definition looks like this: <interface type='bridge'> <mac address='52:54:00:4f:a1:ed'/> <source bridge='br02'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Even when I shuffle them around, the IFs in the VM are correct after a reboot. Hope this helps. Matus -- Matus Staudt Network Engineer Digmia s.r.o. On Fri, 2018-06-01 at 17:06 +0100, [email protected] wrote: > Hi folks, Anyone run into this problem of vNICs being randomly assigned to ports on CSR1Kv please? Is there anything I can use in the VM's XML definition to help it nail the ports down in the correct order? I'm using KVM/libvirt and no cisco provided scripts, booting from a qcow2 image. Thanks adam netconsultings.com ::carrier-class solutions for the telecommunications industry:: _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
