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] RE: FATAL ERROR

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] RE: FATAL ERROR
From: <boualem.ouari@xxxxxxxxxxx>
Date: Sun, 10 Dec 2006 12:40:30 -0500
Delivery-date: Sun, 10 Dec 2006 09:40:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
Thread-index: Acca5zAP6Fkw22aGR9+c/aFO8H6v9gBmuOig
Thread-topic: FATAL ERROR

I finally could started the xen’s kernel with the options nosmp and noapic.

_________________________________________________

Boualem Ouari

Administrateur de systemes Unix/GNU Linux

Connexim Une société en commandite de Bell Canada

Montréal Québec, H2Z 1S4

Tel :       (514) 879-8612

Pagette : (514) 751-8300

 


De : Ouari, Boualem (520330)
Envoyé : 8 décembre 2006 11:38
À : 'xen-users@xxxxxxxxxxxxxxxxxxx'
Objet : FATAL ERROR

 

Hi,

 

I installed the last version of SUSE (LINUX SUSE Enterprise Server 10) with XEN.

When booting the kernel of SUSE ( without XEN) everything starts normally.  

However when I try to start XEN’s Kernel I received the following errors :

 

  (XEN) Xen call trace:

(XEN)    [<ff108ab4>] __qdivrem+0x44/0x4d0

(XEN)    [<ff1125e3>] vsnprintf +0x2e3/0x570

(XEN)    [<ff108f8e>] __divdi3+0x4e/0xa0

(XEN)    [<ff14d179>] calibrate_APIC_clock+0x1c9/0x200

(XEN)    [<ff14d1de>] setup_boot_APIC_clock+0x2e/0x40

(XEN)    [<ff1539a9>] smp_prepare_cpus+0x909/0xd10(XEN)

(XEN)    [<ff134ccd>] intel_p6_mcheck_init+0xbd/0xe0

(XEN)    [<ff1570d4>] get_mtrr_state+0xf4/0x110

(XEN)    [<ff152521>] __start_xen+0x5e1/0x9d0

(XEN)    [<ff124e50>] new_tlbflush_clock_period+0x0/0x40

(XEN)    [<ff10015a>] start_paging+0x52/0x54

(XEN)

(XEN) ************************************

(XEN) CPU0 FATAL TRAP 0 (divide error), ERROR_CODE 0000, IN INTERRUPT CONTEXT.

(XEN) System shutting down -- need manual reset.

(XEN) ************************************

 

 

The server is Proliant DL360 G1 with a CPU Intel PIII 1.2 GHz, 1 Gig of RAM and a Smart Array Integrated Controller (ver 1.50)

 

I created a partition /boot with ID 83 (Linux) formatted ext3 and all others ( / , /usr/local, /tmp,  /var and swap) are in logical volumes formatted ext3 too.

 

Urgent assistance would be greatly appreciated.

 

 

_________________________________________________

Boualem Ouari

Administrateur de systemes Unix/GNU Linux

Connexim Une société en commandite de Bell Canada

Montréal Québec, H2Z 1S4

Tel :       (514) 879-8612

Pagette : (514) 751-8300

 

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] RE: FATAL ERROR, boualem.ouari <=