similar to: "received packet with own address as source address"

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

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

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

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

Hello. I''ve just started with Xen and configuring Dom0. My hardware is Core2Duo based Xeon server and I installed Debian etch for 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

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, If one sets xend to use network-bridge and there are no bridges already present then it seems that xend will clone eth0 to peth0, create xenbr0 and add peth0 and vif0.0 as ports on that bridge. If on the other hand xenbr0 is created in /etc/network/interfaces then xend will not do any of that peth0 stuff, nor will it add vif0.0 to xenbr0, yet (barring some changes in iptables rules) things

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 have one firewall with 3 ethernet cards, 2 internet links, one cisco 2920 and one problem in RTNETLINK ;o) Let me explain my network : | *** Internet Link 1 *** *** Internet Link 2 *** 10.1.0.1| Serial Serial | 10.2.0.1 |||| +--------------+ +------------+

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

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

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

Hi, I try to get networking running with xen 3.2, but it seems I fail miserably. I am on sles10sp1, with xen 3.2.0, and kernel rpm''s installed from SP2. I configured in /etc/sysconfig/network the NETWORK_LIST: NETWORK_LIST="bridge,0,default,00:DE:AD:BE:EF,192.168.8.13/24,dhcp-off" but an ifconfig xenbr0 still shows the mac address of peth0 fe:ff:ff:ff:ff:ff. Initially, I

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

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,

I''m using xen-3.0.3-64.el5_2.1 on centos 5.2. When I installed centos 5.2 at first time, I could see shared physical device (xenbr0). but after updating virtualization package by yum, it disappeared... connection.py is patched at centos 5.2 release time. so I can''t find out what''s wrong.... bridge configuration is below and it''s normal state.

Hi! I want to forward the port 3389 from the domU to the virtual server with ip address 192.168.122.77 with not success... I tried a lot of iptables rules with no luck so far. Is this possible? I take a look at other post and I don''t found an answer. By example: /sbin/iptables -t nat -A PREROUTING -p tcp -i xenbr0 --dport 3389 -j DNAT --to 192.168.122.77:3389 the virtual nic for the

Hi, I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following: eth0 Link encap:Ethernet

Hi there! I am currently setting up a Xen box on 3 VLans, each VLan interface is in a bridge and currently, dom0 is reachable from on of these and is performing great. My only problem is with domU : it can ping anything but it won''t work for TCP and UDP protocol UNLESS I do a manual tcpdump on my vlan interface. Bridges on dom0: xen-vl97 8000.001372529fbf no

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,