This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] kernel BUG !!

To: "Yassine AYACHI" <ayachi.yassine@xxxxxxxxx>, <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] kernel BUG !!
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Tue, 25 Nov 2008 06:30:57 -0700
Delivery-date: Tue, 25 Nov 2008 05:31:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
A few questions:
1) What update of CentOS5 are you using on the host?
2) Are you using the Xen version that came with CentOS5, or have you manually installed another version?
3) What update of RHEL4 are you running as the guest?
4) The kernel version referenced in the error message indicates that you have a pretty old kernel - 2.6.9-42, while the more recent RHEL releases are on 2.6.9-78 (the latest) or 2.6.9-67.  You may want to try booting a minimal system in your domU and updating the kernel to a later version and see if that helps.

>>> "Yassine AYACHI" <ayachi.yassine@xxxxxxxxx> 2008/11/25 06:11 >>>
Hi all,

I'am trying to run a Red Hat Enterprise Linux ES release 4 VM on a centos5 host ... the boot seems gonig without problem, but towards the end I have this error :

------------[ cut here ]------------
kernel BUG at arch/i386/mm/ioremap-xen.c:32!
invalid operand: 0000 [#1]
Modules linked in: md5(U) ipv6(U) autofs4(U) i2c_dev(U) i2c_core(U) sunrpc(U) ib_sdp(U) ib_ipoib(U) rdma_ucm(U) rdma_cm(U) ib_local_sa(U) findex(U) ib_addr(U) ib_uverbs(U) ib_umad(U) ib_ucm(U) ib_sa(U) ib_cm(U) ib_mad(U) ib_core(U) dm_snapshot(U) dm_zero(U) dm_mirror(U) dm_mod(U) ext3(U) jbd(U)
CPU:    0
EIP:    0061:[<c01132e1>]    Not tainted VLI
EFLAGS: 00010206   (2.6.9-42.0.3.EL.xs0.4.0.263xenU)
EIP is at direct_remap_area_pte_fn+0x19/0x6e
eax: d85ae000   ebx: c130b5a0   ecx: e9000003   edx: 50680000
esi: d85ae000   edi: daa72f28   ebp: d85ae000   esp: daa72eb4
ds: 007b   es: 007b   ss: 0068
Process dchcfg32 (pid: 2027, threadinfo=daa72000 task=ddf4cc30)
Stack: c130b5a0 000185ad 00000000 d85ae000 c0149100 daa72f28 b4600000 b460b000
       b460b000 daab7010 dae2b840 00010000 b45fb000 d8590000 00007ff1 c01134b5
       c01132c8 daa72f28 0000000f d8590100 000f0000 000ef025 00000000 b45fb000
       00010000 00000001 000000f0 00010000 dae2b840 d8590050 dac33284 dac33284
Call Trace:
 [<c0149100>] apply_to_page_range+0x197/0x1de
 [<c01134b5>] __direct_remap_pfn_range+0x17f/0x1cf
 [<c01132c8>] direct_remap_area_pte_fn+0x0/0x6e
 [<c01ee811>] xen_mmap_mem+0x4a/0x52
 [<c014be44>] do_mmap_pgoff+0x48c/0x671
 [<c010d987>] sys_mmap2+0x7e/0xaf
 [<c02564f7>] syscall_call+0x7/0xb
 [<c025007b>] unix_stream_sendmsg+0x147/0x33a
Code: 79 fc ff ff 51 e8 04 b4 0a 00 59 e9 6d fc ff ff 90 90 55 57 56 89 c6 53 89 d3 8b 10 8b 7c 24 14 8b 48 04 85 d2 75 04 85 c9 74 08 <0f> 0b 20 00 04 c4 26 c0 89 da 8b 2f 2b 15 50 1a 36 c0 c1 fa 05
 <0>Fatal exception: panic in 5 seconds
Kernel panic - not syncing: Fatal exception

and it reboot indefinitely
someone know what it is ? Thanks in advance 

This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>