[Xen-users] Re: Compatibility of different Xen versions ...

[Nigel Head <nigel.head@xxxxxxxxx>]

Resend, because my first attempt seems to have got lost somewhere ...

On 10/2/05, Nigel Head <nigel.head@xxxxxxxxx > wrote:

Oh Gurus of Xen, pray enlighten me ...

How do things go with different releases of Xen between Dom0 and DomU's ... I have a server with the (old) Xen version straight off the SuSE 9.3 distribution. I need to update dom0 (getting one or two kernel 'oops' which I suspect will go away with an upgrade) but, if possible, I'd like to avoid updating the domU kernels/modules etc.

Will all 2.x domU's work with all 2.x dom0's or are there interface changes somewhere in the versions?  Couldn't find any refs to thsi in the Xen site, but if it's there and I'm just too dumb to find it a pointer would be appreciated :-)

Thanks in advance,

--
N.

PS: the actual problem is an Oops at "zap_pte_range+0x171", which I have seen mentioned somewhere as a kernel bug, so  I'm assuming that I need a newer Xen to be able to use a newer kernel ... right? 

It seems to have a predilection for hitting sshd which is getting to be a considerable pain as this server is at a remote location.

Haven't yet done the resarch to see which kernel I need ... need a couple of spare hours which I haven't found yet !



--------------------------------------------------------------------------------------------------------------------------------------

Sep 29 23:24:40 dom0 kernel: Oops: 0003 [#1]
Sep 29 23:24:40 dom0 kernel: Modules linked in: ipt_LOG ipt_limit ipt_pkttype ipt_physdev bridge nvram ipt_state ip6t_REJECT ipt_R
EJECT iptable_mangle iptable_filter ip6table_mangle ip_nat_ftp iptable_nat ip_conntrack_ftp ip_conntrack ip_tables ip6table_filter
 ip6_tables ipv6 edd evdev joydev sg st sd_mod sr_mod scsi_mod video1394 ohci1394 raw1394 ieee1394 capability e100 mii e1000 hw_ra
ndom uhci_hcd ehci_hcd i2c_i801 i2c_core usbcore intel_agp agpgart parport_pc lp parport dm_mod raid1 reiserfs ide_cd cdrom ide_di
sk piix ide_core
Sep 29 23:24:40 dom0 kernel: CPU:    0
Sep 29 23:24:40 dom0 kernel: EIP:    0061:[<c01445f1>]    Not tainted VLI
Sep 29 23:24:40 dom0 kernel: EFLAGS: 00011202   (2.6.11.4-21.8-xen)
Sep 29 23:24:40 dom0 kernel: EIP is at zap_pte_range+0x171/0x350
Sep 29 23:24:40 dom0 kernel: eax: 00000000   ebx: 00227c20   ecx: c1227c20   edx: 2dac2067
Sep 29 23:24:40 dom0 kernel: esi: 00000000   edi: 0002dac2   ebp: d20d9fa4   esp: d11d9e84
Sep 29 23:24:40 dom0 kernel: ds: 007b   es: 007b   ss: 0069
Sep 29 23:24:40 dom0 kernel: Process sshd (pid: 14968, threadinfo=d11d8000 task=d10b4a60)
Sep 29 23:24:40 dom0 kernel: Stack: 00000000 00000020 00000000 00000000 2dac2067 c1227c20 00000000 00001000
Sep 29 23:24:40 dom0 kernel:        b7fe9000 c03930c0 b83e9000 d087bb80 b7fea000 c03930c0 c014481b 00001000
Sep 29 23:24:40 dom0 kernel:        00000000 d10b0780 00000001 b7fe9000 d087bb80 b7fea000 c03930c0 c014487d
Sep 29 23:24:40 dom0 kernel: Call Trace:
Sep 29 23:24:40 dom0 kernel:  [<c014481b>] zap_pmd_range+0x4b/0x70
Sep 29 23:24:40 dom0 kernel:  [<c014487d>] zap_pud_range+0x3d/0x70
Sep 29 23:24:40 dom0 kernel:  [<c0144917>] unmap_page_range+0x67/0x80
Sep 29 23:24:40 dom0 kernel:  [<c0144a24>] unmap_vmas+0xf4/0x230
Sep 29 23:24:40 dom0 kernel:  [<c0149156>] unmap_region+0x76/0xf0
Sep 29 23:24:40 dom0 kernel:  [<c0149426>] do_munmap+0xe6/0x130
Sep 29 23:24:40 dom0 kernel:  [<c01494b0>] sys_munmap+0x40/0x70
Sep 29 23:24:40 dom0 kernel:  [<c0109210>] syscall_call+0x7/0xb
Sep 29 23:24:40 dom0 kernel: Code: 24 14 01 4c 24 14 8b 4c 24 14 8b 01 f6 c4 08 b8 00 00 00 00 0f 44 c1 89 44 24 14 8b 44 24 18 85
 c0 0f 85 e8 00 00 00 85 d2 74 07 <c7> 45 00 00 00 00 00 8b 44 24 24 c7 40 08 01 00 00 00 8b 44 24


N.

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