From: Paul Larson <plars@linuxtestproject.org>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Strange xend problem shutting down domains
Date: Wed, 02 Mar 2005 12:08:15 -0600 [thread overview]
Message-ID: <1109786895.4911.56.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-03-02 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 18:08 Paul Larson [this message]
2005-03-02 18:56 ` Strange xend problem shutting down domains Nivedita Singhvi
2005-03-02 22:22 ` Paul Larson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1109786895.4911.56.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.