|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] Debian 4.0, domU's can not get network access
HI i' ve tried xen 3.0.4 with etch 4.0 and ive exactly the same problem.
2007/4/15, Nicolai Lang <nicolai@xxxxxxxxxx>:
Hi all,
I have installed a Debian 4.0 (newly released), compiled and installed Xen. All went as I am used to from Ubuntu.
I created a new guest with Debian Etch debootstrap, and it boots without problems. But it can not fetch an IP address from my DHCP server
(10.13.15.1). When I use TCPDump on xenbr0, it only shows the requets being transmitted but nothing is recieved.
I hope I have included all relevant information below, and I hope someone
can help me where to look for the cause. I have searched widely in the Wiki, google and mailinglist.
Once I suceed, I will post an new article on the Wiki with a step-by-step guide to compiling and installing Xen from source on Debian
4.0.
Thank you very much in advance
Best regards Nicolai
root@judas:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61 inet addr:10.13.15.50
Bcast:10.13.15.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:677 errors:0 dropped:0 overruns:0 frame:0
TX packets:522 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:85879 (83.8 KiB) TX bytes:96248 (93.9 KiB) Interrupt:17 Base address:0x6000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 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)
xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
---->We can just notice that when xend start, it don't put the PETH0 and vif0.0 in the bridge Xenbr0, plus we can add that xend don't creat PETH0 and
vif0.0....
maybe a bug with ETCH 4.0.....
root@judas:~# iptables -L
Chain INPUT (policy ACCEPT) target prot opt source destination
Chain FORWARD (policy ACCEPT) target prot opt source destination
Chain OUTPUT (policy ACCEPT) target prot opt source destination
root@judas:~#
Console during startup: Setting up networking.... Configuring network interfaces...Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium.
All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:16:3e:00:01:03 Sending on LPF/eth0/00:16:3e:00:01:03 Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPREQUEST on eth0 to
255.255.255.255 port 67 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 15 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7 No DHCPOFFERS received.
----> No peth0 in the bridge ... so we can't have a network....
After the startup - notice that vifl1.0 and xenbr0 recieves data, but nothing is transmitted
root@judas:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61 inet addr:10.13.15.50 Bcast:10.13.15.255 Mask:
255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:960 errors:0 dropped:0 overruns:0 frame:0 TX packets:826 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:108668 (106.1 KiB) TX bytes:203020 (198.2 KiB) Interrupt:17 Base address:0x6000
lo Link encap:Local Loopback inet addr:127.0.0.1
Mask:255.0.0.0 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)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:15 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:3420 (3.3 KiB) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:15 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:3420 (3.3 KiB) TX bytes:0 (0.0 b)
root@judas:~# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif1.0
deamon.log: Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/770 Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/769 Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/1/0 Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing backend/vbd/1/769/node /dev/loop0 to xenstore. Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing backend/vbd/1/769/physical-device 7:0 to xenstore.
Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing backend/vbd/1/769/hotplug-status connected to xenstore. Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for
vif1.0, bridge xenbr0. Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-status connected to xenstore. Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing backend/vbd/1/770/node /dev/loop1 to xenstore.
Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing backend/vbd/1/770/physical-device 7:1 to xenstore. Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing backend/vbd/1/770/hotplug-status connected to xenstore.
messages: Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers Apr 15 17:16:17 judas kernel: Bridge firewalling registered Apr 15 17:17:45 judas kernel: device vif1.0 entered promiscuous mode Apr 15 17:17:45 judas kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering learning state Apr 15 17:17:49 judas kernel: xenbr0: topology change detected, propagating Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering forwarding
state
xend-debug.log: Xend started at Sun Apr 15 17:16:16 2007. ifdown: interface eth0 not configured SIOCSIFNAME: Device or resource busy
Somebady have found something????
_______________________________________________
Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
-- Benjamin HENRION Elève de 4eme année de l' EXIA (Nancy) Ecole supérieure d'informatique Spé Réseaux
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|