Juan Carlos Castro y Castro
2007-Jun-25 15:45 UTC
[Fedora-xen] Confused on how to have each guest reach a VLAN
Both my host and guests are Fedora 6. My first, naive thought, was to just configure eth0.N within each guest OS. For testing purposes, I created eth0.69 both within guest01 and guest02, with addresses 10.11.12.101 and 10.1.12.102 respectively. But guest01 and guest02 can''t ping one another through these new addresses. I read http://wiki.xensource.com/xenwiki/XenNetworking and, in its last paragraph, it suggests I have to configure VLAN in the host OS, and add virtual interfaces to a bridge. But I''m confused about how to do that. Which interfaces do I have to create? Do I have to add them to the xenbr0 bridge? Can I have this start automagically upon "xm create"? Below are my ifconfig on the host machine, and the config files for the two guests (they have IDs 5 and 6): ---------------------------------------------------------------------- eth0 Link encap:Ethernet HWaddr 00:15:17:23:7D:6D inet addr:192.168.0.195 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:fe23:7d6d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:159825 errors:0 dropped:0 overruns:0 frame:0 TX packets:62265 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41732783 (39.7 MiB) TX bytes:61710095 (58.8 MiB) 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:4123270 errors:0 dropped:0 overruns:0 frame:0 TX packets:4123270 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:377591540 (360.0 MiB) TX bytes:377591540 (360.0 MiB) 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 MTU:1500 Metric:1 RX packets:1552519 errors:0 dropped:0 overruns:0 frame:0 TX packets:324298 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2101900272 (1.9 GiB) TX bytes:84510344 (80.5 MiB) Base address:0x2000 Memory:48180000-481a0000 tap0 Link encap:Ethernet HWaddr CA:C9:C4:AB:3E:A6 inet6 addr: fe80::c8c9:c4ff:feab:3ea6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:349 errors:0 dropped:0 overruns:0 frame:0 TX packets:1710 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:104729 (102.2 KiB) TX bytes:928665 (906.8 KiB) tap1 Link encap:Ethernet HWaddr 0E:3E:CA:31:FB:7A inet6 addr: fe80::c3e:caff:fe31:fb7a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37 errors:0 dropped:0 overruns:0 frame:0 TX packets:1195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:2922 (2.8 KiB) TX bytes:874780 (854.2 KiB) 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 NOARP MTU:1500 Metric:1 RX packets:62278 errors:0 dropped:0 overruns:0 frame:0 TX packets:159837 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:61715017 (58.8 MiB) TX bytes:41733575 (39.8 MiB) vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 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:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:6844 (6.6 KiB) xenbr0 Link encap:Ethernet HWaddr 0E:3E:CA:31:FB:7A UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:97424 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:25040439 (23.8 MiB) TX bytes:0 (0.0 b) ---------------------------------------------------------------------- name = "guest01" uuid = "6ab45a27-0718-5dc1-d235-1704e4273870" maxmem = 192 memory = 192 vcpus = 1 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 0 apic = 0 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 disk = [ "file:/var/lib/xen/images/guest01,hda,w" ] vif = [ "mac=00:16:3e:13:61:c3,bridge=xenbr0,type=ioemu" ] serial = "pty" ---------------------------------------------------------------------- name = "guest02" uuid = "6ab45a27-0718-5dc1-d235-1704e4273871" maxmem = 192 memory = 192 vcpus = 1 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 0 apic = 0 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 disk = [ "file:/var/lib/xen/images/guest02,hda,w" ] vif = [ "mac=00:16:3e:13:61:c4,bridge=xenbr0,type=ioemu" ] serial = "pty" ----------------------------------------------------------------------
Dale Bewley
2007-Jun-25 20:25 UTC
Re: [Fedora-xen] Confused on how to have each guest reach a VLAN
You could create each vlan in your dom0 like this # cat ifcfg-vlan20 DEVICE=eth0.20 BOOTPROTO=static ONBOOT=yes VLAN=yes BRIDGE=xenbr20 And define a bridge for each one like this # cat ifcfg-xenbr20 DEVICE=xenbr20 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=172.19.20.253 NETMASK=255.255.255.128 NETWORK=172.19.20.128 BROADCAST=172.19.20.255 Then edit your domU config to use xenbr20 etc.* Comment out the network-bridge script in your xend config. When you fire up the instance Xen will create the virtual interface on the fly. The domU doesn''t know or care what broadcast domain (VLAN) it is in. It only knows it''s subnet information. You might put a dhcp server on VLAN 20 above and tell all your domU''s to use BOOTPROTO=dhcp. *This format for the bridge name is deprecated in Fedora 7, but it works. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3