Hello!
Problem: Hyper-V changes MAC address of virtual network adapter on every migration,
So '75-persistent-net-generator.rules' script changes network interface number.
Suggested solution: ignore MAC addresses specific for Hyper-V in the script
Tested: on Debian Lenny (5.0.x) with udev-0.125-7+lenny3
on Debian Squeze (6.0) with udev-164-3
Suggested patch: (for latest release - "udev-167")
------------------------------------------------------------------------------------------------------------
diff -r -u udev-167/extras/rule_generator/75-persistent-net-generator.rules udev-167.patched/extras/rule_generator/75-persistent-net-generator.rules
--- udev-167/extras/rule_generator/75-persistent-net-generator.rules 2010-09-03 08:08:14.000000000 -0400
+++ udev-167.patched/extras/rule_generator/75-persistent-net-generator.rules 2011-04-06 10:50:15.000000000 -0400
@@ -33,6 +33,8 @@
ENV{MATCHADDR}=="52:54:00:*", GOTO="persistent_net_generator_end"
# ignore VMWare virtual interfaces
ENV{MATCHADDR}=="00:0c:29:*|00:50:56:*", GOTO="persistent_net_generator_end"
+# ignore Hyper-V virtual interfaces
+ENV{MATCHADDR}=="00:15:5d:*", GOTO="persistent_net_generator_end"
# These vendors are known to violate the local MAC address assignment scheme
# Interlan, DEC (UNIBUS or QBUS), Apollo, Cisco, Racal-Datacom
------------------------------------------------------------------------------------------------------------
Thank you,
Leonid Antonenkov
Linux Developer
Intermedia
________________________________
This message (including attachments) is private and confidential. If you have received this message in error, please notify us and remove it from your system.
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
