Re: [Xen-users] newbie in trouble with CentOS Xen

[Greg Woods <woods@xxxxxxxx>]

On Thu, 2013-04-04 at 16:26 -0600, Alexandre Kouznetsov wrote:
> Hello.
> 
> El 04/04/13 13:26, Greg Woods escribiÃ:
> > On Thu, 2013-04-04 at 12:16 -0600, Alexandre Kouznetsov wrote:
> >
> >> This is weired.
> >
> > It looks fairly normal for the way that RedHat/CentOS does it. What is
> > odd is that there is no ifconfig output for eth0.
> Please post an example, it would be great.
> 
> I expected pethX to keep the original interface's MAC.

It doesn't on my systems. I'll admit that I do not fully understand how
all this works, but here is partial ifconfig output from a working
CentOS 5.9 system:

eth2      Link encap:Ethernet  HWaddr 00:1B:21:A1:CA:B0  
          inet addr:192.168.203.2  Bcast:192.168.203.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:40680 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40048 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10464680 (9.9 MiB)  TX bytes:10335739 (9.8 MiB)

peth2     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:40298 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40189 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:9853371 (9.3 MiB)  TX bytes:10403372 (9.9 MiB)
          Memory:fa7e0000-fa800000 

xenbr2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:78922 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:19374293 (18.4 MiB)  TX bytes:0 (0.0 b)

From "brctl show":

xenbr2          8000.feffffffffff       no              vif5.1
                                                        vif4.1
                                                        vif3.1
                                                        vif2.1
                                                        vif1.1
                                                        vif0.2
                                                        peth2

Then all the /etc/xen config files just reference xenbr2.

All of the xenbrX and pethX devices have this same pseudo-MAC address.
It is not clear to me how they are connected to the underlying ethX
device.

All this said, if "ifconfig eth0" shows no output, while this device is
supposed to be used for bridged networking in Xen, that's a problem. If
it were me, I'd be looking at "dmesg" output to figure out why the
"eth0" device isn't being set up at boot time. Fix what you know is
broken first.

--Greg



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users