DomU stuck in "s" state in -unstable

DomU stuck in "s" state in -unstable

[Christopher S. Aker]

Using yesterday's unstable:

(domU):
INIT: Switching to runlevel: 0
INIT: Sending processes the TERM signal
...
Power down.

Ok, good...

[root@host27 xen]# xm destroy xen8
[root@host27 xen]# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      123    0  r----  33589.1        
xen8              24        0    1  ---s-     43.4    9624


/var/log/xend.log loops the following:

DEBUG (XendDomain:244) XendDomain>reap> domain died name=xen8 id=24
DEBUG (XendDomain:247) XendDomain>reap> shutdown id=24 reason=poweroff
DEBUG (XendDomain:487) domain_restart_schedule> 24 poweroff 0
INFO (XendDomain:564) Destroying domain: name=xen8
DEBUG (XendDomainInfo:673) Closing console, domain 24
INFO (XendRoot:112) EVENT> xend.domain.exit ['xen8', '24', 'poweroff']
INFO (XendRoot:112) EVENT> xend.domain.destroy ['xen8', '24']

-Chris

RE: DomU stuck in "s" state in -unstable

[Ian Pratt]

> [root@host27 xen]# xm destroy xen8
> [root@host27 xen]# xm list
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> Domain-0           0      123    0  r----  33589.1        
> xen8              24        0    1  ---s-     43.4    9624

Yep, this is understood. Mike's preparing a big update to xend
(basically a rewrite) that fixes this and a bunch of other problems.
Stay tuned.

Ian

Re: DomU stuck in "s" state in -unstable

[Christopher S. Aker]

> > [root@host27 xen]# xm destroy xen8
> > [root@host27 xen]# xm list
> > Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> > Domain-0           0      123    0  r----  33589.1
> > xen8              24        0    1  ---s-     43.4    9624
>
> Yep, this is understood. Mike's preparing a big update to xend
> (basically a rewrite) that fixes this and a bunch of other problems.
> Stay tuned.

Cool.  Wasn't sure if this was a xend problem specifically, since vmtools won't
destroy the domain either.

-Chris

Re: DomU stuck in "s" state in -unstable

[Anthony Liguori]

Christopher S. Aker wrote:

>>Yep, this is understood. Mike's preparing a big update to xend
>>(basically a rewrite) that fixes this and a bunch of other problems.
>>Stay tuned.
>>    
>>
>
>Cool.  Wasn't sure if this was a xend problem specifically, since vmtools won't
>destroy the domain either.
>  
>
A domain won't disappear until all of the memory mapped from the domain 
is unmapped.  The culprit here is either xcs or the device backends 
themself.  It's not really harmful to the system to have these domains 
not totally destroyed (most of the memory has been reclaimed) but it is 
annoying.

xcs is pretty good about eventually cleaning itself up so it's probably 
the devices not being properly destroyed.  One of the features I'm 
working on for vm-tools is the ability to remove devices manually (after 
domain destruction).

This will provide a way to recover from this sort of thing in the future.

Regards,
Anthony Liguori

>-Chris
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>