similar to: Dom0 network problem

Hi, I''ve installed xen 3.0.3 from packages (xen-linux-system) on a debian etch, and i''ve configured it with network-bridge script in the default way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me. the problem I have: I cannot ping any outer machine from dom0 (nor any outer machine can ping me). It gives me a "Destination Host Unreachable" message that

Last problem I had involved changing one character in my configuration scripts. Really easy once someone showed me what was wrong. Well I think this issue is just the same. The moment I used apt to install the Xen kernal and tools I lost internet connectivity. I have been managing because I can restore connectivity be deleting the bridge mpower@dodtsair:~$ sudo ifdown eth0

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Before starting xend (xen 3.0) these are my correct network interfaces: eth0 Link encap:Ethernet HWaddr 00:14:5E:0A:53:04 inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:14:5E:0A:53:05 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 lo Link encap:Local Loopback inet

Hi, I have a strange problem with my networking setup. I read all forums around the world where people had similar problems, but couldn''t find a solution. I have an Attansic L1 gigeth chip on my mainboard. This chip works OK in stock Ubuntu Gutsy (development) 2.6.22-9-generic kernel. When I boot into Xen, and after the bridge is created, the network stops working. Some info: - If I

Hello again, folks! I''m getting one strange problem with FC5 running on XEN 3.0.3 x64... The MRTG point to my machine with XEN running one absurd volume of output data sent (normal is around 6 MB/s) and when XEN is working we get 80 MB/s until my DRAC is alive... after this, the machine crash, DRAC stop do reply, swith stop do work together... Anyone knows whats happening now? ;)

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hi All, I am facing an issue regarding communicating a value from outside to a Guest OS (linux, solaris and windows) launched on Xen Server. I did went through this thread, but It was not completely clear. http://lists.xensource.com/archives/html/xen-users/2006-07/msg00473.html My question is - Is there a way in Xen, through which I can communicate a value from outside to a Guest OS (linux,

Hi ! I have install the xen4+centos5 on my server following the post of the kernel version is 2.6.32.27 which is download from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git But after I reboot the server ,and run the "ifconfig", whose output likes the following [root@localhost scripts]# ifconfig eth0 Link encap:Ethernet HWaddr 00:15:C5:EB:96:C3

Hello. I have installed the SuSE Linux 10 XEN kernel but no domU yet. Now I cannot ping to and from dom0. I get lots of ARP broadcasts from dom0 but dom0 seems to ignore ARP answers. When pinging to dom0 it ignores arp requests. This happens regardless xend is running or not. This happens in the xen kernel only, when booting stock kernel all works as expected. What can I do? Robert

hi, i''ve tried again Debian testing, with xen 3.1 binary. it works fine but i can''t have the networt working: i''ve have an ethernet card with static IP: 172.20.2.160 gateway: 172.20.2.1 uname -r :2.6.18-xen without xen, the network works fine. here''s my output: eth0 Lien encap:Ethernet HWaddr 00:0F:FE:6B:57:32 inet adr:172.20.2.160

All is in subject. Example : root@harobed:~ # brctl show bridge name bridge id STP enabled interfaces root@harobed:~ # ifconfig lo Lien encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:H?te UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16510 errors:0 dropped:0 overruns:0 frame:0

I am installed Xen 3.0 on a Fedora Core 4(2.6.12-1.1454_FC4xen0) machine. This machine is currently running one host domain: [root@]# xm list Name Id Mem(MB) CPU VCPU(s) State Time(s) Domain-0 0 128 0 1 r---- 49.1 fc4-vm1 1 63 0 1 -b--- 18.5 Following is the network configuration for Domain-0: eth0 Link

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

Hi, I ''ve got a CentOS 5.2 server running xen 3.0 with 2 DomUs also running CentOS 5.2. All my boxes are up-to date. I''m experiencing trouble with networking. Dom0 can reach the outside world when no DomU are started. It can also reach the outside world when only one DomU is running. The troubles begin when I start the second DomU. At first, this new DomU, called DomU2,

Hi, I''m now blocked for 2 days on getting the network to work in my domU. Here is the problem : The domU refuses to start when a vif is configured. It''s just staying paused for about 1m40s, then the xm create command line give back with an "Error: Device 0 (vif) could not be connected. Hotplug scripts not working.", and the domU is destroyed. Nothing particular

Hi, I''m using Xen 3.0.3 on two servers with Debian Etch (amd64). These servers have 10 nics (2 onboard and 8 in two 4-port cards) so that every vm can have its own interface. This worked so far with the Xen Version from Etch with a wrapper script wich started 10 bridges at boot time. But now I''ve updated Xen on one of these server to Xen 3.2.0 from backports.org and now the

I installed 64-bit xen 3.1.0 (from xensource.com tarballs) on three new machines today, using a configuration setup that I''ve used successfully many times before. However, I encountered a new problem. These are Dell Poweredge 1950 servers, by the way. >From lspci 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet

Hello everybody, Here again with a Xenbr0 bridge problem I''m a Gentoo user, xen-sources-2.6.34 and I always used the bridge from eth0 to xenbr0. Here''s what I get at boot time: * Bringing up interface eth0 * null [...] * Starting Xen control daemon ... And the bridge doesn''t come up. The normal behaviour should be that the Xenbr0 bridge comes up automatically, but