Re: domU crash

[Ted Kaczmarek <tedkaz@optonline.net>]

On Mon, 2005-10-17 at 15:34 +0200, Stephan Böni wrote:
> 
> > > > > The log you sent shows the domain being successfully created 
> > > > > and unpaused;
> > > > > it should then start to boot.  What happens next?
> > > > 
> > > > Nothing.
> > > > 
> > > > # xm list
> > > > Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> > > > Domain-0           0       251    0      1  r-----     36.1
> > > > inhouse            8      1024    0      1  ------    252.2
> > > 
> > > You have a domain here, and it's already used 252 seconds of 
> > > CPU time, so it's
> > > doing _something_.  Is that time going up rapidly?  Try xm 
> > > list a few times to
> > > find out.  What's on the domain's console (xm console 
> > > inhouse)?  And it's
> > > Ctrl-] to exit the console again.
> > 
> > Oops. I've rebooted the hole system and now it works. :-)
> 
> Bullshit! It works only one time and then i've got the same problem:
> 
> # xm list
> Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> Domain-0           0       251    0      1  r-----     26.4
> inhouse            3      1024    0      1  ------     28.9
> # xm list
> Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> Domain-0           0       251    0      1  r-----     26.5
> inhouse            3      1024    0      1  ------     36.1
> # xm list
> Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> Domain-0           0       251    0      1  r-----     26.8
> inhouse            3      1024    0      1  ------    165.8
> # xm list
> Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> Domain-0           0       251    0      1  r-----     27.0
> inhouse            3      1024    0      1  ------    178.8
> 
> # xm console inhouse
> 
> (nothing displayed!)
> 
> Stephan
> 
Make sure you start the domU in console and have a serial console
connected to xend. You will likely have a better chance of seeing what
is happening.

Regards,
Ted