Hi, I was running Xen fine but installed an additional PCI network card and subsequently an additional network interface eth1 for it. This has caused xenbr0 to disappear and I cannot create/start any guest domains. I restarted xend but it has no effect. Is there any way to re-create xenbr0. Kindly help. Regards, Asim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Asim, On Thu, Jun 26, 2008 at 9:42 AM, Asim <linkasim@gmail.com> wrote:> Hi, > I was running Xen fine but installed an additional PCI network card and > subsequently an additional network interface eth1 > for it. This has caused xenbr0 to disappear and I cannot create/start any > guest domains. I restarted xend but it has no > effect. Is there any way to re-create xenbr0. Kindly help. >It sounds like you are running into a problem with one of the bridge scripts. Trying running /etc/xen/scripts/network-bridge manually to see any errors. Please post the relevant lines of /etc/xen/xend-config.sxp Also, do a brctl show and post that output as well. Are you sure that the eth1 is the new card or the old card? It could be that you just need to change the netdev in /etc/xen/xend-config.sxp. Cheers, Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Todd - These seem to be a wonderful set of debugging steps that I did
not know - but unfortunately I could not catch the error. My eth0 is
working, eth1 is not enabled yet. Is it due to the way my kernel IP routing
table is set? Kindly help.
[root@adsl-01 ~]# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.00e0815caafe no peth0
eth1 8000.0007e93904bd no peth1
[root@adsl-01 ~]# /etc/xen/scripts/network-bridge status
===========================================================5: eth0:
<BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:e0:81:5c:aa:fe brd ff:ff:ff:ff:ff:ff
inet 128.105.104.101/24 brd 128.105.104.255 scope global eth0
inet6 fe80::2e0:81ff:fe5c:aafe/64 scope link
valid_lft forever preferred_lft forever
5: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:e0:81:5c:aa:fe brd ff:ff:ff:ff:ff:ff
inet 128.105.104.101/24 brd 128.105.104.255 scope global eth0
inet6 fe80::2e0:81ff:fe5c:aafe/64 scope link
valid_lft forever preferred_lft forever
bridge name bridge id STP enabled interfaces
eth0 8000.00e0815caafe no peth0
eth1 8000.0007e93904bd no peth1
128.105.104.0/24 dev eth0 proto kernel scope link src 128.105.104.101
128.105.104.0/24 dev eth1 proto kernel scope link src 128.105.104.126
169.254.0.0/16 dev eth1 scope link
default via 128.105.104.248 dev eth0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
128.105.104.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
128.105.104.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 128.105.104.248 0.0.0.0 UG 0 0 0 eth0
===========================================================[root@adsl-01 ~]#
/etc/xen/scripts/network-bridge start
There are no errors but there is no xenbr0!
The sxp file:
(network-script ''network-bridge netdev=eth0'')
(network-script network-bridge)
#(network-script network-route)
#(network-script network-nat)
(vif-script vif-bridge)
#(vif-script vif-route)
#(vif-script vif-nat)
Since these are static IPs, I''m confident that the working interface is
eth0.
-Asim
On Thu, Jun 26, 2008 at 9:40 AM, Todd Deshane <deshantm@gmail.com> wrote:
> Hi Asim,
>
>
> On Thu, Jun 26, 2008 at 9:42 AM, Asim <linkasim@gmail.com> wrote:
>
>> Hi,
>> I was running Xen fine but installed an additional PCI network card and
>> subsequently an additional network interface eth1
>> for it. This has caused xenbr0 to disappear and I cannot create/start
any
>> guest domains. I restarted xend but it has no
>> effect. Is there any way to re-create xenbr0. Kindly help.
>>
>
>
> It sounds like you are running into a problem with one of the bridge
> scripts.
>
> Trying running /etc/xen/scripts/network-bridge manually to see any errors.
>
> Please post the relevant lines of /etc/xen/xend-config.sxp
>
> Also, do a brctl show and post that output as well.
>
> Are you sure that the eth1 is the new card or the old card? It could be
> that you
> just need to change the netdev in /etc/xen/xend-config.sxp.
>
> Cheers,
> Todd
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Thu, Jun 26, 2008 at 11:12 AM, Asim <linkasim@gmail.com> wrote:> Thanks Todd - These seem to be a wonderful set of debugging steps that I > did not know - but unfortunately I could not catch the error. My eth0 is > working, eth1 is not enabled yet. Is it due to the way my kernel IP routing > table is set? Kindly help. > > > [root@adsl-01 ~]# brctl show > bridge name bridge id STP enabled interfaces > eth0 8000.00e0815caafe no peth0 > eth1 8000.0007e93904bd no peth1 > >Looks like you are now also running Xen 3.2? You should just change your guest configs to use eth0 directly as the bridge and not use xenbr0. Cheers, Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,
I did as mentioned above (used eth0) as my bridge but I am still
unable to ssh from my guest. I get :
[root@fedora_pristine driver]# ssh 128.105.104.102
ssh: connect to host 128.105.104.102 port 22: Network is unreachable
This is the relevant line from my cfg file:
vif = [ ''mac=00:16:3E:6F:CF:77, bridge=eth0'' ]
Output of brctl show:
[root@adsl-02 images]# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.00e0815c75c2 no peth0
vif140.0
eth1 8000.0007e93907e5 no peth1
Please help.
-Asim
On 6/26/08, Todd Deshane <deshantm@gmail.com>
wrote:> On Thu, Jun 26, 2008 at 11:12 AM, Asim <linkasim@gmail.com> wrote:
>
>> Thanks Todd - These seem to be a wonderful set of debugging steps that
I
>> did not know - but unfortunately I could not catch the error. My eth0
is
>> working, eth1 is not enabled yet. Is it due to the way my kernel IP
>> routing
>> table is set? Kindly help.
>>
>>
>> [root@adsl-01 ~]# brctl show
>> bridge name bridge id STP enabled interfaces
>> eth0 8000.00e0815caafe no peth0
>> eth1 8000.0007e93904bd no peth1
>>
>>
> Looks like you are now also running Xen 3.2?
>
> You should just change your guest configs to use eth0 directly as the
bridge
> and not use xenbr0.
>
> Cheers,
> Todd
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
A few questions/comments.. Are you using Xen 3.2? Why are eth0 and eth1 both bridges? in your xend-config.sxp you have two network script lines (network-script ''network-bridge netdev=eth0'') (network-script network-bridge) I think that the second overrides the first, you should only use one, if you want more bridges you should use a custom script. from the guest, do you at least see an eth0 device? what does it think it has for routes? While the guest is running, do a ping or other network traffic and do a trace on the different network cards on dom0 to see if it is being picked up. What version of xen, how installed, what distro, etc.? Cheers, Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks a lot Todd for your response.
Yes, I''m using a Xen 3.2. Its a code that I checked out in May 15 and
built on CentOS 4. The machine(dom0) is connected to internet via
static IP.
eth0 is a bridge. eth1 is an interface that is down currently. I
intend to use eth1 for passthrough I/O but was trying to get bridged
networking working first. I deleted this bridge.
The relevant lines in my sxp are. I''m sorry for the previous
confusion. I corrected it and now sxp looks like:-
(network-script network-bridge netdev=eth0)
(vif-script vif-bridge)
I removed the old bridge. This has made brctl look like:
[root@adsl-02 images]# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.00e0815c75c2 no peth0
vif152.0
At domU:
eth0 Link encap:Ethernet HWaddr 00:16:3E:6F:CF:77
inet6 addr: fe80::216:3eff:fe6f:cf77/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:47866 (46.7 KiB) TX bytes:3204 (3.1 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: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)
[root@fedora_pristine ~]# ping 128.105.104.102
connect: Network is unreachable
[root@fedora_pristine ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
The routing table is empty. The ping returns immediately without doing anything.
Am I missing any steps? Shouldnt the domU creation fix the networking.
Do I need to make any changes to sysconfig/network-scripts/* files?
Thanks,
Asim
On 7/1/08, Todd Deshane <deshantm@gmail.com>
wrote:> A few questions/comments..
>
> Are you using Xen 3.2?
>
> Why are eth0 and eth1 both bridges?
>
> in your xend-config.sxp you have two network script lines
> (network-script ''network-bridge netdev=eth0'')
> (network-script network-bridge)
>
> I think that the second overrides the first, you should only use one,
> if you want more bridges you should use a custom script.
>
> from the guest, do you at least see an eth0 device? what does it
> think it has for routes?
>
> While the guest is running, do a ping or other network traffic and do
> a trace on the different network cards on dom0 to see if it is being
> picked up.
>
> What version of xen, how installed, what distro, etc.?
>
>
> Cheers,
> Todd
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> > > At domU: > > eth0 Link encap:Ethernet HWaddr 00:16:3E:6F:CF:77 > inet6 addr: fe80::216:3eff:fe6f:cf77/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:65 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:47866 (46.7 KiB) TX bytes:3204 (3.1 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: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) > >eth0 in the domU doesn''t have an IP address. It needs one, either static or dhcp. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Todd, I added IPADDR in the ifcfg-eth0 file and it worked. Thanks a lot. -Asim On 7/1/08, Todd Deshane <deshantm@gmail.com> wrote:>> >> >> At domU: >> >> eth0 Link encap:Ethernet HWaddr 00:16:3E:6F:CF:77 >> inet6 addr: fe80::216:3eff:fe6f:cf77/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:65 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:47866 (46.7 KiB) TX bytes:3204 (3.1 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: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) >> >> > eth0 in the domU doesn''t have an IP address. It needs one, either static or > dhcp. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users