On Tue, Jan 3, 2012 at 5:13 PM, Peter Larsen
<plarsen@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>> Is there no way to alter udev's behaviour? Is udev even
>> needed on a server system using virtual hardware?
>> Altering the rules file not a big deal in itself but it
>> adds needless busywork when setting up a new guest.
>
> Make sure the 70-persistent-net.rules is empty or doesn't contain any
> mappings in your template. This file is generated automatically when new
> hardware is discovered. So as long as the template doesn't contain it,
> you'll get it generated. The issue you'll find yourself in, however, is
> that you may discover the NICs in the wrong sequence so eth0 and eth1
> gets swapped around for you.
>
> A better solution is to not use the MAC address but the "bios" location
> in 70-persistent-net.rules. If you do that, you can keep the file in the
> template.
>
> It's a very common problem. Another way is to have a %post script in KS
> or after initial startup as a VM, that fixes the file based on what the
> VM properties are.
It happens in real hardware too if you move a disk to a different
chassis, clone a drive, restore a backup to similar hardware, etc.
Where is the best documentation on what triggers the rules to be
rewritten, how the bios location works, etc.?
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
