WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] How to use DomU as network backend?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] How to use DomU as network backend?
From: Peter Fokkinga <peter@xxxxxxxxxxx>
Date: Thu, 11 May 2006 23:16:26 +0200
Delivery-date: Thu, 11 May 2006 14:17:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44630229.8020203@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <44630229.8020203@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) H3 (4.0.1)
Quoting Matthias Wolf <matze.wolf@xxxxxxx>:
i really stuck. I am trying to get a DomU working as network backend.
All my systems are based on Gentoo with Xen 3.0.2 and Kernel 2.6.16.


I'm not sure I completely understand your situation, but I have
a domU that uses two physical PCI network cards and is connected
to a bridge which is defined in dom0. Maybe the configuration
below gives you some inspiration ;-)

Cheers, Peter

/etc/xen/vm.ein
---------------
vmid = 3
name = "ein"

kernel = "/vserver/kernels/vmlinuz-2.6.16-xenU"
root   = "/dev/hda1"
memory = 256
extra  = "quiet 2"

pci = ['01:00.0', '02:00.0']

disk = ['phy:/dev/vg1/einU,hda1,w']

vif      = ['ip=10.0.2.1,bridge=xenbr0']
ip       = "10.0.2.1"
netmask  = "255.255.0.0"
gateway  = "10.0.1.1"
hostname = "ein.lan"


peter@ein:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3E:1E:47:1F
          inet addr:10.0.2.1  Bcast:10.0.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:469733 errors:0 dropped:0 overruns:0 frame:0
          TX packets:442929 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:186453748 (177.8 MiB)  TX bytes:46955234 (44.7 MiB)

eth1      Link encap:Ethernet  HWaddr 00:13:D3:50:F6:17
          inet addr:10.1.1.251  Bcast:10.1.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:41131 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47920 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8371629 (7.9 MiB)  TX bytes:23469827 (22.3 MiB)
          Interrupt:16

eth2      Link encap:Ethernet  HWaddr 00:13:D3:50:F6:16
          inet addr:10.1.2.251  Bcast:10.1.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:52423 errors:0 dropped:0 overruns:0 frame:0
          TX packets:143492 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5244763 (5.0 MiB)  TX bytes:202871967 (193.4 MiB)
          Interrupt:17

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



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

<Prev in Thread] Current Thread [Next in Thread>