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

[Xen-users] networking issue for beginners

To: "Xen-Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] networking issue for beginners
From: "md" <md@xxxxxxxxxxxxx>
Date: Sat, 14 Jan 2006 12:21:56 +0100
Delivery-date: Sat, 14 Jan 2006 11:19:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi List,
 
sorry for bothering you with this issue again - but I don't understand the networking stuff at all.....
 
 
However - I managed to build my custom kernels (dom0 with LVM, domFW as priviledged domain to be my firewall and a domU kernel for all my guests).
 
Also I understood that testing is the release to choose becauseI would like to use personalised bridges. (btw, how do I patch files as http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a didn't work for as I learned to patch...) 
 
 
I hide the 2nd pci devices of my machine from dom0 and attached them to my FW domain
 
lspci in dom0 broght:
 
0000:02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03)
0000:02:09.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03)
 
So I modified menu.lst as:
 
title   Xen 3.0 / XenLinux 2.6
kernel  /xen-3.0.gz dom0_mem=262144 physdev_dom0_hide=(02:09.1)
module  /vmlinuz-2.6-xen root=/dev/md2 ro console=tty0
module  /initrd.2.6.12.6-xen.img
 
ifconfig in dom0:
 
eth0      Link encap:Ethernet  HWaddr 00:E0:81:30:A5:CE
          inet addr:192.168.100.99  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:81ff:fe30:a5ce/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:891 errors:0 dropped:0 overruns:0 frame:0
          TX packets:666 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:78504 (76.6 KiB)  TX bytes:96772 (94.5 KiB)
 
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:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:202 (202.0 b)  TX bytes:202 (202.0 b)
 
peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:878 errors:0 dropped:0 overruns:0 frame:0
          TX packets:664 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:82832 (80.8 KiB)  TX bytes:99338 (97.0 KiB)
          Interrupt:24
 
vif0.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:666 errors:0 dropped:0 overruns:0 frame:0
          TX packets:892 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:96772 (94.5 KiB)  TX bytes:78594 (76.7 KiB)
 
xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1544 (1.5 KiB)  TX bytes:378 (378.0 b)
my domU (ppriviledged firewall) config looks like:
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.12.6-xen0-FW"
 
# Initial memory allocation (in megabytes) for the new domain.
memory = 64
 
# A name for your domain. All domains must have different names.
name = "Firewall"

pci = [ '02,09,1' ]
 
vif = [
'mac=ff:fe:00:00:00:01, ip=192.168.100.130, bridge=isp0, vifname=isp0.0',
'mac=ff:fe:00:00:00:02, ip=192.168.100.131, bridge=LAN, vifname=LAN0.0',
'mac=ff:fe:00:00:00:03, ip=192.168.100.132, bridge=DMZ, vifname=DMZ0.0' ]
 
disk = [ 'file:/opt/xen/domains/xen1.img,sda1,w', 'file:/opt/xen/domains/xen1.swap,sda2,w' ]
 
Well - fire up my firewall leads to:
Error: Error creating domain: (38, 'Function not implemented')
and xend-debug.log shows:
Traceback (most recent call last):
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 77, in op_create
    dominfo = self.xd.domain_create(config)
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomain.py", line 226, in domain_create
    dominfo = XendDomainInfo.create(config)
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 182, in create
    vm.initDomain()
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 1199, in initDomain
    self.createDevices()
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 1338, in createDevices
    self.createDevice(n, c)
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 975, in createDevice
    return self.getDeviceController(deviceClass).createDevice(devconfig)
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/server/DevController.py", line 80, in createDevice
    (devid, back, front) = self.getDeviceDetails(config)
  File "/usr/src/xen-unstable/dist/install/usr/lib/python/xen/xend/server/pciif.py", line 75, in getDeviceDetails
    enable = True)
error: (38, 'Function not implemented')
~
I guess I missed a few things....
 
How does xen know, that there are bridges called isp0, LAN and DMZ?
Anything about dummy devices that I forgott?
 
 
Any help would be highly appreciated...
 
thanx
 
Mat
 
icq 49761472
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] networking issue for beginners, md <=