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

RE: [Xen-users] xen 3.1 - domU hangs just after "xm create"


  • To: "Сергей Лукашевич" <lukash33@xxxxxxxxx>
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Tue, 26 Jun 2007 17:47:42 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 26 Jun 2007 08:46:01 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Ace4AfOszw97NADFQ0CuqYCXtuRExgABmqHA
  • Thread-topic: [Xen-users] xen 3.1 - domU hangs just after "xm create"

 

> -----Original Message-----
> From: Сергей Лукашевич [mailto:lukash33@xxxxxxxxx] 
> Sent: 26 June 2007 15:54
> To: Petersson, Mats
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] xen 3.1 - domU hangs just after "xm create"
> 
> 
> After my changing from 'reboot on crash' to 'destroy on 
> crash' the domain is simply crashing every time in a few 
> seconds with the following in the xend.log:
> 
> [2007-06-26 14:25:26 9539] WARNING (XendDomainInfo:1065) 
> Domain has crashed: name=sles id=12.
> 
> Also I have "xm dmesg", "/var/log/messages" and 
> "domain-builder-ng.log" to look at. But nothing suspictious 
> except the following lines in the
> 
> Jun 26 14:21:19 xen-ice /sbin/hotplug[23560]: 
> /etc/hotplug/xen-backend.agent: line 14: sigerr: command not found
> 
> and later on
> 
> 
> Jun 26 14:21:36 xen-ice kernel: irqbalance[3488]: segfault at 
> 0000000000528238 rip 00000000004016ba rsp 00007fff01578ed0 error 4

This is a bit suspicious - maybe you could turn off "irqbalance" just to see if 
it helps - it appears from what I read that it's not really required (it's a 
good idea to have it, but the system should operate without it). 

--
Mats
> 
> 
> How could I guess reasons of the crash please. Will my 
> posting more logs help?
> 
> 
> 
> 25.06.07, 20:45, Petersson, Mats <Mats.Petersson@xxxxxxx> <>:
> 
> > So, the kernel crashes, and when it tries to restart, the 
> old one hasn't gone yet (maybe it never will??). 
> > Not sure what to say here. Obviously, the kernel itself 
> should be fine, as Dom0 works fine. 
> > Not sure what the "solution" refers to either - I guess it 
> says "change the settings for pre-emption model and 
> frequency" to something else - but what I don't really know. 
> > There's nothing that says "this is wrong" in the xend.log 
> as far as I can see (but this is just the last few lines, right?)
> > --
> > Mats
> > [snip lots of logs and old comments]
> 
> 
> 
> 



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


 


Rackspace

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