|
From: Bruce S. <bw...@re...> - 2012-03-24 12:05:51
|
> OK, the brief update. "--enable-rule_generator" works (adds persistent-net and
> persistent-cd).
OK, good. Are you going to commit that change?
And do we need to add anything in the boot scripts to run the script
that creates persistent-net?
> During the testing (in KVM) I found the following lines in
> persistent_net_generator which floored me:
>
> # ignore KVM virtual interfaces
> 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"
>
> I have no idea why persistent_net should not work in virtualized environments.
> For me it looks like a bug/mistake.
> I'd be happy if you share your opinion.
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.
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.
- BS
|