From: Dominik Klein <dk@in-telegence.net>
To: xen-devel@lists.xensource.com
Subject: [badly solved] Re: Domain status after shutdown command: ---s--
Date: Tue, 22 Apr 2008 13:36:08 +0200 [thread overview]
Message-ID: <480DCDA8.6060008@in-telegence.net> (raw)
In-Reply-To: <C428D973.1F0F3%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 14/4/08 07:18, "Dominik Klein" <dk@in-telegence.net> wrote:
>
>> Dominik Klein wrote:
>>> Keir Fraser wrote:
>>>> What's in the tail of /var/log/xen/xend.log after the domain shuts down?
>>> [2008-04-10 08:12:27 4114] DEBUG (__init__:1072)
>>> XendDomainInfo.shutdown(poweroff)
>>> [2008-04-10 08:12:27 4114] DEBUG (__init__:1072)
>>> XendDomainInfo.handleShutdownWatch
>>> [2008-04-10 08:12:27 4114] DEBUG (__init__:1072)
>>> XendDomainInfo.handleShutdownWatch
>>>
>>> That's all it says after executing the shutdown command.
>> Problem still exists in 3.2.1rc3
>
> I wasn't able to repro this unfortunately. I think the shutdown watch is
> supposed to execute refreshShutdown() and that triggers domain teardown.
> You'll probably have to dig into the code yourself to track this one down.
>
> -- Keir
New information:
The problem exists with
(dom0-cpus 1)
in /etc/xen/xend-config.sxp
This is the requested tail /var/log/xen/xend.log after shutdown (and
CTRL+5).
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices irq.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices vkbd.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices vfb.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices
console.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for 0.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices pci.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices
ioports.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices tap.
[2008-04-22 13:31:28 4203] DEBUG (__init__:1072) Waiting for devices vtpm.
[2008-04-22 13:31:28 4203] INFO (__init__:1072) Domain dktestvmxen (1)
unpaused.
With the default
(dom0-cpus 0)
the problem is gone.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices irq.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices vkbd.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices vfb.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices
console.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for 0.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices pci.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices
ioports.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices tap.
[2008-04-22 13:36:03 4202] DEBUG (__init__:1072) Waiting for devices vtpm.
[2008-04-22 13:36:03 4202] INFO (__init__:1072) Domain dktestvmxen (1)
unpaused.
[2008-04-22 13:36:27 4202] INFO (__init__:1072) Domain has shutdown:
name=dktestvmxen id=1 reason=poweroff.
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) XendDomainInfo.destroy:
domid=1
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072)
XendDomainInfo.destroyDomain(1)
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) Destroying device model
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) Releasing devices
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) Removing vif/0
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) Removing vbd/769
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/769
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) Removing console/0
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) No device model
[2008-04-22 13:36:27 4202] DEBUG (__init__:1072) Releasing devices
Any ideas?
Regards
Dominik
prev parent reply other threads:[~2008-04-22 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 12:34 Domain status after shutdown command: ---s-- Dominik Klein
2008-02-19 13:21 ` Keir Fraser
2008-02-19 13:29 ` Dominik Klein
2008-02-19 14:08 ` Keir Fraser
2008-02-19 14:26 ` Dominik Klein
2008-02-20 9:23 ` Dominik Klein
2008-02-19 14:31 ` Dominik Klein
2008-03-17 15:09 ` Marc Patino Gómez
2008-04-09 14:25 ` Dominik Klein
2008-04-09 14:39 ` Keir Fraser
2008-04-10 6:13 ` Dominik Klein
2008-04-14 6:18 ` Dominik Klein
2008-04-14 8:50 ` Keir Fraser
2008-04-22 11:36 ` Dominik Klein [this message]
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=480DCDA8.6060008@in-telegence.net \
--to=dk@in-telegence.net \
--cc=xen-devel@lists.xensource.com \
/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.