Re: Domain 0 stop response on frequently reboot VMS

[Keir Fraser <keir@xen.org>]

You'll probably want to see if you can get SysRq output from dom0 via serial
line. It's likely you can if it is alive enough to respond to ping. This
might tell you things like what all processes are getting blocked on, and
thus indicate what is stopping dom0 from making progress.

 -- Keir

On 15/10/2010 13:43, "MaoXiaoyun" <tinnycloud@hotmail.com> wrote:

> 
>  Hi Keir:
>  
>          First, I'd like to express my appreciation for the help your offered
> before.
>          Well, recently we confront a rather nasty domain 0 no response
> problem.
>  
>          We still have 12 HVMs almost continuously and concurrently reboot
> test on a physical server.
>          A few hours later, the server looks like dead. We only can ping to
> the server and get right response,
> the Xen works fine since we can get debug info from serial port. Attached is
> the full debug output.
> After decode the domain 0 CPU stack, I find the CPU still works for domain 0
> since the stack changed
> info changed every time I dumped.
>  
>         Could help to take a look at the attentchment to see whether there are
> some hints for debugging this
> problem. Thanks in advance.
>  
>  
>  
>          
> 
>        
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel