|
From: Serge L. <ser...@gm...> - 2012-03-25 01:52:32
|
On 03/24/2012 03:12 PM, Bruce Smith wrote: >>> I did a little research and it sounds like many virtualized >>> environments reuse MAC address ranges assigned to other manufacturers, >>> so I guess they don't want a conflict. >> I'd say if we have more than 1 NIC in a VM, we have to fixate name<-> mac >> regardless of possible conflict (if there is a conflict, we have to re-generate >> mac addresses - but it's a bit different story). To be honest, I don't >> understand the reason of ignoring NIC name persistence in VM, but those line >> were intentionally added - so, the reason apparently exists. It goads my >> curiosity :) > > I don't understand it either. Hmm. I'll ask udev developers. > > Does KVM keep the same Mac address every time it boots the same VM? > (if not, then it makes sense) It's configurable. Usually mac addresses are "static" for each VM. > >>> Is there a file in /lib/udev/rules.d/ that has a rule to omit KVM >>> devices? (like "75-persistent-net-generator.rules") If so, I'd be >>> okay with editing the file to remove the VM rules, or just removing >>> that file. >> Yes, it's exactly "75-persistent-net-generator.rules" file. Done as a patch >> because we cannot remove the rules file. > > Why can't the file just be removed in the install script? Technically it's not a problem to remove a file, but it is a rule (configuration) file for write_net_rules which generates /etc/udev/rules.d/70-persistent-net.rules. It's a pretty big config, we removed only a small part from it. If we delete the file, write_net_rules will work incorrectly. Serge |