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

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

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] How do I find out why Dom0 crashes on guest startup?
From: "Schober Walter" <Walter.Schober@xxxxxxxxx>
Date: Fri, 18 May 2007 13:06:52 +0200
Cc: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
Delivery-date: Fri, 18 May 2007 04:05:16 -0700
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: AceZOYbSomWpTe1SSGS0aABhqjcWPwAAkfag
Thread-topic: [Xen-users] How do I find out why Dom0 crashes on guest startup?
I have something to confess: I installed qemu (qemu-0.9.0-i386.tar.gz),
too. Needed that qemu-img to convert an raw to a qcow.

Removed all the files from the package now, rebooted then, but still
Dom0 crashes.
The guest crashing the Dom0 is not using that qcow image.

br
Walter

-----Original Message-----
From: Nico Kadel-Garcia [mailto:nkadel@xxxxxxxxx] 
Sent: Friday, May 18, 2007 12:47 PM
To: Schober Walter
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] How do I find out why Dom0 crashes on guest
startup?

Schober Walter wrote:
>
> 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.
>
> System: Centos 5 x86_64 @ HP DL360G5, latest yum update done.
>
> Will attach more info on config, when needed.
>
> Many thanks!
> Walter
>
RHEL 5, and thus CentOS 5, both have auto-updates turned on by default 
with yum-updatesd. I consider this *insane*, since it will patch things 
without a chance to say "hmm, I'm busy today, let's not do that Xen 
kernel patch right now!".

Can you bring up the machine without Xen and check /var/log/rpmpkgs, 
created by /etc/cron.daily/rpm, to check the software you've installed?

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