[Xen-devel] Re: [xen-discuss] problem with network in domU

[Juergen Keil <jk@xxxxxxxx>]

> Maciej Browarski wrote:
> > Hello,
> > I'm using xen-3.1.2 downloaded today from repository.
> > As dom0 I have linux-kernel 2.6.18 and Debian distro.
> > As domU I install OpenSolaris Nevada 75a.
> > My config file looks:
> > name = 'osdev'
> > memory = '1024'
> > vcpus = 2
> > disk = [ 'file:/mnt/xen/osdev/disk.raw,0,w',  
> > 'file:/mnt/xen/osdev/disk1.raw,1,w' ]
> > vif = [ '' ]
> > on_shutdown = 'destroy'
> > on_reboot = 'destroy'
> > on_crash = 'destroy'
> > 
> > After xm create I see new devices in dom0: peth0, xenbr0 and etc.
> > bash# brctl show
> > xenbr0          8000.feffffffffff       no              vif0.0
> >                                                         peth0
> >                                                         vif3.0
> > So, on dom0 outside network works fine, but on domU I have strange 
> > behavior ( dom0 and domU has addresses from DHCP).
> >  From domU I catch good address. I can also ping outside gateway but 
> > connect with any TCP/UDP ports outside my machine is incorrect (there 
> > are only SYN and SYN/ACK nothing more and timeout).
> > All connection between dom0 and domU works good.
> > Have you any idea what's wrong ?
> 
> sounds a bit like you're having difficulty with checksums.

Yep, see also: 
http://www.opensolaris.org/os/community/xen/docs/linux-dom0/#Networking_failures

Maciej probably has to set the kernel variable "xnf_cksum_offload = 0"
in the solaris domU, so that the linux dom0 network backend driver sends
packets with correct checksums for the solaris domU.


Apparently there are issues with OpenSolaris's xen network frontend driver
checksum offload support, which does not get along with a linux dom0
backend driver.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel