[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Dom0 network problem
Hello. I've just started with Xen and configuring Dom0. My hardware is Core2Duo based Xeon server and I installed Debian etchfor amd64 architecture. The Xen related pachages installed are the following. linux-image-2.6.17-2-xen-amd64 linux-modules-2.6.17-2-xen-amd64 xen-hypervisor-3.0.3-1-amd64 xen-tools xen-utils-3.0.3-1 xen-utils-common My problem is that when xend is configure to have bridge network, Dom0 can not communicate with the external machines. I've not tried the other DomUs yet. (I guess they cannot communicate either.) The related part of xend-config.sxp is the following. (network-script 'network-bridge') (vif-script vif-bridge)If the the above first line is replaced with (network-script network- dummy) then everything works correctly. I appreciate any help to solve this problem. Here are something about status and logs.The routing definition becomes different under the network-bridge. I tried to invoke place a link /etc/rc0.d/S34xend -> /etc/init.d/xend but it did not solve the problem. Under network-bridge # netstat -rn Kernel IP routing tableDestination Gateway Genmask Flags MSS Window irtt Iface 10.140.202.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 0.0.0.0 10.140.203.254 0.0.0.0 UG 0 0 0 eth0 Under network-dummy # netstat -r Kernel IP routing tableDestination Gateway Genmask Flags MSS Window irtt Iface localnet * 255.255.254.0 U 0 0 0 eth0 default 10.140.203.254 0.0.0.0 UG 0 0 0 eth0 From /var/log/messageskernel: eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem ce000000, IRQ 16, node addr 00145e18c59f ... kernel: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex ... kernel: Bridge firewalling registered kernel: device vif0.0 entered promiscuous modekernel: audit(1165827245.987:2): dev=vif0.0 prom=256 old_prom=0 auid=4294967295 kernel: xenbr0: port 1(vif0.0) entering learning state kernel: xenbr0: topology change detected, propagating kernel: xenbr0: port 1(vif0.0) entering forwarding state kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready kernel: bnx2: peth0 NIC Link is Up, 1000 Mbps full duplex kernel: ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready kernel: device peth0 entered promiscuous modekernel: audit(1165827249.211:3): dev=peth0 prom=256 old_prom=0 auid=4294967295 kernel: xenbr0: port 2(peth0) entering learning state kernel: xenbr0: topology change detected, propagating kernel: xenbr0: port 2(peth0) entering forwarding state From /var/log/xen/xen.log[2006-12-11 17:54:04 xend 4490] INFO (__init__:1072) Xend Daemon started [2006-12-11 17:54:04 xend 4490] INFO (__init__:1072) Xend changeset: Tue Oct 17 22:09:52 2006 +0100 .[2006-12-11 17:54:04 xend.XendDomainInfo 4490] DEBUG (__init__:1072) XendDomainI nfo.recreate({'paused': 0, 'cpu_time': 11483528780L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 5021444, 'maxmem_kb': 17179869180, 'max_vcpu_id': 3, 'crash ed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 4, 'blocked': 0})[2006-12-11 17:54:04 xend.XendDomainInfo 4490] INFO (__init__:1072) Recreating d omain 0, UUID 00000000-0000-0000-0000-000000000000.[2006-12-11 17:54:04 xend.XendDomainInfo 4490] WARNING (__init__: 1072) No vm pat h in store for existing domain 0[2006-12-11 17:54:04 xend.XendDomainInfo 4490] DEBUG (__init__:1072) Storing VM details: {'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'xend/rest art_count': '0', 'vcpus': '4', 'vcpu_avail': '3', 'memory': '4904', 'on_crash': 'restart', 'maxmem': '4904'}[2006-12-11 17:54:04 xend.XendDomainInfo 4490] DEBUG (__init__:1072) Storing dom ain details: {'cpu/1/availability': 'online', 'cpu/3/availability': 'offline', ' name': 'Domain-0', 'console/limit': '1048576', 'cpu/2/availability': 'offline', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/ 0/availabil ity': 'online', 'memory/target': '5021696'}[2006-12-11 17:54:04 xend 4490] DEBUG (__init__:1072) number of vcpus to use is 2 [2006-12-11 17:54:05 xend.XendDomainInfo 4490] DEBUG (__init__:1072) XendDomainI nfo.handleShutdownWatch Output of some commnds # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 # ifconfig eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:255.255.254.0 inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:133 errors:0 dropped:0 overruns:0 frame:0 TX packets:60 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:21923 (21.4 KiB) TX bytes:5019 (4.9 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:38 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2880 (2.8 KiB) TX bytes:2880 (2.8 KiB) 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:197 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:27309 (26.6 KiB) TX bytes:5637 (5.5 KiB) Interrupt:16 Memory:ce000000-ce011100 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:60 errors:0 dropped:0 overruns:0 frame:0 TX packets:133 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5019 (4.9 KiB) TX bytes:21923 (21.4 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:187 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:23880 (23.3 KiB) TX bytes:0 (0.0 b) Thank you. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |