thr3ads.net - Xen users - [Xen-users] eth3 change name to eth4

If this information is useful, please help other people find it:
Share via:

Emiliano Vazquez

2009-Jan-07 00:52 UTC

[Xen-users] eth3 change name to eth4_rename

Hi folks.

I´m having a problem with my XEN, i will explain:

uname -a ==>  Linux ubuntu 2.6.24-19-xen
xen-detect ==> Running in PV context on Xen v3.2.

Since 2 or 3 days my eth3 don´t change your name to peth3   (peth3 exist but
with a fake MAC 00:00:00:00:00:00)

I have a "brand new" NIC called eth4_rename with the mac address of
eth3   (here is my problem)

What happend ?

I check udev rules and it´s OK. 

There is only one think i can´t understand :

cat /var/log/messages  | grep eth3

Jan  6 16:38:10 ubuntu kernel: [   10.044263] eth3:  setting full-duplex.
Jan  6 16:38:27 ubuntu kernel: [   35.543649] peth3:  setting half-duplex.
Jan  6 16:38:27 ubuntu kernel: [   35.546133] ADDRCONF(NETDEV_UP): peth3: link
is not ready
Jan  6 16:38:37 ubuntu kernel: [   45.328835] device peth3 entered promiscuous
mode
Jan  6 16:38:37 ubuntu kernel: [   45.328848] audit(1231267117.765:6): dev=peth3
prom=256 old_prom=0 auid=4294967295
Jan  6 16:38:57 ubuntu kernel: [   62.705517] eth3: port 2(tap5) entering
learning state
Jan  6 16:38:57 ubuntu kernel: [   62.708041] eth3: topology change detected,
propagating
Jan  6 16:38:57 ubuntu kernel: [   62.708044] eth3: port 2(tap5) entering
forwarding state
Jan  6 16:38:57 ubuntu kernel: [   62.792030] eth3: port 3(vif3.1) entering
learning state
Jan  6 16:38:57 ubuntu kernel: [   62.792107] eth3: topology change detected,
propagating
Jan  6 16:38:57 ubuntu kernel: [   62.792109] eth3: port 3(vif3.1) entering
forwarding state
Jan  6 16:44:00 ubuntu kernel: [  331.229210] peth3:  setting full-duplex.
Jan  6 16:44:00 ubuntu kernel: [  331.230872] ADDRCONF(NETDEV_CHANGE): peth3:
link becomes ready
Jan  6 16:44:00 ubuntu kernel: [  331.231414] eth3: port 1(peth3) entering
learning state
Jan  6 16:44:00 ubuntu kernel: [  331.232721] eth3: topology change detected,
propagating
Jan  6 16:44:00 ubuntu kernel: [  331.232724] eth3: port 1(peth3) entering
forwarding state
Jan  6 16:45:00 ubuntu kernel: [  391.005849] eth3: port 1(peth3) entering
disabled state
Jan  6 16:47:50 ubuntu kernel: [  560.381618] eth3: port 1(peth3) entering
learning state
Jan  6 16:47:50 ubuntu kernel: [  560.382896] eth3: topology change detected,
propagating
Jan  6 16:47:50 ubuntu kernel: [  560.382900] eth3: port 1(peth3) entering
forwarding state
Jan  6 16:48:50 ubuntu kernel: [  620.045284] eth3: port 1(peth3) entering
disabled state
Jan  6 16:52:00 ubuntu kernel: [  808.807594] eth3: port 1(peth3) entering
learning state
Jan  6 16:52:00 ubuntu kernel: [  808.808982] eth3: topology change detected,
propagating
Jan  6 16:52:00 ubuntu kernel: [  808.808985] eth3: port 1(peth3) entering
forwarding state
Jan  6 16:53:00 ubuntu kernel: [  868.582834] eth3: port 1(peth3) entering
disabled state
Jan  6 16:54:25 ubuntu kernel: [  953.316822] eth3: port 1(peth3) entering
learning state
Jan  6 16:54:25 ubuntu kernel: [  953.318219] eth3: topology change detected,
propagating
Jan  6 16:54:25 ubuntu kernel: [  953.318222] eth3: port 1(peth3) entering
forwarding state
Jan  6 16:54:28 ubuntu kernel: [  956.047533] eth3: port 1(peth3) entering
disabled state
Jan  6 16:54:28 ubuntu kernel: [  956.066211] eth3: port 1(peth3) entering
disabled state
Jan  6 16:58:23 ubuntu kernel: [ 1189.692606] eth3: port 3(vif3.1) entering
disabled state
Jan  6 16:58:23 ubuntu kernel: [ 1189.692617] eth3: port 2(tap5) entering
disabled state
Jan  6 16:58:23 ubuntu kernel: [ 1190.114152] peth3: port 3(vif3.1) entering
learning state
Jan  6 16:58:23 ubuntu kernel: [ 1190.114163] peth3: port 2(tap5) entering
learning state
Jan  6 16:58:23 ubuntu kernel: [ 1190.115490] peth3: topology change detected,
propagating
Jan  6 16:58:23 ubuntu kernel: [ 1190.115493] peth3: port 3(vif3.1) entering
forwarding state
Jan  6 16:58:23 ubuntu kernel: [ 1190.115494] peth3: topology change detected,
propagating
Jan  6 16:58:23 ubuntu kernel: [ 1190.115496] peth3: port 2(tap5) entering
forwarding state
Jan  6 17:07:26 ubuntu kernel: [ 1730.535993] peth3: port 2(tap5) entering
disabled state
Jan  6 17:07:26 ubuntu kernel: [ 1728.755756] peth3: port 2(tap5) entering
disabled state
Jan  6 17:07:26 ubuntu kernel: [ 1730.719301] peth3: port 3(vif3.1) entering
disabled state
Jan  6 17:07:26 ubuntu kernel: [ 1730.748729] peth3: port 3(vif3.1) entering
disabled state
Jan  6 22:34:55 ubuntu kernel: [21175.707670] eth3: port 2(tap5) entering
disabled state
Jan  6 22:34:55 ubuntu kernel: [21176.014488] eth3: port 3(vif9.1) entering
disabled state
Jan  6 22:35:27 ubuntu kernel: [21149.769633] device eth3 entered promiscuous
mode
Jan  6 22:35:27 ubuntu kernel: [21149.769636] audit(1231288527.517:57): dev=eth3
prom=256 old_prom=0 auid=4294967295
Jan  6 22:35:31 ubuntu kernel: [21153.444607] device eth3 left promiscuous mode
Jan  6 22:35:31 ubuntu kernel: [21153.444610] audit(1231288531.309:61): dev=eth3
prom=0 old_prom=256 auid=4294967295
Jan  6 22:39:48 ubuntu kernel: [21405.835146] eth3: port 1(eth4_rename) entering
disabled state
Jan  6 22:39:58 ubuntu kernel: [21415.679927] eth3: port 2(tap5) entering
disabled state
Jan  6 22:39:58 ubuntu kernel: [21415.970464] eth3: port 3(vif10.1) entering
disabled state


I can´t conect my Virtual Machine with your NIC.

Thanks for read my message.

Emiliano Vazquez


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

Vladimir Elizarov

2009-Jan-07 01:47 UTC

head link

Re: [Xen-users] eth3 change name to eth4_rename

Emiliano Vazquez wrote:> Hi folks.
>  
> I´m having a problem with my XEN, i will explain:
>  
> uname -a ==>  Linux ubuntu 2.6.24-19-xen
> xen-detect ==> Running in PV context on Xen v3.2.
>  
> Since 2 or 3 days my eth3 don´t change your name to peth3   (peth3 
> exist but with a fake MAC 00:00:00:00:00:00)
>  
> I have a "brand new" NIC called eth4_rename with the mac address
of
> eth3   (here is my problem)
>  
> What happend ?
>  
> I check udev rules and it´s OK.
>  
> There is only one think i can´t understand :
>  
> cat /var/log/messages  | grep eth3
>  
> Jan  6 16:38:10 ubuntu kernel: [   10.044263] eth3:  setting full-duplex.
> Jan  6 16:38:27 ubuntu kernel: [   35.543649] peth3:  setting half-duplex.
> Jan  6 16:38:27 ubuntu kernel: [   35.546133] ADDRCONF(NETDEV_UP): 
> peth3: link is not ready
> Jan  6 16:38:37 ubuntu kernel: [   45.328835] device peth3 entered 
> promiscuous mode
> Jan  6 16:38:37 ubuntu kernel: [   45.328848] audit(1231267117.765:6): 
> dev=peth3 prom=256 old_prom=0 auid=4294967295
> Jan  6 16:38:57 ubuntu kernel: [   62.705517] eth3: port 2(tap5) 
> entering learning state
> Jan  6 16:38:57 ubuntu kernel: [   62.708041] eth3: topology change 
> detected, propagating
> Jan  6 16:38:57 ubuntu kernel: [   62.708044] eth3: port 2(tap5) 
> entering forwarding state
> Jan  6 16:38:57 ubuntu kernel: [   62.792030] eth3: port 3(vif3.1) 
> entering learning state
> Jan  6 16:38:57 ubuntu kernel: [   62.792107] eth3: topology change 
> detected, propagating
> Jan  6 16:38:57 ubuntu kernel: [   62.792109] eth3: port 3(vif3.1) 
> entering forwarding state
> Jan  6 16:44:00 ubuntu kernel: [  331.229210] peth3:  setting full-duplex.
> Jan  6 16:44:00 ubuntu kernel: [  331.230872] ADDRCONF(NETDEV_CHANGE): 
> peth3: link becomes ready
> Jan  6 16:44:00 ubuntu kernel: [  331.231414] eth3: port 1(peth3) 
> entering learning state
> Jan  6 16:44:00 ubuntu kernel: [  331.232721] eth3: topology change 
> detected, propagating
> Jan  6 16:44:00 ubuntu kernel: [  331.232724] eth3: port 1(peth3) 
> entering forwarding state
> Jan  6 16:45:00 ubuntu kernel: [  391.005849] eth3: port 1(peth3) 
> entering disabled state
> Jan  6 16:47:50 ubuntu kernel: [  560.381618] eth3: port 1(peth3) 
> entering learning state
> Jan  6 16:47:50 ubuntu kernel: [  560.382896] eth3: topology change 
> detected, propagating
> Jan  6 16:47:50 ubuntu kernel: [  560.382900] eth3: port 1(peth3) 
> entering forwarding state
> Jan  6 16:48:50 ubuntu kernel: [  620.045284] eth3: port 1(peth3) 
> entering disabled state
> Jan  6 16:52:00 ubuntu kernel: [  808.807594] eth3: port 1(peth3) 
> entering learning state
> Jan  6 16:52:00 ubuntu kernel: [  808.808982] eth3: topology change 
> detected, propagating
> Jan  6 16:52:00 ubuntu kernel: [  808.808985] eth3: port 1(peth3) 
> entering forwarding state
> Jan  6 16:53:00 ubuntu kernel: [  868.582834] eth3: port 1(peth3) 
> entering disabled state
> Jan  6 16:54:25 ubuntu kernel: [  953.316822] eth3: port 1(peth3) 
> entering learning state
> Jan  6 16:54:25 ubuntu kernel: [  953.318219] eth3: topology change 
> detected, propagating
> Jan  6 16:54:25 ubuntu kernel: [  953.318222] eth3: port 1(peth3) 
> entering forwarding state
> Jan  6 16:54:28 ubuntu kernel: [  956.047533] eth3: port 1(peth3) 
> entering disabled state
> Jan  6 16:54:28 ubuntu kernel: [  956.066211] eth3: port 1(peth3) 
> entering disabled state
> Jan  6 16:58:23 ubuntu kernel: [ 1189.692606] eth3: port 3(vif3.1) 
> entering disabled state
> Jan  6 16:58:23 ubuntu kernel: [ 1189.692617] eth3: port 2(tap5) 
> entering disabled state
> Jan  6 16:58:23 ubuntu kernel: [ 1190.114152] peth3: port 3(vif3.1) 
> entering learning state
> Jan  6 16:58:23 ubuntu kernel: [ 1190.114163] peth3: port 2(tap5) 
> entering learning state
> Jan  6 16:58:23 ubuntu kernel: [ 1190.115490] peth3: topology change 
> detected, propagating
> Jan  6 16:58:23 ubuntu kernel: [ 1190.115493] peth3: port 3(vif3.1) 
> entering forwarding state
> Jan  6 16:58:23 ubuntu kernel: [ 1190.115494] peth3: topology change 
> detected, propagating
> Jan  6 16:58:23 ubuntu kernel: [ 1190.115496] peth3: port 2(tap5) 
> entering forwarding state
> Jan  6 17:07:26 ubuntu kernel: [ 1730.535993] peth3: port 2(tap5) 
> entering disabled state
> Jan  6 17:07:26 ubuntu kernel: [ 1728.755756] peth3: port 2(tap5) 
> entering disabled state
> Jan  6 17:07:26 ubuntu kernel: [ 1730.719301] peth3: port 3(vif3.1) 
> entering disabled state
> Jan  6 17:07:26 ubuntu kernel: [ 1730.748729] peth3: port 3(vif3.1) 
> entering disabled state
> Jan  6 22:34:55 ubuntu kernel: [21175.707670] eth3: port 2(tap5) 
> entering disabled state
> Jan  6 22:34:55 ubuntu kernel: [21176.014488] eth3: port 3(vif9.1) 
> entering disabled state
> Jan  6 22:35:27 ubuntu kernel: [21149.769633] device eth3 entered 
> promiscuous mode
> Jan  6 22:35:27 ubuntu kernel: [21149.769636] 
> audit(1231288527.517:57): dev=eth3 prom=256 old_prom=0 auid=4294967295
> Jan  6 22:35:31 ubuntu kernel: [21153.444607] device eth3 left 
> promiscuous mode
> Jan  6 22:35:31 ubuntu kernel: [21153.444610] 
> audit(1231288531.309:61): dev=eth3 prom=0 old_prom=256 auid=4294967295
> Jan  6 22:39:48 ubuntu kernel: [21405.835146] eth3: port 
> 1(eth4_rename) entering disabled state
> Jan  6 22:39:58 ubuntu kernel: [21415.679927] eth3: port 2(tap5) 
> entering disabled state
> Jan  6 22:39:58 ubuntu kernel: [21415.970464] eth3: port 3(vif10.1) 
> entering disabled state
>  
> I can´t conect my Virtual Machine with your NIC.
>  
> Thanks for read my message.
>  
> Emiliano Vazquez
>  
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
try to change name eth3 in /etc/udev/rules.d/70-persistent-net.rules
example:
# PCI device 0x1106:0x3106 (via-rhine)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:1e:58:aa:72:07", ATTR{type}=="1",
KERNEL=="eth*",
NAME="lan0"


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

Emiliano Vazquez

2009-Jan-07 14:11 UTC

head link

Re: [Xen-users] eth3 change name to eth4_rename

Hi again.

I made the change in the  /etc/udev/rules.d/70-persistent-net.rules  but did 
not work.

I have to change the NIC for another, that solve the problem.


Thanks Vladimir!

Emiliano Vazquez



----- Original Message ----- 
From: "Vladimir Elizarov" <xengelpublicx@gmail.com>
To: "Emiliano Vazquez" <emilianovazquez@gmail.com>
Cc: <xen-users@lists.xensource.com>
Sent: Tuesday, January 06, 2009 11:47 PM
Subject: Re: [Xen-users] eth3 change name to eth4_rename

> Emiliano Vazquez wrote:
>> Hi folks.
>>  I´m having a problem with my XEN, i will explain:
>>  uname -a ==>  Linux ubuntu 2.6.24-19-xen
>> xen-detect ==> Running in PV context on Xen v3.2.
>>  Since 2 or 3 days my eth3 don´t change your name to peth3   (peth3
exist
>> but with a fake MAC 00:00:00:00:00:00)
>>  I have a "brand new" NIC called eth4_rename with the mac
address of eth3
>> (here is my problem)
>>  What happend ?
>>  I check udev rules and it´s OK.
>>  There is only one think i can´t understand :
>>  cat /var/log/messages  | grep eth3
>>  Jan  6 16:38:10 ubuntu kernel: [   10.044263] eth3:  setting 
>> full-duplex.
>> Jan  6 16:38:27 ubuntu kernel: [   35.543649] peth3:  setting 
>> half-duplex.
>> Jan  6 16:38:27 ubuntu kernel: [   35.546133] ADDRCONF(NETDEV_UP):
peth3:
>> link is not ready
>> Jan  6 16:38:37 ubuntu kernel: [   45.328835] device peth3 entered 
>> promiscuous mode
>> Jan  6 16:38:37 ubuntu kernel: [   45.328848] audit(1231267117.765:6): 
>> dev=peth3 prom=256 old_prom=0 auid=4294967295
>> Jan  6 16:38:57 ubuntu kernel: [   62.705517] eth3: port 2(tap5)
entering
>> learning state
>> Jan  6 16:38:57 ubuntu kernel: [   62.708041] eth3: topology change 
>> detected, propagating
>> Jan  6 16:38:57 ubuntu kernel: [   62.708044] eth3: port 2(tap5)
entering
>> forwarding state
>> Jan  6 16:38:57 ubuntu kernel: [   62.792030] eth3: port 3(vif3.1) 
>> entering learning state
>> Jan  6 16:38:57 ubuntu kernel: [   62.792107] eth3: topology change 
>> detected, propagating
>> Jan  6 16:38:57 ubuntu kernel: [   62.792109] eth3: port 3(vif3.1) 
>> entering forwarding state
>> Jan  6 16:44:00 ubuntu kernel: [  331.229210] peth3:  setting 
>> full-duplex.
>> Jan  6 16:44:00 ubuntu kernel: [  331.230872] ADDRCONF(NETDEV_CHANGE): 
>> peth3: link becomes ready
>> Jan  6 16:44:00 ubuntu kernel: [  331.231414] eth3: port 1(peth3) 
>> entering learning state
>> Jan  6 16:44:00 ubuntu kernel: [  331.232721] eth3: topology change 
>> detected, propagating
>> Jan  6 16:44:00 ubuntu kernel: [  331.232724] eth3: port 1(peth3) 
>> entering forwarding state
>> Jan  6 16:45:00 ubuntu kernel: [  391.005849] eth3: port 1(peth3) 
>> entering disabled state
>> Jan  6 16:47:50 ubuntu kernel: [  560.381618] eth3: port 1(peth3) 
>> entering learning state
>> Jan  6 16:47:50 ubuntu kernel: [  560.382896] eth3: topology change 
>> detected, propagating
>> Jan  6 16:47:50 ubuntu kernel: [  560.382900] eth3: port 1(peth3) 
>> entering forwarding state
>> Jan  6 16:48:50 ubuntu kernel: [  620.045284] eth3: port 1(peth3) 
>> entering disabled state
>> Jan  6 16:52:00 ubuntu kernel: [  808.807594] eth3: port 1(peth3) 
>> entering learning state
>> Jan  6 16:52:00 ubuntu kernel: [  808.808982] eth3: topology change 
>> detected, propagating
>> Jan  6 16:52:00 ubuntu kernel: [  808.808985] eth3: port 1(peth3) 
>> entering forwarding state
>> Jan  6 16:53:00 ubuntu kernel: [  868.582834] eth3: port 1(peth3) 
>> entering disabled state
>> Jan  6 16:54:25 ubuntu kernel: [  953.316822] eth3: port 1(peth3) 
>> entering learning state
>> Jan  6 16:54:25 ubuntu kernel: [  953.318219] eth3: topology change 
>> detected, propagating
>> Jan  6 16:54:25 ubuntu kernel: [  953.318222] eth3: port 1(peth3) 
>> entering forwarding state
>> Jan  6 16:54:28 ubuntu kernel: [  956.047533] eth3: port 1(peth3) 
>> entering disabled state
>> Jan  6 16:54:28 ubuntu kernel: [  956.066211] eth3: port 1(peth3) 
>> entering disabled state
>> Jan  6 16:58:23 ubuntu kernel: [ 1189.692606] eth3: port 3(vif3.1) 
>> entering disabled state
>> Jan  6 16:58:23 ubuntu kernel: [ 1189.692617] eth3: port 2(tap5)
entering
>> disabled state
>> Jan  6 16:58:23 ubuntu kernel: [ 1190.114152] peth3: port 3(vif3.1) 
>> entering learning state
>> Jan  6 16:58:23 ubuntu kernel: [ 1190.114163] peth3: port 2(tap5) 
>> entering learning state
>> Jan  6 16:58:23 ubuntu kernel: [ 1190.115490] peth3: topology change 
>> detected, propagating
>> Jan  6 16:58:23 ubuntu kernel: [ 1190.115493] peth3: port 3(vif3.1) 
>> entering forwarding state
>> Jan  6 16:58:23 ubuntu kernel: [ 1190.115494] peth3: topology change 
>> detected, propagating
>> Jan  6 16:58:23 ubuntu kernel: [ 1190.115496] peth3: port 2(tap5) 
>> entering forwarding state
>> Jan  6 17:07:26 ubuntu kernel: [ 1730.535993] peth3: port 2(tap5) 
>> entering disabled state
>> Jan  6 17:07:26 ubuntu kernel: [ 1728.755756] peth3: port 2(tap5) 
>> entering disabled state
>> Jan  6 17:07:26 ubuntu kernel: [ 1730.719301] peth3: port 3(vif3.1) 
>> entering disabled state
>> Jan  6 17:07:26 ubuntu kernel: [ 1730.748729] peth3: port 3(vif3.1) 
>> entering disabled state
>> Jan  6 22:34:55 ubuntu kernel: [21175.707670] eth3: port 2(tap5)
entering
>> disabled state
>> Jan  6 22:34:55 ubuntu kernel: [21176.014488] eth3: port 3(vif9.1) 
>> entering disabled state
>> Jan  6 22:35:27 ubuntu kernel: [21149.769633] device eth3 entered 
>> promiscuous mode
>> Jan  6 22:35:27 ubuntu kernel: [21149.769636] audit(1231288527.517:57):
>> dev=eth3 prom=256 old_prom=0 auid=4294967295
>> Jan  6 22:35:31 ubuntu kernel: [21153.444607] device eth3 left 
>> promiscuous mode
>> Jan  6 22:35:31 ubuntu kernel: [21153.444610] audit(1231288531.309:61):
>> dev=eth3 prom=0 old_prom=256 auid=4294967295
>> Jan  6 22:39:48 ubuntu kernel: [21405.835146] eth3: port 1(eth4_rename)
>> entering disabled state
>> Jan  6 22:39:58 ubuntu kernel: [21415.679927] eth3: port 2(tap5)
entering
>> disabled state
>> Jan  6 22:39:58 ubuntu kernel: [21415.970464] eth3: port 3(vif10.1) 
>> entering disabled state
>>  I can´t conect my Virtual Machine with your NIC.
>>  Thanks for read my message.
>>  Emiliano Vazquez
>> 
------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
> try to change name eth3 in /etc/udev/rules.d/70-persistent-net.rules
> example:
> # PCI device 0x1106:0x3106 (via-rhine)
> SUBSYSTEM=="net", ACTION=="add",
DRIVERS=="?*",
> ATTR{address}=="00:1e:58:aa:72:07", ATTR{type}=="1",
KERNEL=="eth*",
> NAME="lan0"
> 

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

Xen users - Jan 2009 - eth3 change name to eth4_rename

[Xen-users] eth3 change name to eth4_rename

Re: [Xen-users] eth3 change name to eth4_rename

Re: [Xen-users] eth3 change name to eth4_rename