Xen devel - Mar 2005 - Strange xend problem shutting down domains

It seems there''s a problem shutting down the first domain you start in
xen unstable (haven''t tried testing yet).  If I start a domain and try
to shut it down, it never disappears from xm list.  I get a continual
stram of these messages with about a 1 sec delay between each set of
them in xend.log:

[2005-03-02 12:25:00 xend] DEBUG (XendDomain:244) XendDomain>reap>
domain died name=bob13-vm2 id=1
[2005-03-02 12:25:00 xend] DEBUG (XendDomain:247) XendDomain>reap>
shutdown id=1 reason=poweroff
[2005-03-02 12:25:00 xend] DEBUG (XendDomain:487)
domain_restart_schedule> 1 poweroff 0
[2005-03-02 12:25:00 xend] INFO (XendDomain:564) Destroying domain:
name=bob13-vm2
[2005-03-02 12:25:00 xend] DEBUG (XendDomainInfo:651) Closing console,
domain 1
[2005-03-02 12:25:00 xend] INFO (XendRoot:91) EVENT> xend.domain.exit
[''bob13-vm2'', ''1'',
''poweroff'']
[2005-03-02 12:25:00 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy
[''bob13-vm2'', ''1'']

Now, if I start another domain, I can shut it down just fine and it
disappears from the list fine as well.  Anyone seen this before, or have
any ideas about where to look to see what''s going on?

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

Paul Larson wrote:
> It seems there''s a problem shutting down the first domain you
start in
> xen unstable (haven''t tried testing yet).  If I start a domain and
try
> to shut it down, it never disappears from xm list.  I get a continual
> stram of these messages with about a 1 sec delay between each set of
> them in xend.log:
Just as an additional data point, I just saw it last evening too,
testing 0301 unstable, with one domain. However, I did not see
repeated messages (just one set, that looked correct).
> [2005-03-02 12:25:00 xend] DEBUG (XendDomain:244) XendDomain>reap>
> domain died name=bob13-vm2 id=1
xm list did, however, show it to be in S state (shutdown).
Running into other issues at the moment which are preventing
me from further debugging..

One thing to look at (this may be an independent problem) is
that we may not be removing the lockfile appropriately in
every code path going down..

thanks,
Nivedita




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

On Wed, 2005-03-02 at 10:56 -0800, Nivedita Singhvi
wrote:
> Paul Larson wrote:
> 
> > It seems there''s a problem shutting down the first domain you
start in
> > xen unstable (haven''t tried testing yet).  If I start a
domain and try
> > to shut it down, it never disappears from xm list.  I get a continual
> > stram of these messages with about a 1 sec delay between each set of
> > them in xend.log:
> 
> Just as an additional data point, I just saw it last evening too,
> testing 0301 unstable, with one domain. However, I did not see
> repeated messages (just one set, that looked correct).
> 
I just did a quick test with the latest 2.0-testing and it appears that
I can shutdown the first domain just fine with it.  Still investigating.

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org