Antwort: Re: Xen 3.0.3 and VLAN
Tim Post <tim.post@netkinetics.net> schrieb am 03.11.2006 02:34:42:
Hi Tim,
> Try using brctl to manually create the bridge, then pin the nic to the
> bridge manually (quick fix), if that works just toss something in init.d
> to do so.
Thanks for your advice!
I adjusted the interfaces file so that the xenbr0 ius created there,
the system can be sucessfully booted with the attached configuration
communicating over VLAN 94 with the network.
I do not yet understand which component is going to create the vifX.Y
interfaces
needed to start successfully the DomU's ?
xm create yields:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
The system ist running the latest debian/unstable tree,
so there is udev but no hotplug package.
/etc/network/interfaces:
auto lo
iface lo inet loopback
auto eth0.94
iface eth0.94 inet static
address 172.17.94.48
netmask 255.255.255.0
gateway 172.17.94.254
broadcast 172.17.94.255
auto xenbr0
iface xenbr0 inet static
address 172.17.94.48
netmask 255.255.255.0
gateway 172.17.94.254
broadcast 172.17.94.255
bridge_fd 0
bridge_maxwait 0
bridge_helo 0
bridge_stp off
bridge_ports eth0.94
# some other interface used as interconnect to second xen-maschine
auto eth1
iface eth1 inet static
address 10.10.10.1
netmask 255.255.255.0
/etc/xen/xend-config.sxp:
(xend-http-server yes)
(xend-unix-server yes)
(xend-tcp-xmlrpc-server yes)
(xend-unix-xmlrpc-server yes)
(xend-relocation-server yes)
(xend-address '')
(xend-relocation-address '')
(xend-relocation-hosts-allow '')
(network-script network-dummy)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)
domU.cfg:
kernel = '/boot/vmlinuz-2.6.18-1-xen-vserver-686'
ramdisk = '/boot/initrd.img-2.6.18-1-xen-vserver-686'
memory = '256'
root = '/dev/sda1 ro'
disk = [ 'file:/mnt/vserver/images/domains/openser/disk.img,sda1,w',
'file:/mnt/vserver/images/domains/openser/swap.img,sda2,w' ]
name = 'openser'
dhcp = 'dhcp'
vif = [ 'bridge=xenbr0 mac=00:16:3e:06:a2:f8' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
ifconfig:
eth0 Protokoll:Ethernet Hardware Adresse 00:0F:20:98:A2:B4
inet6 Adresse: fe80::20f:20ff:fe98:a2b4/64
Gltigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6342 errors:0 dropped:0 overruns:0 frame:0
TX packets:716 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlnge:1000
RX bytes:489663 (478.1 KiB) TX bytes:130201 (127.1 KiB)
Interrupt:16
eth1 Protokoll:Ethernet Hardware Adresse 00:0F:20:98:A2:B5
inet Adresse:10.10.10.1 Bcast:10.10.10.255 Maske:255.255.255.0
inet6 Adresse: fe80::20f:20ff:fe98:a2b5/64
Gltigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlnge:1000
RX bytes:0 (0.0 b) TX bytes:492 (492.0 b)
Interrupt:17
eth0.94 Protokoll:Ethernet Hardware Adresse 00:0F:20:98:A2:B4
inet6 Adresse: fe80::20f:20ff:fe98:a2b4/64
Gltigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3406 errors:0 dropped:0 overruns:0 frame:0
TX packets:711 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlnge:0
RX bytes:194066 (189.5 KiB) TX bytes:123921 (121.0 KiB)
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gltigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlnge:0
RX bytes:5560 (5.4 KiB) TX bytes:5560 (5.4 KiB)
xenbr0 Protokoll:Ethernet Hardware Adresse 00:0F:20:98:A2:B4
inet Adresse:172.17.94.48 Bcast:172.17.94.255
Maske:255.255.255.0
inet6 Adresse: fe80::20f:20ff:fe98:a2b4/64
Gltigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3403 errors:0 dropped:0 overruns:0 frame:0
TX packets:705 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlnge:0
RX bytes:193856 (189.3 KiB) TX bytes:123453 (120.5 KiB)
Reply to: