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-fr

[Xen-fr] Crash Redhat avec Xen 3.0.2.2

To: <xen-fr@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-fr] Crash Redhat avec Xen 3.0.2.2
From: "Dominique Jeannerod" <dominique.jeannerod@xxxxxxxxxx>
Date: Tue, 29 Aug 2006 15:27:46 +0200
Delivery-date: Tue, 29 Aug 2006 06:27:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <3CAAFF45-964F-49F5-AAE9-C800A3A7058E@xxxxxxxxxx>
List-archive: <http://lists.xensource.com/archives/html/xen-fr>
List-help: <mailto:xen-fr-request@lists.xensource.com?subject=help>
List-id: xen-fr.lists.xensource.com
List-post: <mailto:xen-fr@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-fr>, <mailto:xen-fr-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-fr>, <mailto:xen-fr-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-fr@xxxxxxxxxxxxxxxxxxx
Sender: xen-fr-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaV/SI4MdgppSEGRXCr8ltnOvye7w1cSHiA
 
Bonjour,
J'utilise en production sans soucis depuis plusieurs mois deux machines
virtuelles Fedora Core 4 sous Xen 3.0.2.2, sur un domain 0 Redhat Enterprise
Linux 4 Update 3 (Serveur HP DL385).
Les machines virtuelles sont des fichiers, stockés sur une baie Infortrend
accédée en iSCSI avec core-iscsi.
Le serveur vient de crasher, avec les messages suivants dans
/var/log/messages :
Aug 29 14:53:40 sh-prod-01 kernel: ------------[ cut here ]------------
Aug 29 14:53:40 sh-prod-01 kernel: kernel BUG at
arch/i386/mm/hypervisor.c:338!
Aug 29 14:53:40 sh-prod-01 kernel: invalid opcode: 0000 [#2]
Aug 29 14:53:40 sh-prod-01 kernel: SMP
Aug 29 14:53:40 sh-prod-01 kernel: Modules linked in: iscsi_initiator_mod
nfs cpqci nfsd exportfs lockd ipv6 i2c_dev i2c_core sunrpc vfat fat
ip_tables x_tables hw_random amd74xx cciss
Aug 29 14:53:40 sh-prod-01 kernel: CPU:    1
Aug 29 14:53:40 sh-prod-01 kernel: EIP:    0061:[<c0116b52>]    Tainted: P
VLI
Aug 29 14:53:40 sh-prod-01 kernel: EFLAGS: 00010096   (2.6.16-xen0 #3)
Aug 29 14:53:40 sh-prod-01 kernel: EIP is at
xen_create_contiguous_region+0x502/0x520
Aug 29 14:53:40 sh-prod-01 kernel: eax: ffffffff   ebx: 00000006   ecx:
dbb5dd88   edx: 00000001
Aug 29 14:53:40 sh-prod-01 kernel: esi: 00000000   edi: ed679000   ebp:
dbb5ddb4   esp: dbb5dd10
Aug 29 14:53:40 sh-prod-01 kernel: ds: 007b   es: 007b   ss: 0069
Aug 29 14:53:40 sh-prod-01 kernel: Process hpetfe (pid: 30626,
threadinfo=dbb5c000 task=eb859a90)
Aug 29 14:53:40 sh-prod-01 kernel: Stack: <0>c90cae94 dbb5df44 00001000
ed67a000 2d679000 00000000 00000000 00000000
Aug 29 14:53:40 sh-prod-01 kernel:        c15acf20 0002d679 00000001
00000000 00000000 00000000 ed434994 00000000
Aug 29 14:53:40 sh-prod-01 kernel:        c15acf20 c03d5940 00000000
00a8a000 00000000 00a8a067 00000000 00a17000
Aug 29 14:53:40 sh-prod-01 kernel: Call Trace:
Aug 29 14:53:40 sh-prod-01 kernel:  [<c01054fa>]
show_stack_log_lvl+0xaa/0xe0
Aug 29 14:53:40 sh-prod-01 kernel:  [<c010571b>] show_registers+0x19b/0x210
Aug 29 14:53:40 sh-prod-01 kernel:  [<c0105939>] die+0x109/0x1b0
Aug 29 14:53:40 sh-prod-01 kernel:  [<c0105a69>] do_trap+0x89/0xd0
Aug 29 14:53:40 sh-prod-01 kernel:  [<c0105de8>] do_invalid_op+0xb8/0xd0
Aug 29 14:53:40 sh-prod-01 kernel:  [<c010513b>] error_code+0x2b/0x30
Aug 29 14:53:40 sh-prod-01 kernel:  [<c011287b>] pgd_ctor+0x2b/0x40
Aug 29 14:53:40 sh-prod-01 kernel:  [<c01616af>] cache_init_objs+0x5f/0x90
Aug 29 14:53:40 sh-prod-01 kernel:  [<c01618ff>] cache_grow+0x13f/0x1f0
Aug 29 14:53:40 sh-prod-01 kernel:  [<c0161ba8>]
cache_alloc_refill+0x1f8/0x240
Aug 29 14:53:40 sh-prod-01 kernel:  [<c0161e37>] kmem_cache_alloc+0x87/0x90
Aug 29 14:53:40 sh-prod-01 kernel:  [<c01128df>] pgd_alloc+0x1f/0x320
Aug 29 14:53:40 sh-prod-01 kernel:  [<c011c885>] mm_init+0x85/0xb0
Aug 29 14:53:40 sh-prod-01 kernel:  [<c011cb09>] dup_mm+0x59/0x340
Aug 29 14:53:40 sh-prod-01 kernel:  [<c011ce4b>] copy_mm+0x5b/0x80
Aug 29 14:53:40 sh-prod-01 kernel:  [<c011d7a4>] copy_process+0x3b4/0xde0
Aug 29 14:53:41 sh-prod-01 kernel:  [<c011e2ca>] do_fork+0x6a/0x1b0
Aug 29 14:53:41 sh-prod-01 kernel:  [<c0103a19>] sys_clone+0x39/0x40
Aug 29 14:53:41 sh-prod-01 kernel:  [<c0104fa9>] syscall_call+0x7/0xb
Aug 29 14:53:41 sh-prod-01 kernel: Code: b8 24 b6 3e c0 e8 1f 53 26 00 b8 f4
ff ff ff e9 6c fb ff ff 0f 0b 8f 00 64 c9 38 c0 e9 cc fd ff ff 0f 0b 55 01
b2 c4 38 c0 eb ad <0f> 0b 52 01 b2 c4 38 c0 e9 50 ff ff ff 0f 0b 8f 00 64 c9
38 c0

Est-ce que quelqu'un a déjà rencontré ce type de problème ?
Comment diagnostiquer cet incident pour éviter qu'il se reproduise ?

Merci d'avance pour toute suggestion ou piste de réflexion.
Ceci dit, je ne peux pas faire n'importe quel test sur le serveur, étant en
production.

Cordialement,

Dominique JEANNEROD                                +33 (0)6 98 77 87 63
(mobile)
 
mailto:dominique.jeannerod@xxxxxxxxxx
MATRICS Communications


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

<Prev in Thread] Current Thread [Next in Thread>