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 ?
Regards
Maciej
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. the following is a way to disable ip checksums *in dom0*; I don''t know whether the same works in domU, but you could give it a try: Set "ip:dohwcksum" to 0 in /etc/system. Reboot, retest, report results. (btw: that means you need to add a line looking like this: set ip:dohwcksum = 0 to /etc/system in your domU) hth -- Michael Schuster Sun Microsystems, Inc. recursion, n: see ''recursion''
michael schuster wrote:> 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. > > the following is a way to disable ip checksums *in dom0*; I don''t know > whether the same works in domU, but you could give it a try: > > Set "ip:dohwcksum" to 0 in /etc/system. Reboot, retest, report results. > > (btw: that means you need to add a line looking like this: > set ip:dohwcksum = 0 > to /etc/system in your domU) > > hthThanks :) it''s works :) Best Regards, Maciej
> 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.
Installing Xen 3.1 SNV76 (75a) DomU at CentOS 5 (Debian Etch 4) Dom0 I still followed SNV66 DomU at Linux Dom0 procedure described for example at http://wiki.tardis.ed.ac.uk/index.php/OpenSolaris_Xen_domU or http://bderzhavets.blogspot.com/2007/09/install-solaris-domu-64-bit-under-xen-3.html. No issues with network. OpenSolaris Guide for SNV76 may be viewed at http://www.opensolaris.org/os/community/xen/docs/linux-dom0/;jsessionid=EA66B0B0B926DD7919450357F1B3E83E Actually, it sounds:- If you''re running at least Xen 3.1, the install step is relatively simple. Create a solaris.py file that reads something like this: <br> name = ''solaris'' <br> memory = ''1024'' <br> disk =[ ''file:/export/isos/snv_76.iso,6:cdrom,r'', ''file:/export/img/solaris.img,0,w'' ] <br> vif = [ '''' ] <br> bootloader = ''pygrub'' <br> kernel = ''/boot/platform/i86xpv/kernel/amd64/unix'' <br> ramdisk = ''/boot/amd64/x86.miniroot'' <br> extra = ''/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom'' <br> I didn''t get a chance to test the most recent instruction above. This message posted from opensolaris.org
Suggested schemas presume that SNV DomU gets static IP address. Otherwise, during initial DomU install you won''t be able drop to shell to "scp" updated boot_archive to Linux Dom0 (after editing /etc/system). In other words we need to update the ramdisk after editing ''/etc/system'' so: bootadm update-archive -R /a and <br> "scp" boot_archive to Linux Dom0. Runtime SNV DomU config file is supposed to have entry:- <br> ramdisk = ''/usr/lib/xen-solaris/boot_archive'' <br> referencing boot_archive been copied to Linux Dom0 <br> before SNV DomU restarts. It worked for SNV66,SNV75a,SNV76. <br> I am not sure that bug is fixed in SNV76 This message posted from opensolaris.org