thr3ads.net - Xen users - [Xen-users] invalid network interface after starting xend [Sep 2005]

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

Stephan Böni

2005-Sep-27 13:44 UTC

[Xen-users] invalid network interface after starting xend

Before starting xend (xen 3.0) these are my correct network interfaces:

eth0      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:04
          inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
 
eth1      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:05
          inet addr:192.168.1.52  Bcast:192.168.1.255  Mask:255.255.255.0
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0

After starting xend i have some ungly interfaces:

eth1      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:05
          inet addr:192.168.1.52  Bcast:192.168.1.255  Mask:255.255.255.0
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
 
peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
 
vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 
xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Where is going my eth0 interface? And what is this funny peth0 interface with
this wrong mac address?

Thanks for your help.

Stephan

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

Ted Kaczmarek

2005-Sep-27 14:18 UTC

head link

Re: [Xen-users] invalid network interface after starting xend

On Tue, 2005-09-27 at 15:44 +0200, Stephan Böni wrote:> Before starting xend (xen 3.0) these are my correct network interfaces:
> 
> eth0      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:04
>           inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
>  
> eth1      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:05
>           inet addr:192.168.1.52  Bcast:192.168.1.255  Mask:255.255.255.0
>  
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
> 
> After starting xend i have some ungly interfaces:
> 
> eth1      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:05
>           inet addr:192.168.1.52  Bcast:192.168.1.255  Mask:255.255.255.0
>  
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>  
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>  
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>  
> xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> 
> Where is going my eth0 interface? And what is this funny peth0 interface
with this wrong mac address?
> 
> Thanks for your help.
> 
> Stephan
> I have been seeing similar issues as well, trying to use more than 1 nic
on a domU with unstable has not been possible for me. If you really want
to crash a domU quick, try to add a vlan to your dom0 and domU share on
a second nic :-)
>From what I have observed you also can''t bring a new interface
onlineafter xend has started as well. Meaning add a new ethernet to dom0 than
try to get a domU interface to bridge to it.

What makes you think the peth0 has the wrong mac address? 

On my unstable

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:382176 errors:0 dropped:0 overruns:0 frame:0
          TX packets:359951 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:290578836 (277.1 MiB)  TX bytes:194010196 (185.0 MiB)
          Interrupt:18 Base address:0x1c00

[root@inyoureyes mail]# brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.feffffffffff       no              peth0
                                                        vif0.0
                                                        vif1.1
                                                        vif2.1
                                                        vif3.1
                                                        vif4.1
                                                        vif5.1
                                                        vif6.1
                                                        vif8.1

Regards,
Ted





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

Stephan Böni

2005-Sep-27 14:58 UTC

head link

Re: [Xen-users] invalid network interface after starting xend

Now i've added an ip address to peth0. so it looks like:

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:74 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8181 (7.9 Kb)  TX bytes:470 (470.0 b)
          Interrupt:16

Funny thing. It works. Even with an other mac address as the one of the
physical interface.

Stephan


> -----Ursprüngliche Nachricht-----
> Von: Stephan Böni 
> Gesendet: Dienstag, 27. September 2005 16:42
> An: Ted Kaczmarek
> Cc: Xen-Users
> Betreff: AW: [Xen-users] invalid network interface after starting xend
> 
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Ted Kaczmarek [mailto:tedkaz@optonline.net]
> > Gesendet: Dienstag, 27. September 2005 16:18
> > An: Xen-Users
> > Betreff: Re: [Xen-users] invalid network interface after 
> starting xend
> > 
> > 
> > On Tue, 2005-09-27 at 15:44 +0200, Stephan Böni wrote:
> > > Before starting xend (xen 3.0) these are my correct network 
> > interfaces:
> > > 
> > > eth0      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:04
> > >           inet addr:192.168.1.51  Bcast:192.168.1.255  
> > Mask:255.255.255.0
> > >  
> > > eth1      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:05
> > >           inet addr:192.168.1.52  Bcast:192.168.1.255  
> > Mask:255.255.255.0
> > >  
> > > lo        Link encap:Local Loopback
> > >           inet addr:127.0.0.1  Mask:255.0.0.0
> > > 
> > > After starting xend i have some ungly interfaces:
> > > 
> > > eth1      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:05
> > >           inet addr:192.168.1.52  Bcast:192.168.1.255  
> > Mask:255.255.255.0
> > >  
> > > lo        Link encap:Local Loopback
> > >           inet addr:127.0.0.1  Mask:255.0.0.0
> > >  
> > > peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> > >           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500 
Metric:1
> > >  
> > > vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > >  
> > > xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > > 
> > > Where is going my eth0 interface? And what is this funny 
> > > peth0 interface with this wrong mac address?
> > > 
> > > 
> > I have been seeing similar issues as well, trying to use more 
> > than 1 nic
> > on a domU with unstable has not been possible for me. If you 
> > really want
> > to crash a domU quick, try to add a vlan to your dom0 and 
> > domU share on
> > a second nic :-)
> 
> I have no domU started (only Dom0 is running).
> 
> > From what I have observed you also can't bring a new 
> interface online
> > after xend has started as well. Meaning add a new ethernet to 
> > dom0 than
> > try to get a domU interface to bridge to it.
> 
> The first interface eth0 with mac address 00:14:5E:0A:53:04 is correct
> and works fine. After starting xend it has gone, replaced bei 
> peth0 with
> the mac address FE:FF:FF:FF:FF:FF.
> 
> > What makes you think the peth0 has the wrong mac address?
> 
> peth0 should be a physical interface, isn't it? Or do you 
> don't have any
> physical interfaces? how shows your ifconfig completly?
> 
> > On my unstable
> > 
> > peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
> >           RX packets:382176 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:359951 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:290578836 (277.1 MiB)  TX bytes:194010196 
> > (185.0 MiB)
> >           Interrupt:18 Base address:0x1c00
> > 
> > [root@inyoureyes mail]# brctl show
> > bridge name     bridge id               STP enabled     interfaces
> > xen-br0         8000.feffffffffff       no              peth0
> >                                                         vif0.0
> >                                                         vif1.1
> >                                                         vif2.1
> >                                                         vif3.1
> >                                                         vif4.1
> >                                                         vif5.1
> >                                                         vif6.1
> >                                                         vif8.1
> > 
> 
> Well, and does this work? Because in my configuration it does not.
> 
> Stephan
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Reasonably Related Threads

Search for more reasonably related threads

Xen users - Sep 2005 - invalid network interface after starting xend

[Xen-users] invalid network interface after starting xend

Re: [Xen-users] invalid network interface after starting xend

Re: [Xen-users] invalid network interface after starting xend

Reasonably Related Threads