Re: Spam:*, [Xen-users] Xen questions - Swap, networking and erro rs

[Max E Baro <MEB@xxxxxxxxxxxxxxxxx>]

> I've got the test domain running now, and networking for xenU doesn't
> seem to work.  Here is the current output from ifconfig:
> 
> xen:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:0E:0C:3D:C2:7F
>          inet addr:204.225.94.83  Bcast:204.225.94.127
> Mask:255.255.255.192
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:121293 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:52205 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:8393755 (8.0 MiB)  TX bytes:4168294 (3.9 MiB)
>          Base address:0xec00 Memory:defa0000-defc0000
>
> 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:3494 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:3494 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:296403 (289.4 KiB)  TX bytes:296403 (289.4 KiB)
>
> vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          inet addr:169.254.1.0  Bcast:169.254.255.255  Mask:255.255.255.255
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:11 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:462 (462.0 b)  TX bytes:0 (0.0 b)
>
> Is the network settings for vif3.0 the result of the not configuring the
> vif variable in my xenU config?  I am hesitant specifying a mac address
> as I'm afraid of fubar'ing something.

From what I've learned, you have 2 options here:  either add the IP address, mask and other network parameters under Kernel parameters in the config file; or create an ifcfg-eth0 file in the domU.  The eth0 interface in the domU is attached to the vif3.0 interface in dom0.  On my system I had to bridge the vif to an eth on dom0 to access the domU from outside the box.  You may want to create a virtual eth0.1 and bridge the two with brctl.

 

Max Baro
Technical Support Representative
FACTS Services, Inc.
(305) 284 - 7440
meb@xxxxxxxxxxxxxxxxx

 

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