[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[badly solved] Re: [Xen-devel] Domain status after shutdown command: ---s--



Keir Fraser wrote:
On 14/4/08 07:18, "Dominik Klein" <dk@xxxxxxxxxxxxxxxx> 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

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.