maybe it is sufficient to simply apply to these MAC addrs what we already do to xen. It just seems that then we are vulnerable to device/driver ordering issues.
One other thing to consider is that kvm implements pci hotplug for network devices (http://www.linux-kvm.org/page/Hotadd_pci_devices). So whitelisting of kvm addresses would result in inconsistent naming with 2 network devices being added and removed in somewhat arbitrary order.
http:// hg.fedorahosted .org/hg/ python- virtinst/ file/ae6ca033e8 c5/virtinst/ util.py# l181 indicates that:
- 00:16:3E allocated to xensource
- 52:54:00 used by qemu/kvm
http:// libvirt. org/drvesx. html indicates:
- 00:0c:29 and 00:50:56 are owned by vmware
Further, I know that
- d0-0d used by Eucalyptus
maybe it is sufficient to simply apply to these MAC addrs what we already do to xen. It just seems that then we are vulnerable to device/driver ordering issues.
One other thing to consider is that kvm implements pci hotplug for network devices (http:// www.linux- kvm.org/ page/Hotadd_ pci_devices). So whitelisting of kvm addresses would result in inconsistent naming with 2 network devices being added and removed in somewhat arbitrary order.