Re: domU network data payload corruption

[Saku Ytti <saku+xen-devel@ytti.fi>]

On (2006-02-09 18:34 +0200), Saku Ytti wrote:

 
> Also 'ping' command reporting:
> 64 bytes from 10.10.10.101: icmp_seq=13 ttl=64 time=0.268 ms
> wrong data byte #22 should be 0xaa but was 0xff
> #8      aa aa aa aa aa aa aa aa aa aa aa aa aa aa ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff 
> #40     ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
> 
> now if I run 'ping 10.10.10.101 -p ff', there is no problem, packets
> are received without errors. To further prove it 'ping 10.10.10.101 -s 22
> -p aa' is also ok, but 'ping 10.10.10.101 -s 23 -p aa' not anymore, as 
> all bits after that are set '1'.

Bit more information.

 1) changing domU kernel to xen/stable (2.6.12) does not help
 2) it's always 3rd domU where it beings triggered immediately.
    It can be any domU, just it has to be one that is started 3rd.
    Network doesn't work for a second in the 3rd domU.
     2nd and 1st domU continue to work for quite long time, but
    issue can be triggered there too, not sure what's the trigger.

-- 
  ++ytti