|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-users
Re: [Xen-users] Xen configuration
 
domU is
eth0      Link encap:Ethernet  HWaddr AA:00:00:2A:09:90
         inet addr:192.168.2.19  Bcast:192.168.2.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 b)  TX bytes:42 (42.0 b)
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:4 errors:0 dropped:0 overruns:0 frame:0
         TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:340 (340.0 b)  TX bytes:340 (340.0 b)
xen-br0   Link encap:Ethernet  HWaddr AA:00:00:2A:09:90
         inet addr:192.168.2.19  Bcast:192.168.2.255  Mask:255.255.255.255
         UP BROADCAST RUNNING MULTICAST  MTU:1500  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)
Dom0 is
eth0      Link encap:Ethernet  HWaddr 00:0B:DB:D5:0B:2C
         inet addr:192.168.2.150  Bcast:192.168.2.255  Mask:255.255.255.0
         inet6 addr: fe80::20b:dbff:fed5:b2c/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:61297 errors:0 dropped:0 overruns:0 frame:0
         TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:6268481 (5.9 Mb)  TX bytes:10996 (10.7 Kb)
         Interrupt:28
eth1      Link encap:Ethernet  HWaddr 00:0B:DB:D5:0B:2D
         inet addr:192.168.2.151  Bcast:192.168.2.255  Mask:255.255.255.0
         inet6 addr: fe80::20b:dbff:fed5:b2d/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:58886 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2974 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:6017776 (5.7 Mb)  TX bytes:426989 (416.9 Kb)
         Interrupt:29
lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:4048 errors:0 dropped:0 overruns:0 frame:0
         TX packets:4048 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:344955 (336.8 Kb)  TX bytes:344955 (336.8 Kb)
sit0      Link encap:IPv6-in-IPv4
         NOARP  MTU:1480  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)
vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:6 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:42 (42.0 b)  TX bytes:0 (0.0 b)
xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet addr:192.168.2.150  Bcast:192.168.2.255  Mask:255.255.255.255
         inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1 errors:0 dropped:0 overruns:0 frame:0
         TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:28 (28.0 b)  TX bytes:546 (546.0 b)
Kip Macy wrote:
What does the output of ifconfig -a in dom0 and domU show? 
-Kip
On 4/27/05, Gary A Prochilo <gprochilo@xxxxxxxx> wrote:
  
Question about bridge configuration on the host and virtual machine side. I
am not able to correctly configure xen so that the virtual machine can
 access the network. Any suggestions would really be appreciated. 
Gary 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
    
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
  
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 
 |   
 
 | 
    | 
  
  
    |   | 
    |