[Xen-users] WP Bit kernel panic?

["Anthony G Angerame" <aga1@xxxxxxxxxxxxxx>]

Hello xen folks,

I am running xen 3.0.2 on SUSE SLES 10 on system A and 
SLEX SP1 xen 3.0.4 on system b.
I moved a vm from system a to b and got this kernel panic 
upon booting:


athena:/boot # xm  create -c  vprod
Using config file "/etc/xen/vm/vprod".
Warning: The bootentry option is deprecated.  Use bootargs 
and pass --entry= directly.
Copy kernel /boot/vmlinuz-xenpae from hda2 to 
/var/lib/xen/tmp/kernel.uSo4fI for booting
Started domain vprod
Linux version 2.6.16.27-0.9-xenpae (geeko@buildhost) (gcc 
version 4.1.0 (SUSE Linux)) #1 SMP Tue Feb 13 09:35:18 UTC 
2007
304MB HIGHMEM available.
727MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists
Kernel command line:  TERM=xterm
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Xen reported: 2010.300 MHz processor.
Dentry cache hash table entries: 131072 (order: 7, 524288 
bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 
bytes)
Software IO TLB disabled
vmalloc area: ee000000-f51fe000, maxmem 2d7fe000
Memory: 1025832k/1056768k available (1945k kernel code, 
21948k reserved, 657k data, 176k init, 311304k highmem)
Checking if this processor honours the WP bit even in 
supervisor mode... <1>Unable to handle kernel paging 
request at virtual address c0b81734
 printing eip:
c01133e9
00b0c000 -> *pde = 00000000:819cc001
00b0d000 -> *pme = 00000000:819c6067
00b13000 -> *pte = 00000000:81958061
Oops: 0003 [#1]
SMP
last sysfs file:
Modules linked in:
CPU:    0
EIP:    e019:[<c01133e9>]    Not tainted VLI
EFLAGS: 00010206   (2.6.16.27-0.9-xenpae #1)
EIP is at __set_fixmap+0x2c9/0x3d0
eax: 0d843000   ebx: 0020d843   ecx: 00000000   edx: 
00000002
esi: 00b81730   edi: c0b81730   ebp: 00000b81   esp: 
c038df60
ds: e021   es: e021   ss: e021
Process swapper (pid: 0, threadinfo=c038c000 
task=c032f5c0)
Stack: <0>00000000 00000000 f54e6000 00102000 0d843000 
00000002 00000001 00000000
       00000000 0004c008 00102000 000000b0 00000291 
c039b04c 00000000 00000000
       00102000 00000799 000055bc 00000291 000000b0 
0004c008 00000799 0000156f
Call Trace:
 [<c039b04c>] mem_init+0x38c/0x3f0
 [<c038e635>] start_kernel+0x1b5/0x3a0
 [<c038e210>] unknown_bootoption+0x0/0x270
Code: 3c 89 d8 c1 e8 14 89 ca 09 d0 23 05 04 ab 38 c0 89 
44 24 14 89 d8 8b 54 24 14 c1 e0 0c 0b 44 24 38 23 05 00 
ab 38 c0 89 44 24 10 <89> 57 04 89 86 00 00 00 c0 8b 44 24 
08 e8 f5 35 00 00 e9 ba fe
 <0>Kernel panic - not syncing: Attempted to kill the 
idle task!
 athena:/boot # xm destroy vprod


The hardware on both systems is identical and I have 
previously tried to create a vm under xen 3.0.2 and boot 
it on 3.0.4. Any ideas??

Puzzled,


Tony

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