From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [Xen-users] Re: ARP problems with xen 4.0 with pvops kernel 2.6.32.15 Date: Wed, 09 Jun 2010 11:36:04 -0700 Message-ID: <4C0FDF14.5090508@goop.org> References: <20100609125441.GT17817@reaktio.net> <422684.88306.qm@web56101.mail.re3.yahoo.com> <20100609183406.GA17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100609183406.GA17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Boris Derzhavets , xen-devel@lists.xensource.com, luis.silva@axiomasoft.pt, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 06/09/2010 11:34 AM, Pasi K=E4rkk=E4inen wrote: > On Wed, Jun 09, 2010 at 10:46:13AM -0700, Boris Derzhavets wrote: > =20 >> I've captured an exact error message in text virt-install console :- >> ----------------------------------------------------------------------= ----------------------- >> error 2 reading header: cpio: Bad magic >> >> Running anaconda 13.42, the Fedora system installer - please wait. >> ----------------------------------------------------------------------= ---------------------- >> >> =20 > I guess that means the file anaconda downloaded is corrupt.. ie. networ= king is broken. > =20 I would expect that any cpio wrapped up in an rpm would have to go through a number of layers of sha1/md5/signature/etc checking before the cpio header gets checked. If its making its way through that and then finding a bad magic in the cpio, it would seem to be memory or disk corruption. J > -- Pasi > > > =20 >> Boris. >> P.S. Xen 4.0.1-rc2-pre, 2.6.32.15 (the most recent commit) >> >> --- On Wed, 6/9/10, Pasi K=E4rkk=E4inen wrote: >> >> From: Pasi K=E4rkk=E4inen >> Subject: Re: [Xen-users] Re: [Xen-devel] ARP problems with xen 4.0 w= ith pvops kernel >> 2.6.32.15 >> To: "Boris Derzhavets" >> Cc: "Jeremy Fitzhardinge" , xen-devel@lists.xensour= ce.com, >> luis.silva@axiomasoft.pt, xen-users@lists.xensource.com >> Date: Wednesday, June 9, 2010, 8:54 AM >> >> On Wed, Jun 09, 2010 at 05:47:42AM -0700, Boris Derzhavets wrote: >> > I was able to virt-install F13 PV DomU in nographics mode under= Xen >> > 4.0.1-rc2-pre (2.6.32.15 pvops c2cb3df04eb3ff68d0de102b2acacc9b= 8616e659) >> > at the point of extracting data from Apache mirror at Dom0 on t= op of >> > Ubuntu 10.04 ( text console mode message) >> > ------------------------------------------------- >> > 2 extracting cpio errors. Bad Magic >> > ------------------------------------------------- >> > However, virt-install proceeds further to promt "set up VNC at = DomU" >> > and completed successfully. >> > VNC mode cannot pass through this extractions. It just hangs. >> > >> >> Yeah, there's something weird going on.. >> >> During the weekend I *think* I was successfully able to install gues= ts >> when they didn't have vfb set up at all.. but when I set up vfb (ie.= used virt-manager) >> the VM's started acting weird.. network problems, and problems in ge= neral, >> VM's freezing.. >> >> I haven't had time to confirm that yet.. >> >> -- Pasi >> >> > Boris. >> > >> > --- On Mon, 6/7/10, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> wrote= : >> > >> > From: Pasi K=E4rkk=E4inen <[2]pasik@iki.fi> >> > Subject: Re: [Xen-users] Re: [Xen-devel] ARP problems with xe= n 4.0 with >> > pvops kernel 2.6.32.15 >> > To: "Boris Derzhavets" <[3]bderzhavets@yahoo.com> >> > Cc: "Jeremy Fitzhardinge" <[4]jeremy@goop.org>, >> > [5]xen-devel@lists.xensource.com, [6]luis.silva@axiomasoft.pt= , >> > [7]xen-users@lists.xensource.com >> > Date: Monday, June 7, 2010, 3:55 AM >> > >> > On Sun, Jun 06, 2010 at 11:54:11AM -0700, Boris Derzhavets wr= ote: >> > > Virt-install hangs attempting to retrieve updates.img fr= om Apache >> > Mirror >> > > setup at Dom0 >> > > with kernel 2.6.32.15 >> > > It doesn't happen with 2.6.32.10 (12,14 final). >> > > Environment Xen 4.0 Dom0 on top Ubuntu 10.04 Server. Lib= virt is >> > 0.8.0 . >> > > Attempting to virt-install F13 PV DomU in vnc mode. >> > > >> > > I believe that builds are consistent. >> > > Runtime behavior is the same for .10, .14, .15. Seems to= be >> > communicating >> > > problem between DomU and Dom0 during HTTP download. >> > > >> > >> > I'm seeing PV domU network issues aswell.. when running Xen 4= .0.0 on >> > Fedora 13. >> > I'll have to dig more into it.. >> > >> > -- Pasi >> > >> > > Boris. >> > > >> > > --- On Sun, 6/6/10, Jeremy Fitzhardinge <[1][8]jeremy@go= op.org> wrote: >> > > >> > > From: Jeremy Fitzhardinge <[2][9]jeremy@goop.org> >> > > Subject: Re: [Xen-users] Re: [Xen-devel] ARP problems = with xen >> > 4.0 with >> > > pvops kernel 2.6.32.15 >> > > To: "Boris Derzhavets" <[3][10]bderzhavets@yahoo.com> >> > > Cc: [4][11]luis.silva@axiomasoft.pt, >> > [5][12]xen-devel@lists.xensource.com, >> > > [6][13]xen-users@lists.xensource.com >> > > Date: Sunday, June 6, 2010, 12:43 PM >> > > >> > > On 06/06/2010 03:19 AM, Boris Derzhavets wrote: >> > > > Network issues when working with DomUs in 2.6.32.14 = and finally >> > been >> > > > fixed, >> > > > seem to appear again in 2.6.32.15. Reverting to back= to >> > xen/stable - >> > > > 2.6.32.10 >> > > > works as a fix again. >> > > > >> > > >> > > There are no substantial differences between 2.6.32.14= and .15. >> > If >> > > there are any differences in behaviour between them, t= hen I'd >> > suspect >> > > some inconsistency from boot to boot, or in your kerne= l build >> > process. >> > > >> > > J >> > > >> > > > >> > > > Boris >> > > > >> > > > --- On *Thu, 6/3/10, Lu=EDs Silva >> > /<[1][7][14]luis.silva@axiomasoft.pt>/* >> > > wrote: >> > > > >> > > > >> > > > From: Lu=EDs Silva <[2][8][15]luis.silva@axiomas= oft.pt> >> > > > Subject: Re: [Xen-users] Re: [Xen-devel] ARP pro= blems with >> > xen 4.0 >> > > > with pvops kernel >> > > > To: "Boris Derzhavets" <[3][9][16]bderzhavets@ya= hoo.com> >> > > > Cc: "Jeremy Fitzhardinge" <[4][10][17]jeremy@goo= p.org>, >> > > > [5][11][18]xen-devel@lists.xensource.com, >> > [6][12][19]xen-users@lists.xensource.com >> > > > Date: Thursday, June 3, 2010, 6:20 AM >> > > > >> > > > Hello, >> > > > >> > > > Thanks for the suggestion, xen/stable works ok f= or me. Only >> > > > problem is that I have to disable offload do get= dhcp to >> > work on >> > > > domU, but the problem I described before doesn't= exist in >> > this >> > > > kernel. Later today I'm going to try a previous = build I >> > have based >> > > > on stable-2.6.32.x (2.6.32.13) to check if it al= ready had >> > this >> > > > problem or not and I'll post the results. >> > > > >> > > > Lu=EDs >> > > > >> > > > On Wed, 2010-06-02 at 12:26 -0700, Boris Derzhav= ets wrote: >> > > >> Could you,please, build and try 2.6.32.10 ( xen= /stable) ? >> > > >> >> > > >> Boris. >> > > >> >> > > >> --- On *Wed, 6/2/10, Lu=EDs Silva >> > > **/<[7][13][20]luis.silva@axiomasoft.pt>/* >> > > >> wrote: >> > > >> >> > > >> >> > > >> From: Lu=EDs Silva <[8][14][21]luis.silva@a= xiomasoft.pt> >> > > >> Subject: [Xen-users] Re: [Xen-devel] ARP pr= oblems with >> > xen >> > > >> 4.0 with pvops kernel >> > > >> To: "Jeremy Fitzhardinge" <[9][15][22]jerem= y@goop.org> >> > > >> Cc: [10][16][23]xen-devel@lists.xensource.c= om, >> > > [11][17][24]xen-users@lists.xensource.com >> > > >> Date: Wednesday, June 2, 2010, 2:53 PM >> > > >> >> > > >> Hello, >> > > >> >> > > >> On Wed, 2010-06-02 at 09:06 -0700, Jeremy F= itzhardinge >> > wrote: >> > > >>> On 06/02/2010 01:47 AM, Lu=EDs Silva wrote= : >> > > >>> > Hello, >> > > >>> > >> > > >>> > I'm using the latest stable-2.6.32.x. I = already >> > tried >> > > "ethtool -K >> > > >>> > tx off", but that didn't make a= ny >> > difference. >> > > Also, this only >> > > >>> > happen with pv, in hvm mode all works ok= and the >> > domU sees >> > > the arp >> > > >>> > messages... >> > > >>> >> > > >>> Yes, ARP is a new twist on network problem= s. I'm >> > guessing >> > > you're using >> > > >>> hvm without stubdoms, which means that its= networking >> > > originates from >> > > >>> qemu within dom0, whereas PV and HVM+stubd= om comes >> > via >> > > netback. >> > > >>> >> > > >>> >> > > >> Yes, when I mentioned hvm I was talking abo= ut hvm >> > without >> > > >> stubdoms. I haven't tried those yet. >> > > >>> But aside from that, I'm stumped. Are you= running >> > any >> > > firewalls on >> > > >>> either side? Can you try disabling all t= he offloads >> > (tx, >> > > rx, gso, tso) >> > > >>> on all the relevent interfaces (bridge, ne= tback, >> > within the >> > > guest) and >> > > >>> see if that changes anything? >> > > >>> >> > > >>> J >> > > >>> >> > > >>> >> > > >> >> > > >> Ok, this is the bridge interface: >> > > >> >> > > >> brctl show >> > > >> bridge name bridge id STP enabled >> > interfaces >> > > >> virbr0 8000.feffffffffff no = vif1.0 >> > > >> >> > > >> ifconfig virbr0 >> > > >> virbr0 Link encap:Ethernet HWaddr >> > c2:ef:67:2b:a4:23 >> > > >> inet addr:192.168.120.254 >> > Bcast:192.168.120.255 >> > > Mask:255.255.255.0 >> > > >> inet6 addr: fe80::c0ef:67ff:fe2b:= a423/64 >> > Scope:Link >> > > >> UP BROADCAST RUNNING MULTICAST M= TU:1500 >> > Metric:1 >> > > >> RX packets:0 errors:0 dropped:0 o= verruns:0 >> > frame:0 >> > > >> TX packets:25 errors:0 dropped:0 = overruns:0 >> > > carrier:0 >> > > >> collisions:0 txqueuelen:0 >> > > >> RX bytes:0 (0.0 >> > > >> B) >> > > >> TX bytes:4662 (4.6 KB) >> > > >> >> > > >> >> > > >> >> > > >> I'm not using firewall other than the rules= defined by >> > > >> libvirt. DomU has no firewall and the rules= in dom0 >> > are only >> > > >> these (virbr0 is natted to the outside, vir= br1 is >> > routed. The >> > > >> result is the same in either one of them): >> > > >> >> > > >> sudo iptables -L -n -v >> > > >> Chain INPUT (policy ACCEPT 241K packets, 53= M bytes) >> > > >> pkts bytes target prot opt in out = source >> > > destination >> > > >> 0 0 ACCEPT udp -- virbr1 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 udp dpt:53 >> > > >> 0 0 ACCEPT tcp -- virbr1 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 tcp dpt:53 >> > > >> >> > > >> >> > > >> 0 0 ACCEPT udp -- virbr1 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 udp dpt:67 >> > > >> 0 0 ACCEPT tcp -- virbr1 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 tcp dpt:67 >> > > >> 8 515 ACCEPT udp -- virbr0 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 udp dpt:53 >> > > >> 0 0 >> > > >> >> > > >> ACCEPT tcp -- virbr0 * 0.0.0.0= /0 >> > > 0.0.0.0/0 tcp dpt:53 >> > > >> 0 0 ACCEPT udp -- virbr0 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 udp dpt:67 >> > > >> 0 0 ACCEPT tcp -- virbr0 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 tcp dpt:67 >> > > >> >> > > >> Chain FORWARD (policy ACCEPT 0 packets, 0 b= ytes) >> > > >> pkts bytes target >> > > >> prot >> > > >> opt in out source de= stination >> > > >> 0 0 ACCEPT all -- * virb= r1 >> > 0.0.0.0/0 >> > > 192.168.121.0/24 >> > > >> 0 0 ACCEPT all -- virbr1 * >> > > 192.168.121.0/24 0.0.0.0/0 >> > > >> 0 0 ACCEPT all -- virbr1 virb= r1 >> > 0.0.0.0/0 >> > > >> > > >> >> > > >> 0.0.0.0/0 >> > > >> 0 0 REJECT all -- * virb= r1 >> > 0.0.0.0/0 >> > > 0.0.0.0/0 reject-with icmp-port-unreac= hable >> > > >> 0 0 REJECT all -- virbr1 * >> > 0.0.0.0/0 >> > > 0.0.0.0/0 reject-with icmp-port-unreac= hable >> > > >> 13 3448 ACCEPT all -- * virb= r0 >> > 0.0.0.0/0 >> > > 192.168.120.0/24 >> > > >> state >> > > >> RELATED,ESTABLISHED >> > > >> 16 1374 ACCEPT all -- virbr0 * >> > > 192.168.120.0/24 0.0.0.0/0 >> > > >> 0 0 ACCEPT all -- virbr0 virb= r0 >> > 0.0.0.0/0 >> > > 0.0.0.0/0 >> > > >> 0 0 REJECT all -- * virb= r0 >> > 0.0.0.0/0 >> > > 0.0.0.0/0 reject-with icmp-port-unreac= hable >> > > >> 0 0 REJECT all -- >> > > >> virbr0 >> > > >> * 0.0.0.0/0 0.0.0.0/0 >> > reject-with >> > > icmp-port-unreachable >> > > >> >> > > >> Chain OUTPUT (policy ACCEPT 233K packets, 2= 7M bytes) >> > > >> pkts bytes target prot opt in out = source >> > > destination >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> And these are the various offload parameter= s as set at >> > boot: >> > > >> >> > > >> Offload parameters for virbr0: >> > > >> rx-checksumming: on >> > > >> tx-checksumming: on >> > > >> scatter-gather: on >> > > >> tcp-segmentation-offload: on >> > > >> udp-fragmentation-offload: on >> > > >> generic-segmentation-offload: on >> > > >> generic-receive-offload: off >> > > >> large-receive-offload: off >> > > >> >> > > >> Offload parameters for vif1.0: >> > > >> rx-checksumming: on >> > > >> tx-checksumming: on >> > > >> scatter-gather: on >> > > >> tcp-segmentation-offload: on >> > > >> udp-fragmentation-offload: off >> > > >> generic-segmentation-offload: on >> > > >> generic-receive-offload: off >> > > >> large-receive-offload: off >> > > >> >> > > >> Offload parameters for eth0: >> > > >> rx-checksumming: on >> > > >> tx-checksumming: on >> > > >> scatter-gather: on >> > > >> tcp-segmentation-offload: on >> > > >> udp-fragmentation-offload: off >> > > >> generic-segmentation-offload: off >> > > >> generic-receive-offload: off >> > > >> large-receive-offload: off >> > > >> >> > > >> >> > > >> >> > > >> To disable all checksuming I run the follow= ing >> > commands: >> > > >> dom0: >> > > >> >> > > >> sudo ethtool -K virbr0 tx off sg off tso of= f gso off >> > gro off >> > > >> sudo ethtool -K vif1.0 tx off sg off tso of= f gso off >> > gro off >> > > >> >> > > >> >> > > >> domU >> > > >> >> > > >> sudo ethtool -K eth0 tx off sg off tso off = gso off gro >> > off >> > > >> >> > > >> >> > > >> >> > > >> This managed to get all parameter to off in= the >> > mentioned >> > > >> interfaces, but unfortunately the result is= the same. >> > The arp >> > > >> requests get to vif1.0, but not to eth0 on = the domU. >> > > >> >> > > >> sudo tcpdump -i vif1.0 -n -vv arp >> > > >> tcpdump: WARNING: vif1.0: no IPv4 address a= ssigned >> > > >> tcpdump: listening on vif1.0, link-type EN1= 0MB >> > (Ethernet), >> > > capture size 96 bytes >> > > >> 19:43:51.233378 ARP, Ethernet (len 6), IPv4= (len 4), >> > Request >> > > who-has 192.168.120.1 tell 192.168.120.254, length 28 >> > > >> 19:43:52.233164 ARP, Ethernet (len 6), IPv4= (len 4), >> > Request >> > > who-has 192.168.120.1 tell 192.168.120.254, length 28 >> > > >> 19:43:53.233166 ARP, Ethernet (len 6), IPv4= (len 4), >> > Request >> > > who-has 192.168.120.1 tell 192.168.120.254, length 28 >> > > >> 19:43:54.684214 ARP, Ethernet (len 6), IPv4= (len 4), >> > Request >> > > who-has 192.168.120.1 tell 192.168.120.254, length 28 >> > > >> 19:43:55.684218 ARP, Ethernet (len 6), IPv4= (len 4), >> > Request >> > > who-has 192.168.120.1 tell 192.168.120.254, length 28 >> > > >> 19:43:56.684232 ARP, Ethernet (len 6), IPv4= (len 4), >> > Request >> > > who-has 192.168.120.1 tell 192.168.120.254, length 28 >> > > >> >> > > >> >> > > >> >> > > >> I hope this information is enough. If I can= provide >> > anything >> > > >> else to help debug or test, please just ask= ! ;) >> > > >> >> > > >> Thanks in advance, >> > > >> Lu=EDs >> > > >> >> > > >>> > >> > > >>> > Thanks, >> > > >>> > Lu=EDs >> > > >>> > >> > > >>> > On Tue, 2010-06-01 at 18:20 -0700, Jerem= y >> > Fitzhardinge >> > > wrote: >> > > >>> >> On 06/01/2010 05:38 PM, Lu=EDs Silva wr= ote: >> > > >>> >> > Hello, >> > > >>> >> > >> > > >>> >> > Finally I managed to get a xen 4.0 wo= rking on >> > ubuntu >> > > 10.04 with pvops >> > > >>> >> > kernel and libvirt. However I am havi= ng some >> > problems >> > > with >> > > >>> >> > networking... after initial installat= ion with >> > > netinstall image in hvm >> > > >>> >> > mode, when I transform the vm in xen = pv (via >> > pygrub >> > > with the current >> > > >>> >> > ubuntu kernel), networking startEd to= act >> > weird... >> > > >>> >> > >> > > >>> >> > Basically I'm not using a network scr= ipt from >> > xen. I >> > > define a bridge >> > > >>> >> > (manually or via libvirt, the result = is the >> > same) and I >> > > use vif-bridge >> > > >>> >> > to connect the vif to it. But now the= weird part >> > comes: >> > > I can >> > > >>> >> > communicate from domU to dom0, but no= t the other >> > way >> > > >>> around, >> > > >>> unless I >> > > >>> >> > keep a ping running from domU to dom0= ... That's >> > right, >> > > weird... while >> > > >>> >> > trying the ping from dom0 to domU, I = used >> > tcpdump both >> > > on the bridge, >> > > >>> >> > on the vif and on the eth0 in the dom= U. The arp >> > packets >> > > never get to >> > > >>> >> > domU, but they appear both in the bri= dge and the >> > vif >> > > sniff's... >> > > >>> >> >> > > >>> >> What version of kernel are you using in= dom0 and >> > domU? >> > > There was a >> > > >>> >> netback bug which caused problems with = dom0<->domU >> > > communication, but it >> > > >>> >> has been fixed for a while in 2.6.32 (b= ut only >> > recently >> > > in .31). The >> > > >>> >> workaround is to disable tx checksum of= fload on >> > your >> > > bridge (ethtool -K >> > > >>> >> tx off). >> > > >>> >> >> > > >>> >> J >> > > >>> >> >> > > >>> >> > >> > > >>> >> > Here is the bridge: >> > > >>> >> > ifconfig virbr0 >> > > >>> >> > virbr0 Link encap:Ethernet HWaddr >> > > fe:ff:ff:ff:ff:ff >> > > >>> >> > >> > > >>> >> > > >>> inet addr:192.168.120.254 Bcast:192.168.= 120.255 >> > > Mask:255.255.255.0 >> > > >>> >> > inet6 addr: >> > fe80::7cee:4bff:fe82:e63f/64 >> > > Scope:Link >> > > >>> >> > UP BROADCAST RUNNING MULTIC= AST >> > MTU:1500 >> > > Metric:1 >> > > >>> >> > RX packets:16 errors:0 drop= ped:0 >> > overruns:0 >> > > frame:0 >> > > >>> >> > TX packets:226 errors:0 dro= pped:0 >> > overruns:0 >> > > carrier:0 >> > > >>> >> > collisions:0 txqueuelen:0 >> > > >>> >> > RX bytes:952 (952.0 B) TX = bytes:13953 >> > (13.9 >> > > KB) >> > > >>> >> > >> > > >>> >> > >> > > >>> >> > brctl show >> > > >>> >> > bridge name bridge id STP e= nabled >> > > interfaces >> > > >>> >> > virbr0 8000.feffffffffff no >> > vif5.0 >> > > >>> >> > >> > > >>> >> > >> > > >>> >> > tcpdump -i virbr0 -vv -n >> > > >>> >> > tcpdump: listening on virbr0, link-ty= pe EN10MB >> > > (Ethernet), capture size 96 bytes >> > > >>> >> > 01:31:25.945151 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], >> > > >>> proto ICMP (1), >> > > >>> length 84) >> > > >>> >> > 192.168.120.254 > 192.168.120.1: = ICMP echo >> > request, >> > > id 10317, seq 1, length 64 >> > > >>> >> > 01:31:26.945361 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], proto ICMP (1), length 84) >> > > >>> >> > 192.168.120.254 > 192.168.120.1: = ICMP echo >> > request, >> > > id 10317, seq 2, length 64 >> > > >>> >> > 01:31:27.945420 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], proto ICMP (1), length 84) >> > > >>> >> > 192.168.120.254 > 192.168.120.1: = ICMP echo >> > request, >> > > id 10317, seq 3, length 64 >> > > >>> >> > 01:31:28.945362 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], proto ICMP (1), length 84) >> > > >>> >> > 192.168.120.254 > 192.168.120.1: = ICMP echo >> > request, >> > > id 10317, seq 4, length 64 >> > > >>> >> > 01:31:29.945364 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], proto ICMP (1), length 84) >> > > >>> >> > 192.168.120.254 > 192.168.120.1: = ICMP echo >> > request, >> > > id 10317, >> > > >>> seq 5, length >> > > >>> 64 >> > > >>> >> > 01:31:30.944300 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:30.945359 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], proto ICMP (1), length 84) >> > > >>> >> > 192.168.120.254 > 192.168.120.1: = ICMP echo >> > request, >> > > id 10317, seq 6, length 64 >> > > >>> >> > 01:31:31.944297 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:31.945444 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], proto ICMP (1), length 84) >> > > >>> >> > 192.168.120.254 > 192.168.120.1: = ICMP echo >> > request, >> > > id 10317, seq 7, length 64 >> > > >>> >> > 01:31:32.944294 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:32.945401 IP (tos 0x0, ttl 64, = id 0, >> > offset 0, >> > > flags [DF], proto ICMP (1), length 84) >> > > >>> >> > >> > > >>> >> > > >>> 192.168.120.254 > 192.168.120.1: ICMP ech= o request, >> > id >> > > 10317, seq 8, length 64 >> > > >>> >> > 01:31:33.947293 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:34.947373 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:35.947353 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:37.948352 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:38.948399 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:39.948376 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:31:40.949356 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request >> > > >>> who-has >> > > >>> 192.168.120.1 tell 192.168.120.254, lengt= h 28 >> > > >>> >> > >> > > >>> >> > >> > > >>> >> > tcpdump -i vif5.0 -vv -n >> > > >>> >> > tcpdump: WARNING: vif5.0: no IPv4 add= ress >> > assigned >> > > >>> >> > tcpdump: listening on vif5.0, link-ty= pe EN10MB >> > > (Ethernet), capture size 96 bytes >> > > >>> >> > 01:32:19.956358 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:32:20.956358 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:32:21.956359 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:32:23.957311 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:32:24.957312 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth >> > > >>> 28 >> > > >>> >> > >> > > >>> 01:32:25.957359 ARP, Ethernet (len 6), IP= v4 (len 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:32:27.958360 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:32:28.958310 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > 01:32:29.958362 ARP, Ethernet (len 6)= , IPv4 (len >> > 4), >> > > Request who-has 192.168.120.1 tell 192.168.120.254, le= ngth 28 >> > > >>> >> > >> > > >>> >> > >> > > >>> >> > >> > > >>> >> > Forwarding and iptables don't seem to= be the >> > problem, >> > > because if I >> > > >>> >> > initiate a ping from domU (at the sam= e time as >> > the >> > > failing one from >> > > >>> >> > dom0), the ping in dom0 starts to wor= k. As soon >> > as I >> > > stop the ping in >> > > >>> >> > domU, the one in dom0 starts failing = again... >> > > >>> >> > >> > > >>> >> > Is anyone having the same >> > > >>> problem? Is this a bug >> > > >>> in the kernel? In >> > > >>> >> > dom0 or domU? >> > > >>> >> > >> > > >>> >> > Thanks in advance, >> > > >>> >> > Lu=EDs >> > > >>> >> > >> > > >>> >> > >> > > >>> >> > _____________________________________= __________ >> > > >>> >> > Xen-devel mailing list >> > > >>> >> > [12][18][25]Xen-devel@lists.xensource= .com >> > > >> > > >> > > >>> >> > [15][21][28]http://lists.xensource.co= m/xen-devel >> > > >>> >> > >> > > >>> >> >> > > >>> >> >> > > >>> >> _______________________________________= ________ >> > > >>> >> Xen-devel mailing list >> > > >>> >> [16][22][29]Xen-devel@lists.xensource.c= om >> > > >> > > >> > > >>> >> [19][25][32]http://lists.xensource.com/= xen-devel >> > > >>> >> >> > > >>> >> >> > > >>> > >> > > >>> >> > > >>> >> > > >>> >> > > >> >> > > >> >> > > >> >> > > >> -----Inline Attachment Follows----- >> > > >> >> > > >> ___________________________________________= ____ >> > > >> Xen-users mailing list >> > > >> [20][26][33]Xen-users@lists.xensource.com >> > > >> [21][27][34]http://lists.xensource.com/xen-= users >> > > >> >> > > >> >> > > > >> > > > >> > > > -----Inline Attachment Follows----- >> > > > >> > > > _______________________________________________ >> > > > Xen-users mailing list >> > > > [22][28][35]Xen-users@lists.xensource.com >> > > > >> > > > [24][30][37]http://lists.xensource.com/xen-users >> > > > >> > > > >> > > >> > > References >> > > >> > > Visible links >> > > 1. file:///mc/compose?to=3D[31][38]luis.silva@axiomasoft= .pt >> > > 2. file:///mc/compose?to=3D[32][39]luis.silva@axiomasoft= .pt >> > > 3. file:///mc/compose?to=3D[33][40]bderzhavets@yahoo.com >> > > 4. file:///mc/compose?to=3D[34][41]jeremy@goop.org >> > > 5. file:///mc/compose?to=3D[35][42]xen-devel@lists.xenso= urce.com >> > > 6. file:///mc/compose?to=3D[36][43]xen-users@lists.xenso= urce.com >> > > 7. file:///mc/compose?to=3D[37][44]luis.silva@axiomasoft= .pt >> > > 8. file:///mc/compose?to=3D[38][45]luis.silva@axiomasoft= .pt >> > > 9. file:///mc/compose?to=3D[39][46]jeremy@goop.org >> > > 10. file:///mc/compose?to=3D[40][47]xen-devel@lists.xenso= urce.com >> > > 11. file:///mc/compose?to=3D[41][48]xen-users@lists.xenso= urce.com >> > > 12. file:///mc/compose?to=3D[42][49]Xen-devel@lists.xenso= urce.com >> > > 13. file:///mc/compose?to=3D[43][50]Xen-devel@lists.xenso= urce.com >> > > 14. file:///mc/compose?to=3D[44][51]Xen-devel@lists.xenso= urce.com >> > > 15. [45][52]http://lists.xensource.com/xen-devel >> > > 16. file:///mc/compose?to=3D[46][53]Xen-devel@lists.xenso= urce.com >> > > 17. file:///mc/compose?to=3D[47][54]Xen-devel@lists.xenso= urce.com >> > > 18. file:///mc/compose?to=3D[48][55]Xen-devel@lists.xenso= urce.com >> > > 19. [49][56]http://lists.xensource.com/xen-devel >> > > 20. file:///mc/compose?to=3D[50][57]Xen-users@lists.xenso= urce.com >> > > 21. [51][58]http://lists.xensource.com/xen-users >> > > 22. file:///mc/compose?to=3D[52][59]Xen-users@lists.xenso= urce.com >> > > 23. file:///mc/compose?to=3D[53][60]Xen-users@lists.xenso= urce.com >> > > 24. [54][61]http://lists.xensource.com/xen-users >> > >> > > _______________________________________________ >> > > Xen-devel mailing list >> > > [55][62]Xen-devel@lists.xensource.com >> > > [56][63]http://lists.xensource.com/xen-devel >> > >> > _______________________________________________ >> > Xen-devel mailing list >> > [57][64]Xen-devel@lists.xensource.com >> > [58][65]http://lists.xensource.com/xen-devel >> > >> > References >> > >> > Visible links >> > 1. file:///mc/compose?to=3D[66]jeremy@goop.org >> > 2. file:///mc/compose?to=3D[67]jeremy@goop.org >> > 3. file:///mc/compose?to=3D[68]bderzhavets@yahoo.com >> > 4. file:///mc/compose?to=3D[69]luis.silva@axiomasoft.pt >> > 5. file:///mc/compose?to=3D[70]xen-devel@lists.xensource.com >> > 6. file:///mc/compose?to=3D[71]xen-users@lists.xensource.com >> > 7. file:///mc/compose?to=3D[72]luis.silva@axiomasoft.pt >> > 8. file:///mc/compose?to=3D[73]luis.silva@axiomasoft.pt >> > 9. file:///mc/compose?to=3D[74]bderzhavets@yahoo.com >> > 10. file:///mc/compose?to=3D[75]jeremy@goop.org >> > 11. file:///mc/compose?to=3D[76]xen-devel@lists.xensource.com >> > 12. file:///mc/compose?to=3D[77]xen-users@lists.xensource.com >> > 13. file:///mc/compose?to=3D[78]luis.silva@axiomasoft.pt >> > 14. file:///mc/compose?to=3D[79]luis.silva@axiomasoft.pt >> > 15. file:///mc/compose?to=3D[80]jeremy@goop.org >> > 16. file:///mc/compose?to=3D[81]xen-devel@lists.xensource.com >> > 17. file:///mc/compose?to=3D[82]xen-users@lists.xensource.com >> > 18. file:///mc/compose?to=3D[83]Xen-devel@lists.xensource.com >> > 19. file:///mc/compose?to=3D[84]Xen-devel@lists.xensource.com >> > 20. file:///mc/compose?to=3D[85]Xen-devel@lists.xensource.com >> > 21. [86]http://lists.xensource.com/xen-devel >> > 22. file:///mc/compose?to=3D[87]Xen-devel@lists.xensource.com >> > 23. file:///mc/compose?to=3D[88]Xen-devel@lists.xensource.com >> > 24. file:///mc/compose?to=3D[89]Xen-devel@lists.xensource.com >> > 25. [90]http://lists.xensource.com/xen-devel >> > 26. file:///mc/compose?to=3D[91]Xen-users@lists.xensource.com >> > 27. [92]http://lists.xensource.com/xen-users >> > 28. file:///mc/compose?to=3D[93]Xen-users@lists.xensource.com >> > 29. file:///mc/compose?to=3D[94]Xen-users@lists.xensource.com >> > 30. [95]http://lists.xensource.com/xen-users >> > 31. file:///mc/compose?to=3D[96]luis.silva@axiomasoft.pt >> > 32. file:///mc/compose?to=3D[97]luis.silva@axiomasoft.pt >> > 33. file:///mc/compose?to=3D[98]bderzhavets@yahoo.com >> > 34. file:///mc/compose?to=3D[99]jeremy@goop.org >> > 35. file:///mc/compose?to=3D[100]xen-devel@lists.xensource.com >> > 36. file:///mc/compose?to=3D[101]xen-users@lists.xensource.com >> > 37. file:///mc/compose?to=3D[102]luis.silva@axiomasoft.pt >> > 38. file:///mc/compose?to=3D[103]luis.silva@axiomasoft.pt >> > 39. file:///mc/compose?to=3D[104]jeremy@goop.org >> > 40. file:///mc/compose?to=3D[105]xen-devel@lists.xensource.com >> > 41. file:///mc/compose?to=3D[106]xen-users@lists.xensource.com >> > 42. file:///mc/compose?to=3D[107]Xen-devel@lists.xensource.com >> > 43. file:///mc/compose?to=3D[108]Xen-devel@lists.xensource.com >> > 44. file:///mc/compose?to=3D[109]Xen-devel@lists.xensource.com >> > 45. [110]http://lists.xensource.com/xen-devel >> > 46. file:///mc/compose?to=3D[111]Xen-devel@lists.xensource.com >> > 47. file:///mc/compose?to=3D[112]Xen-devel@lists.xensource.com >> > 48. file:///mc/compose?to=3D[113]Xen-devel@lists.xensource.com >> > 49. [114]http://lists.xensource.com/xen-devel >> > 50. file:///mc/compose?to=3D[115]Xen-users@lists.xensource.com >> > 51. [116]http://lists.xensource.com/xen-users >> > 52. file:///mc/compose?to=3D[117]Xen-users@lists.xensource.com >> > 53. file:///mc/compose?to=3D[118]Xen-users@lists.xensource.com >> > 54. [119]http://lists.xensource.com/xen-users >> > 55. file:///mc/compose?to=3D[120]Xen-devel@lists.xensource.com >> > 56. [121]http://lists.xensource.com/xen-devel >> > 57. file:///mc/compose?to=3D[122]Xen-devel@lists.xensource.com >> > 58. [123]http://lists.xensource.com/xen-devel >> >> _______________________________________________ >> Xen-devel mailing list >> [124]Xen-devel@lists.xensource.com >> [125]http://lists.xensource.com/xen-devel >> >> References >> >> Visible links >> 1. file:///mc/compose?to=3Dpasik@iki.fi >> 2. file:///mc/compose?to=3Dpasik@iki.fi >> 3. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 4. file:///mc/compose?to=3Djeremy@goop.org >> 5. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 6. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 7. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 8. file:///mc/compose?to=3Djeremy@goop.org >> 9. file:///mc/compose?to=3Djeremy@goop.org >> 10. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 11. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 12. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 13. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 14. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 15. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 16. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 17. file:///mc/compose?to=3Djeremy@goop.org >> 18. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 19. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 20. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 21. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 22. file:///mc/compose?to=3Djeremy@goop.org >> 23. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 24. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 25. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 26. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 27. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 28. http://lists.xensource.com/xen-devel >> 29. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 30. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 31. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 32. http://lists.xensource.com/xen-devel >> 33. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 34. http://lists.xensource.com/xen-users >> 35. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 36. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 37. http://lists.xensource.com/xen-users >> 38. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 39. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 40. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 41. file:///mc/compose?to=3Djeremy@goop.org >> 42. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 43. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 44. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 45. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 46. file:///mc/compose?to=3Djeremy@goop.org >> 47. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 48. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 49. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 50. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 51. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 52. http://lists.xensource.com/xen-devel >> 53. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 54. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 55. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 56. http://lists.xensource.com/xen-devel >> 57. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 58. http://lists.xensource.com/xen-users >> 59. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 60. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 61. http://lists.xensource.com/xen-users >> 62. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 63. http://lists.xensource.com/xen-devel >> 64. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 65. http://lists.xensource.com/xen-devel >> 66. file:///mc/compose?to=3Djeremy@goop.org >> 67. file:///mc/compose?to=3Djeremy@goop.org >> 68. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 69. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 70. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 71. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 72. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 73. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 74. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 75. file:///mc/compose?to=3Djeremy@goop.org >> 76. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 77. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 78. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 79. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 80. file:///mc/compose?to=3Djeremy@goop.org >> 81. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 82. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 83. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 84. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 85. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 86. http://lists.xensource.com/xen-devel >> 87. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 88. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 89. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 90. http://lists.xensource.com/xen-devel >> 91. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 92. http://lists.xensource.com/xen-users >> 93. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 94. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 95. http://lists.xensource.com/xen-users >> 96. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 97. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 98. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 99. file:///mc/compose?to=3Djeremy@goop.org >> 100. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 101. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 102. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 103. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 104. file:///mc/compose?to=3Djeremy@goop.org >> 105. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 106. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 107. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 108. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 109. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 110. http://lists.xensource.com/xen-devel >> 111. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 112. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 113. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 114. http://lists.xensource.com/xen-devel >> 115. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 116. http://lists.xensource.com/xen-users >> 117. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 118. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 119. http://lists.xensource.com/xen-users >> 120. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 121. http://lists.xensource.com/xen-devel >> 122. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 123. http://lists.xensource.com/xen-devel >> 124. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 125. http://lists.xensource.com/xen-devel >> =20 > =20