[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] some domUs work, some dont..??

Hello everybody!

I have the following problem (only _sometimes_) when i create a domU and
start it:

 Linux version 2.6.18-5-xen-686 (Debian 2.6.18.dfsg.1-13etch4)
(dannf@xxxxxxxxxx) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Wed Oct 3 04:02:16 UTC 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000008800000 (usable)
0MB HIGHMEM available.
136MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 34816
Kernel command line: root=/dev/sda2 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Xen reported: 1862.000 MHz processor.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Software IO TLB disabled
vmalloc area: c9000000-f51fe000, maxmem 2d7fe000
Memory: 113704k/139264k available (1579k kernel code, 17212k reserved,
584k data, 148k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
<1>BUG: unable to handle kernel paging request at virtual address c003a72c
 printing eip:
01033000 -> *pde = 00000000:c5b52001
01034000 -> *pme = 00000000:bfb83067
01035000 -> *pte = 00000000:805c2061
Oops: 0003 [#1]
Modules linked in:
CPU:    0
EIP:    e019:[<c01106d6>]    Not tainted VLI
EFLAGS: 00010202   (2.6.18-5-xen-686 #1)
EIP is at __set_fixmap+0x1b0/0x341
eax: 00000001   ebx: 001165f2   ecx: 00000000   edx: ffffffff
esi: c003a728   edi: 0003a728   ebp: 0000003a   esp: c031ff80
ds: e021   es: e021   ss: e021
Process swapper (pid: 0, ti=c031e000 task=c02cf660 task.ti=c031e000)
Stack: 00000000 00000000 f54e5000 f500e000 c5b52001 00000000 00000248
       00000000 00022000 00000094 00000248 c032d869 00000000 00000000
       80000000 c029d33a 0000062b 000010cf c1018000 c0347404 c1012364
Call Trace:
 [<c032d869>] mem_init+0x345/0x392
 [<c032357f>] start_kernel+0x1fb/0x37f
Code: 00 c0 75 0e a1 a8 9c 34 c0 8b 1c 98 81 e3 ff ff ff 7f 8b 4c 24 38
89 d8 c1 e8 14 89 ca 09 d0 8b 15 08 d0 31 c0 23 05 0c d0 31 c0 <89> 46
04 c1 e3 0c 0b 5c 24 34 21 d3 89 9f 00 00 00 c0 e9 63 01
EIP: [<c01106d6>] __set_fixmap+0x1b0/0x341 SS:ESP e021:c031ff80
 <0>Kernel panic - not syncing: Attempted to kill the idle task!

I create those images with the xen-tools and extract them from a .tar
file (different distributions -> sarge, ubuntu). The silly thing is that
this problem comes only sometimes. Most of the times the domUs work
without any problems...Can anybody tell me if this might be a kernel,
xen-tools or xend problem or even how to solve it?

I use xen-tools 3.8; Dom0 hostsystem: Debian etch; Kernel:
vmlinuz-2.6.18-5-xen-686; Xen 3.1 (3.1.0-2). System has enough power and
4gb ram...(use pae-kernel)



Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.