Re: [Xen-users] Debian domU interface naming strangeness

["Ray Barnes" <tical.net@xxxxxxxxx>]

That worked great.  Thanks!

On Thu, Jul 31, 2008 at 6:10 PM, Stephen Kent <xen-users@xxxxxxxxxx> wrote:
>
> Ray:
>
> Debian and most distros with udev keep a record of previously observed
> interfaces in /etc/udev/rules.d/70-persistent-net.rules. If you don't
> specify a MAC address for the domU in your config, Xen will create a random
> MAC and assign it to your domU, which will then think it's a new interface.
> Delete 70-persistent-net.rules in your domU and change your vif= line so it
> includes mac=00:16:3E:3D:A0:30 in the configuration, and reboot the domU.
> It should recognize eth0 as the same interface every boot.
>
> - Stephen
>
> On Thu, 31 Jul 2008 17:52:04 -0400, "Ray Barnes" <tical.net@xxxxxxxxx>
> wrote:
>> Hi all.  I've got a Debian domU I created from scratch a few weeks
>> ago.  Every time I rolled it out previously in testing, it worked
>> fine.  But now it seems to make the ethernet device eth1 rather than
>> eth0 in the domU:
>>
>> localhost:~# ifconfig -a
>> eth1      Link encap:Ethernet  HWaddr 00:16:3E:3D:A0:30
>>           BROADCAST MULTICAST  MTU:1500  Metric:1
>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>
>> lo        Link encap:Local Loopback
>>           inet addr:127.0.0.1  Mask:255.0.0.0
>>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>
>> localhost:~# dmesg|grep -i eth
>> netfront: Initialising virtual ethernet driver.
>> netfront: device eth0 has flipping receive path.
>> localhost:~#
>>
>> Note that as eth1, it routes traffic just fine.  I can ifconfig it up
>> and set an IP address, then get good routed connectivity.  I'm seeing
>> this eth1 naming issue on dom0s running CentOS 5.0 with the stock Xen
>> 3.0.3 (yes that means literally 5.0, not a higher minor number), as
>> well as Cent 5.1 with Xen 3.2.0 compiled from source.  But obviously
>> it presents a problem since I can't count on consistent naming.
>>
>> Thoughts?
>>
>> -Ray
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users