|
From: Serge L. <ser...@gm...> - 2012-03-24 10:15:59
|
Hi,
OK, the brief update. "--enable-rule_generator" works (adds persistent-net and
persistent-cd).
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.
Serge
On 03/23/2012 07:14 PM, Serge Leschinsky wrote:
> Hi Bruce,
>
> you are right... We missed "--enable-rule_generator" in udev script.
> Will test the script during weekend.
>
> BTW: There is a problem with 2 instances of devfs (/dev/, /shm/dev).
> A quick research shows that we should change init scripts a bit, i.e.
>
> --- pre_init 2012-03-23 19:06:49.000000000 -0700
> +++ pre_init 2012-03-23 19:07:55.000000000 -0700
> @@ -58,7 +58,8 @@
> # this won't completely umount, because the loop device is still using it
> # that's why we use the lazy option
> umount /initrd -l &> /dev/null
> -umount /shm/dev &> /dev/null
> +# it will fail because /shm/dev/console is locked
> +#umount /shm/dev &> /dev/null
>
> echo "Freeing InitRD memory"
> freeramdisk /dev/ram0
>
> and
>
> --- etc/init.d/boot 2012-03-23 19:12:17.000000000 -0700
> +++ /etc/init.d/boot 2012-03-23 19:11:28.000000000 -0700
> @@ -49,6 +49,10 @@
> /sbin/udevadm settle
> evaluate_retval
>
> +# unmount "old" devtmpfs and remove the dir
> +umount /shm/dev &> /dev/null
> +rm -rf /shm/dev &> /dev/null
> +
> # ls /dev/
>
> if [ -f /proc/sys/kernel/sysrq ]; then
>
>
>
> Sincerely,
> Serge
>
>
> On 03/23/2012 06:28 PM, Bruce Smith wrote:
>> I'm installing DL 1.6.0-RC3 on a new firewall and it assigns eth0&
>> eth1 to different network cards depending if I cold boot (power on)
>> vs. a warm reboot.
>>
>> The script that writes /etc/udev/rules.d/70-persistent-net.rules
>> doesn't seem to exist any longer, and that file is never getting
>> created automatically. I had to create it manually to fix the random
>> NIC name assignment problem.
>>
>> Is this a bug, or are we handling the naming of NIC's differently now?
>>
>> BTW, I tried assigning the module names in setup, instead of using
>> autoselect. That made no difference, and did not assign the names as
>> I specified.
>>
>> - BS
>>
>> ------------------------------------------------------------------------------
>> This SF email is sponsosred by:
>> Try Windows Azure free for 90 days Click Here
>> http://p.sf.net/sfu/sfd2d-msazure
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>
|