On Tue, Jan 3, 2012 at 8:52 AM, James B. Byrne <byrnejb@xxxxxxxxxxxxx> wrote:
I have set up a kvm host and configured a standard clone
prototype for generating new guests. One persistent (pun
intended) annoyance when cloning is the behaviour of udev
with respect to the virtual network interface.
The prototype is configured with just eth0 having a
dedicated IP addr. When the prototype is cloned udev
creates rules for both eth0 and eth1 in the clone.
Because eth1 does not exist in the cloned guest one has to
manually edit /etc/udev/rules.d/70-persistent-net.rules to
get rid of the bogus entries and then restart the clone
instance to have the changes take effect. All this does is
return the new guest to the prototype eth0 configuration.
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.
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@xxxxxxxxxxxxx
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
I do this on VM clones. It depends on your OS but where I've had to do it is with Ubuntu VMs. I'm not sure where exactly they set that in CentOS but I'd start looking in /lib/udev/rules.d/75-persistent-net-generator.rules
Grant McWilliams
_______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-virt
