WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] domUs kernel panic on boot

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] domUs kernel panic on boot
From: michael@xxxxxxxxxx
Date: Sun, 14 Jan 2007 20:05:56 -0000 (UTC)
Delivery-date: Sun, 14 Jan 2007 12:05:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: Normal
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.3a
I've been having a problem with newly created domUs kernel panicking when
I start them, below is a copy of the errors I'm getting.  I'm running
CentOS 4.4 with the Xen 3.0.3 RPMS from xensource.com.

Usually when this happens the guest will restart itself and boot normally.
 Any ideas what would cause this?

kernel BUG at arch/i386/mm/hypervisor.c:207!
invalid operand: 0000 [#1]
SMP
Modules linked in:
CPU:    0
EIP:    0061:[<c0115693>]    Not tainted VLI
EFLAGS: 00010282   (2.6.9-42.0.2.EL.xs148xenU)
EIP is at xen_pgd_pin+0x44/0x52
eax: ffffffea   ebx: cfb40ed4   ecx: 00000001   edx: 00000000
esi: 00007ff0   edi: cff352c0   ebp: 00000000   esp: cfb40ed4
ds: 007b   es: 007b   ss: 0068
Process bash (pid: 398, threadinfo=cfb40000 task=cf934c10)
Stack: 00000002 000a6666 0fb42000 cff352c0 001f6840 cff352c0 c0112162
cff35304
       c01121ee cff35304 cfba9ddc c011a68b 0000012c 00000000 cfba9df8
cfba9e00
       cfba9de8 cff35540 cff352c0 cff357b8 cff35538 cff35540 c011a410
fffffff4
       cf9340f0 c13dac40 00000000 00000000 cf9340f0 c011b1a2 cfb40fc4
bfed55f4
Call Trace:
 [<c0112162>] __pgd_pin+0x2a/0x3b
 [<c01121ee>] mm_pin+0x1f/0x2b
 [<c011a68b>] dup_mmap+0x23a/0x28e
 [<c011a410>] copy_mm+0xb9/0xfa
 [<c011b1a2>] copy_process+0x6ae/0xafb
 [<c011b6db>] do_fork+0x8e/0x175
 [<c0126c89>] sigprocmask+0xb0/0xca
 [<c0126dd8>] sys_rt_sigprocmask+0x135/0x145
 [<c0105d37>] sys_clone+0x22/0x26
 [<c025639b>] syscall_call+0x7/0xb
Code: 00 75 0d a1 a4 40 33 c0 8b 04 90 25 ff ff ff 7f 89 44 24 04 89 e3 b9
01 00 00 00 31 d2 be f0 7f 00 00 e8 b1 bc fe ff 85 c0 79 08 <0f> 0b cf 00
e6 c2 26 c0 83 c4 10 5b 5e c3 56 89 c2 c1 ea 0c 53
 <0>Fatal exception: panic in 5 seconds
Kernel panic - not syncing: Fatal exception

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] domUs kernel panic on boot, michael <=