Comment 17 for bug 341006
Revision history for this message
| Scott Moser (smoser) wrote Re: [Bug 341006] Re: ease cloning of virtual images by disabling mac address rules | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Thu, 11 Feb 2010, Martin Pitt wrote:
> PCI based addressing ought to work, although this would break the
> (admittedly rather theoretical) possibility to move them to a different
> slot, etc. For hotpluggable network cards (USB etc, as you might find
> them on e. g. the Beagle board or other embedded controllers) we must
> stay at MAC-based identification.
Ok, so assuming "addressed based persistent naming" is desirable, I have
2 thoughts on how it could enabled:
a.) for all cards on the pci bus, use pci based persistent naming.
This fails in the moving a card from slot 1 to slot 2 case as you
mentioned above.
b.) for all devices deemed "virtual" use address based persistent naming.
This fails if we can't determine something to be "virtual". If we
selectively enable for known MAC addrs OR known drivers, then we'd miss
anywhere where the hypervisor implements a emulated device (pcnet32 or
e1000 in kvm) and selects a MAC address that we don't whitelist.
b, seems safer as we can have more strict control on the white list.
Thoughts?