Re: [Xen-users] help with xen instalolation on debion ecth

[Iñaki Baz Castillo <ibc@xxxxxxxxxxxx>]

El Tuesday 08 May 2007 12:31:07 Michele Menciassi escribió:
> # ifconfig
> i've that output
> 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)
>
> i've no interface up... it's right?

Do the following:

~# cat /proc/net/dev
and see there which eth devices exist.

It's really possible that the number is eth3 o eth14 and there is a reason for 
that: udev and no-mac associated to domU internal eth.

I explain it:

With udev and udev rules when a new dev (new MAC) is detected the system uses 
a NEW ethX because there is an association MAC-ethX in:
  /etc/udev/rules.d  (see "25-iftab.rules" o "z25-net.rules"):

-----------
# This file causes network devices to be assigned consistent names.
# See udev(8) for syntax.

SUBSYSTEM=="net", ACTION=="add", DRIVER=="?*", \
                                PROGRAM="iftab_helper %k", NAME="$result"
------------

So it's possible that you have in that file more that one MAC detected so more 
than one eth created.


In Debian Etch, when upgrading "udev" is installed so udev rules start 
working.


To solve it the best option is to assign a MAC to your domU interface. So edit 
your /etc/xen/vm.cfg file:

   vif  = [ 'ip=192.168.1.241, mac=00:16:3e:60:73:3d' ]

Note that there is a range of MAC that you can use for Xen virtual machines (I 
don't knoiw it exactly).



Regards.

-- 
*Iñaki Baz Castillo*
ibc@xxxxxxxxxxxx

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