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

[Xen-users] xend nothing to flush, waiting for peth0 to negotiate



Hi,

I would like to ask concerning problems after installing xen 3.3 on Centos 5.2
I use 2.6.18.8-xen (xen3.3.1 testing - installing with mercurial). After done with make world and make install, I did mkinitrd and placing it in /boot
changing the grub and reboot.. succeded
I do not install libvirt and the domUs from the previous xen 3.0 (built-in Centos 5.2) are NOT able to start :

[root@wing godwing]# /usr/sbin/xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  3919     2     r-----    706.5
[root@wing godwing]# /usr/sbin/xm create -c /etc/xen/balthasar
Using config file "/etc/xen/balthasar".
Error: Boot loader didn't return any data!

While rebooting : xend : nothing to flush... waiting peth0 to negotiate link ? And I find no veth0, veth1, vif[x].[x]
Following I attach the results, thus you might examine:

[root@wing godwing]# /usr/sbin/brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00173f0a7a26       no              peth0
eth1            8000.0019db3895b4       no              peth1
xenbr0          8000.000000000000       no
xenbr1          8000.000000000000       no

note: I don't know why eth0 and eth1 become the bridge??!! The xenbr0 and xenbr1 I built it with brctl addbr, but it won't bridge to eth0. I still can connect to inet (LAN) with it.

[root@wing godwing]# /sbin/ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: peth1: <BROADCAST,MULTICAST,UP,LOWER_
UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:19:db:38:95:b4 brd ff:ff:ff:ff:ff:ff
3: peth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:17:3f:0a:7a:26 brd ff:ff:ff:ff:ff:ff
4: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0
9: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
    link/ether 00:17:3f:0a:7a:26 brd ff:ff:ff:ff:ff:ff
10: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
    link/ether 00:19:db:38:95:b4 brd ff:ff:ff:ff:ff:ff
11: xenbr0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: xenbr1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

[root@wing godwing]# /sbin/ip route show
10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.10
192.168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.10
default via 192.168.200.1 dev eth0


[root@wing godwing]# /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:17:3F:0A:7A:26 
          inet addr:192.168.200.10  Bcast:192.168.200.255  Mask:255.255.255.0
          inet6 addr: fe80::217:3fff:fe0a:7a26/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3773 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1623 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1396281 (1.3 MiB)  TX bytes:323917 (316.3 KiB)

eth1      Link encap:Ethernet  HWaddr 00:19:DB:38:95:B4 
          inet addr:10.0.0.10  Bcast:10.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::219:dbff:fe38:95b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:11061 (10.8 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:1956 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1956 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3253188 (3.1 MiB)  TX bytes:3253188 (3.1 MiB)

peth0     Link encap:Ethernet  HWaddr 00:17:3F:0A:7A:26 
          inet6 addr: fe80::217:3fff:fe0a:7a26/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10258 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7929 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6433117 (6.1 MiB)  TX bytes:1339807 (1.2 MiB)
          Interrupt:18 Base address:0xa000

peth1     Link encap:Ethernet  HWaddr 00:19:DB:38:95:B4 
          inet6 addr: fe80::219:dbff:fe38:95b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:276 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:67479 (65.8 KiB)
          Interrupt:16 Base address:0x4000

sit0      Link encap:IPv6-in-IPv4 
          NOARP  MTU:1480  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)

xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
          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)

xenbr1    Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
          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)

[root@wing godwing]# /etc/xen/scripts/network-bridge status
============================================================
9: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
    link/ether 00:17:3f:0a:7a:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.200.10/24 brd 192.168.200.255 scope global eth0
    inet6 fe80::217:3fff:fe0a:7a26/64 scope link
       valid_lft forever preferred_lft forever
9: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
    link/ether 00:17:3f:0a:7a:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.200.10/24 brd 192.168.200.255 scope global eth0
    inet6 fe80::217:3fff:fe0a:7a26/64 scope link
       valid_lft forever preferred_lft forever
 
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00173f0a7a26       no              peth0
eth1            8000.0019db3895b4       no              peth1
xenbr0          8000.000000000000       no
xenbr1          8000.000000000000       no
 
10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.10
192.168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.10
default via 192.168.200.1 dev eth0
 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth1
192.168.200.0   0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         192.168.200.1   0.0.0.0         UG    0      0        0 eth0
============================================================

[root@wing godwing]# dmesg
Bridge firewalling registered
peth0: link up, 100Mbps, full-duplex, lpa 0x45E1
peth0: Promiscuous mode enabled.
device peth0 entered promiscuous mode
eth0: port 1(peth0) entering learning state
eth0: topology change detected, propagating
eth0: port 1(peth0) entering forwarding state
peth0: Promiscuous mode enabled.
r8169: peth1: link up
device peth1 entered promiscuous mode
eth1: port 1(peth1) entering learning state
eth1: topology change detected, propagating
eth1: port 1(peth1) entering forwarding state
suspend: event channel 23
peth0: no IPv6 routers present
eth0: no IPv6 routers present
peth1: no IPv6 routers present
eth1: no IPv6 routers present
peth0: Promiscuous mode enabled.
peth0: Promiscuous mode enabled.
eth0: port 1(peth0) entering disabled state
peth0: Promiscuous mode enabled.
device peth0 left promiscuous mode
eth0: port 1(peth0) entering disabled state
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth1: port 1(peth1) entering disabled state
device peth1 left promiscuous mode
eth1: port 1(peth1) entering disabled state
r8169: eth1: link up
eth0: no IPv6 routers present
eth1: no IPv6 routers present
peth0: link up, 100Mbps, full-duplex, lpa 0x45E1
peth0: Promiscuous mode enabled.
device peth0 entered promiscuous mode
eth0: port 1(peth0) entering learning state
eth0: topology change detected, propagating
eth0: port 1(peth0) entering forwarding state
peth0: Promiscuous mode enabled.
r8169: peth1: link up
device peth1 entered promiscuous mode
eth1: port 1(peth1) entering learning state
eth1: topology change detected, propagating
eth1: port 1(peth1) entering forwarding state
peth0: Promiscuous mode enabled.
peth0: Promiscuous mode enabled.
eth0: port 1(peth0) entering disabled state
peth0: Promiscuous mode enabled.
device peth0 left promiscuous mode
eth0: port 1(peth0) entering disabled state
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth1: port 1(peth1) entering disabled state
device peth1 left promiscuous mode
eth1: port 1(peth1) entering disabled state
r8169: eth1: link up
peth0: link up, 100Mbps, full-duplex, lpa 0x45E1
peth0: Promiscuous mode enabled.
device peth0 entered promiscuous mode
eth0: port 1(peth0) entering learning state
eth0: topology change detected, propagating
eth0: port 1(peth0) entering forwarding state
r8169: peth1: link up
peth0: Promiscuous mode enabled.
device peth1 entered promiscuous mode
eth1: port 1(peth1) entering learning state
eth1: topology change detected, propagating
eth1: port 1(peth1) entering forwarding state
peth0: no IPv6 routers present
eth0: no IPv6 routers present
peth1: no IPv6 routers present
eth1: no IPv6 routers present

How do I solve this? Would you mind giving me a hand?
Thank you in advance

Best regards.


--
Eric Jansen
CentOS Linuxer
_______________________________________________
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®.