Re: [Xen-users] dom0 networking disabled

["Greg Saunders" <saundersgreg@xxxxxxxxxxx>]

I think I have a similar situation to the one Kirk Brown had.

I've intalled Etch . . .

Linux 2.6.18-4-amd64 #1 SMP Wed Feb 21 14:29:38 UTC 2007 x86_64 GNU/Linux

.. . . and also the xen-linux-system-2.6.18-4-xen package and the 
bridge-utils package.   But I haven't tried installing any domUs because I 
can't even get an internet connection when I boot up using "Xen 
3.0.3-1-amd64 / Debian GNU/Linux, kernel 2.6.18-4-xen-amd64".  Assuming I 
should have internet connection when running the Xen kernel (like I do when 
I run the original Etch kernel), here's what I've done:

I've changed my /etc/network/interfaces file from . . .

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

auto eth0

.. . . to . . .

auto lo
iface lo inet loopback

iface xenbr0 inet dhcp
bridge_ports eth0

auto xenbr0


Note that there are couple of differences there from what Kirk Brown had: 
I'm using DHCP; I had an "allow-hotplug eth0" line in my original interfaces 
file, which I don't know if I should leave, remove, or maybe change to 
"allow-hotplug xenbr0".

My /etc/xen/xen-config.sxp file looks like this:


(network-script network-dummy)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)


The Kirk Browm message that started the thread I'm trying to continue has a 
section called "***** IFCONFIG AFTER NETWORK-BRIDGE *****".  I don't know 
what "AFTER NETWORK-BRIDGE" means, but when I enter the command . . .
ifconfig -a

.. . . I get this:

eth1      Link encap:UNSPEC  HWaddr 
32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00
         BROADCAST 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:1000
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

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:18 errors:0 dropped:0 overruns:0 frame:0
         TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1060 (1.0 KiB)  TX bytes:1060 (1.0 KiB)

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)

xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:3888 (3.7 KiB)


The . . .

brctl show

.. . . command reveals:

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000000000000       no


I take it there's something I'm missing, either to do with the brctl command 
or extra requirements to use DHCP, or "hotplug" . . . or did I not dance 
naked around the computer in quite the right way?

Hmmmmm.

_________________________________________________________________
Get Out Of The House - Ski, Skate & Sun 
http://local.live.com/?mkt=en-ca/?v=2&cid=A6D6BDB4586E357F!147

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