[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] 2 network connection for dom0 and domU(s)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gabor Szilagyi wrote:
> chris wrote:
>> eth1 doesnt show running so theres some issue with your dom0
>> configuration of eth1. you could try pasting the config here and see if
>> anyone can notice whats wrong
> 
> As I stated it is not plugged into a switch (because I do not have
> physical connection nearby for that network) if you think that makes a
> difference I can fake that and put it onto the same network different
> static IP... should this matter ??

Chris,

Both interfaces on dom0 are now connected (pingable from other hosts on
their respective network). Logged in the the domU (while started with
one bridge) and configured the /etc/network/interface file within domU
same way for both interface ...

Still the two bridge config doesn't work...

While watching the process I noticed that peth0 is created also vifID.0
and vifID.1 is created (watching ifconfig -a) but when I got the error
message they are all taken down ... wondering where is th issue on dom0
or domU ???

Gabor

> 
> Gabor
> 
>> On Thu, Feb 18, 2010 at 12:36 PM, Gabor Szilagyi <szilagyi@xxxxxxxxxxxx
>> <mailto:szilagyi@xxxxxxxxxxxx>> wrote:
> 
>> chris wrote:
>>> what does ifconfig -a and "brtcl show" output?
>> When I try with the two bridge config line
> 
>> vif = [ 'mac=00:16:3e:00:01:06, bridge=eth0' ,
>> 'mac=00:16:3e:10:01:01, bridge=eth1', ]
> 
>> got this error and the ifconfig/brctl below
>> Using config file "./test1_pv.cfg".
> 
>> Error: Device 1 (vif) could not be connected. Hotplug scripts not
>> working.
> 
> 
>> rasnew:/home/gabor# ifconfig -a
>> eth0      Link encap:Ethernet  HWaddr 00:21:86:ef:3e:bb
>>          inet addr:1 XX.XX.242.105  Bcast: XX.X.242.255
>>  Mask:255.255.255.0
>>          inet6 addr: fe80::221:86ff:feef:3ebb/64 Scope:Link
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:652048 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:62069 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:0
>>          RX bytes:130026530 (124.0 MiB)  TX bytes:7218830 (6.8 MiB)
> 
>> eth1      Link encap:Ethernet  HWaddr 00:0e:0c:64:cf:3c
>>          inet addr:10.0.0.105  Bcast:10.0.0.255  Mask:255.255.255.0
>>          UP 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:8 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:0
>>          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)
> 
>> peth0     Link encap:Ethernet  HWaddr 00:21:86:ef:3e:bb
>>          inet6 addr: fe80::221:86ff:feef:3ebb/64 Scope:Link
>>          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>>          RX packets:714082 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:94462 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:100
>>          RX bytes:229396507 (218.7 MiB)  TX bytes:9422167 (8.9 MiB)
>>          Memory:fc800000-fc820000
> 
>> tmpbridge Link encap:Ethernet  HWaddr 72:b2:05:6d:34:50
>>          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:0
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
>> rasnew:/home/gabor# brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> eth0            8000.002186ef3ebb       no              peth0
>> tmpbridge               8000.000000000000       no
> 
>> end domU eventualy quits
> 
>> trying with domU config
> 
>> vif = [ 'mac=00:16:3e:00:01:06, bridge=eth0' , ]
> 
>> No other changes !!!
>> rasnew:/home/gabor# ifconfig -a
>> eth0      Link encap:Ethernet  HWaddr 00:21:86:ef:3e:bb
>>          inet addr: XX.XX.242.105  Bcast:XX.XX.242.255
>>  Mask:255.255.255.0
>>          inet6 addr: fe80::221:86ff:feef:3ebb/64 Scope:Link
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:652584 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:62139 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:0
>>          RX bytes:130063411 (124.0 MiB)  TX bytes:7237170 (6.9 MiB)
> 
>> eth1      Link encap:Ethernet  HWaddr 00:0e:0c:64:cf:3c
>>          inet addr:10.0.0.105  Bcast:10.0.0.255  Mask:255.255.255.0
>>          UP 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:8 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:0
>>          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)
> 
>> peth0     Link encap:Ethernet  HWaddr 00:21:86:ef:3e:bb
>>          inet6 addr: fe80::221:86ff:feef:3ebb/64 Scope:Link
>>          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>>          RX packets:714624 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:94547 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:100
>>          RX bytes:229442341 (218.8 MiB)  TX bytes:9441589 (9.0 MiB)
>>          Memory:fc800000-fc820000
> 
>> tmpbridge Link encap:Ethernet  HWaddr 72:b2:05:6d:34:50
>>          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:0
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
>> vif21.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>>          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>>          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>>          RX packets:15 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:15 errors:0 dropped:6 overruns:0 carrier:0
>>          collisions:0 txqueuelen:32
>>          RX bytes:872 (872.0 B)  TX bytes:2021 (1.9 KiB)
> 
> 
>> rasnew:/home/gabor# brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> eth0            8000.002186ef3ebb       no              peth0
>>                                                        vif21.0
>> tmpbridge               8000.000000000000       no
> 
> 
>> I am not sure if this helps ...
> 
>> Gabor
> 
>>> On Thu, Feb 18, 2010 at 11:46 AM, Gabor Szilagyi
>> <szilagyi@xxxxxxxxxxxx <mailto:szilagyi@xxxxxxxxxxxx>
>>> <mailto:szilagyi@xxxxxxxxxxxx <mailto:szilagyi@xxxxxxxxxxxx>>> wrote:
>>> chris wrote:
>>>> In my experience its because the bridge is not brought up unless the
>>>> interface is configured. Does the eth1 on dom0 have an IP address
>>> or did
>>>> you put it up with ifconfig?
>>> Thanks Chris,
>>> Yes, it is fully configured (second network cable is not attached
>> right
>>> now but was tested). Actually /etc/network/interfaces file is fully
>>> configured on the dom0 for eth0 and eth1 ... just the second
>> network is
>>> not in the location where the host is now :-) could this be an issue?
>>> See ifconfig print out in my message below.
>>> Again, when I have only one bridge declared in the domU config (see
>>> below it comes up fine with one interface using the modifed
>> wrapper but
>>> with both it hangs
>>> Gabor
> 
>>>> - chris
>>>> On Thu, Feb 18, 2010 at 10:21 AM, Gabor Szilagyi
>>> <szilagyi@xxxxxxxxxxxx <mailto:szilagyi@xxxxxxxxxxxx>
>> <mailto:szilagyi@xxxxxxxxxxxx <mailto:szilagyi@xxxxxxxxxxxx>>
>>>> <mailto:szilagyi@xxxxxxxxxxxx <mailto:szilagyi@xxxxxxxxxxxx>
>> <mailto:szilagyi@xxxxxxxxxxxx <mailto:szilagyi@xxxxxxxxxxxx>>>> wrote:
> 
>>>> I am new to xen and went through the wiki(s) on bridging btw dom0
>>>> and domU.
>>>> My physical host has two network card which needs to be attached
>>> to two
>>>> different network (one private one public).
>>>> First using one bridge was successful but I am having trouble to
>> bring
>>>> up the second. I have tried to  modifie the xendconfig and tried to
>>>> create a custom wrapper for the bridging script following some
>>> examples.
>>>> The dom0 is Debian Squeeze (base install) with dom0 kernel
>>> compiled from
>>>> the jeremy's tree (no problem there). The Hypervisor 3.4.2 (64bit)
>>>> I have not found exact receipt for the layout I want
>>>> dom0 -- eth0 -- XX.XX.242.0/24 -- "bridge1" -- eth0 -- domU1
>>>> dom0 -- eth1 -- 10.0.0.0/24 <http://10.0.0.0/24> <http://10.0.0.0/24>
>>> <http://10.0.0.0/24>    -- "bridge2" --
>>>> eth1 -- domU1
>>>> All the interfaces will be using static IP (I have no problem
>>>> configuring those within their OS).
> 
>>>> Current setup:
>>>> rasnew:/etc/xen# cat xend-config.sxp|grep -v ^#|grep bridge
>>>> (network-script network-bridge-custom)
>>>> (vif-script vif-bridge)
>>>> rasnew:/etc/xen# cat ./scripts/network-bridge-custom
>>>> #!/bin/sh
>>>> /etc/xen/scripts/network-bridge "$@" netdev=eth0
>>>> /etc/xen/scripts/network-bridge "$@" netdev=eth1
> 
>>>> The test domU config is like this the uncommented line would hang the
>>>> domU although it shows up in xm list
>>>> rasnew:/etc/xen# cat test1_pv.cfg
>>>> bootloader = '/usr/lib/xen-3.4/bin/pygrub'
>>>> memory = 256
>>>> name = "testPV"
>>>> vif = [ 'mac=00:16:3e:00:01:06, bridge=eth0' , ]
>>>> #vif = [ 'mac=00:16:3e:00:01:06, bridge=eth0' ,
>>> 'mac=00:16:3e:10:01:01,
>>>> bridge=eth1', ]
>>>> disk = [ 'phy:/dev/vm-vg/testdomU.disk,xvda1,w', ]
>>>> On the host both eth0 and eth1 us up :
>>>> rasnew:/etc/xen# ifconfig
>>>> eth0      Link encap:Ethernet  HWaddr 00:21:86:ef:3e:bb
>>>>          inet addr: XX.XX.242.105  Bcast: XX.XX.242.255
>>>>  Mask:255.255.255.0
>>>>          inet6 addr: fe80::221:86ff:feef:3ebb/64 Scope:Link
>>>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>          RX packets:643696 errors:0 dropped:0 overruns:0 frame:0
>>>>          TX packets:61616 errors:0 dropped:0 overruns:0 carrier:0
>>>>          collisions:0 txqueuelen:0
>>>>          RX bytes:129478544 (123.4 MiB)  TX bytes:7094105 (6.7 MiB)
>>>> eth1      Link encap:Ethernet  HWaddr 00:0e:0c:64:cf:3c
>>>>          inet addr:10.0.0.105  Bcast:10.0.0.255  Mask:255.255.255.0
>>>>          UP 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)
> 
> 
>>>> Not sure what else I should list here :-)
>>>> Any suggestion would be appreciated. Can this be done with the xen
>>>> scripts or I have to build the bridges manually?
>>>> Thanks.
>>>> Gabor

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



- --
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Gabor Szilagyi (Mr.)                    Gabor.Szilagyi@xxxxxxxxxxxx |
                                           Benjamin Franklin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkt9j+IACgkQcYMbOTV6LVp5pwCfULnVesDtosHJ5T6rpH+OMpxS
2GYAoOZ9DK6mS/NTFlsDoGVop+QGUC6w
=nCeL
-----END PGP SIGNATURE-----

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.