RE: [Xen-users] How do I find out why Dom0 crashes on guest startup?

["Schober Walter" <Walter.Schober@xxxxxxxxx>]

Thanks Mats! I can do a remote serial console via iLO2 on com2: but
cannot cut&paste from it (Hello HP!) - so I have screenshots only (can
send them on request) ...

Finally it tells me
Panic on CPU 2:
CPU2 FATAL PAGE FAULT
[error_code=0000]
Faulting linear address: 000000000000000

It happens on the 
(XEN) (GUEST: 1) Starting emulated 16-bit real-mode: ip=0600:000

Stack Trace can be sent on request as JPG.

br
Walter

-----Original Message-----
From: Petersson, Mats [mailto:Mats.Petersson@xxxxxxx] 
Sent: Friday, May 18, 2007 12:12 PM
To: Schober Walter; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] How do I find out why Dom0 crashes on guest
startup?

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Schober Walter
> Sent: 18 May 2007 11:08
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] How do I find out why Dom0 crashes on 
> guest startup?
> 
> Before Wednesday all run fine. Then I must have done 
> something - I tried to get rid of those IPMI error messages 
> on starting hpasm, installed the latest RPMs from HP website 
> - but can't tell exactly when it started that the DomU 
> startup crashed my Dom0.
> 
> Anyway ... How can I find out now, what exactly causes my Dom0 
> to crash? Which logs would tell me that? 
> 
> /var/log/messages: Sometimes xenbr changes into forwarding of 
> tap0 before, sometimes not. 
> /var/log/xen/xend.log: The only thing that sounds strange: 
> [2007-05-18 11:56:58 xend 3475] DEBUG (XendDomain:153) number 
> of vcpus to use is 0 
> 
> Meanwhile: hp-OpenIMPI, hpasm, hprsm, cmanic removed, 
> OpenIPMI removed. 
> 
> Still, the Dom0 crashed (just reboots, no output on Display, 
> SSH connection interrupted) on starting a DomU. 

Are you able to get serial output from the server to another machine? 

If so, set xen to use "console=com1 com1=115200,8n1".

If not, try adding "noreboot". 

[Both of these are arguments on the "xen.gz" line in your
/boot/grub/grub.conf]

--
Mats
> 
> System: Centos 5 x86_64 @ HP DL360G5, latest yum update done. 
> 
> Will attach more info on config, when needed. 
> 
> Many thanks! 
> Walter 
> 
> 
> 



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