Domain status after shutdown command: ---s--

Domain status after shutdown command: ---s--

[Dominik Klein]

Hi

this was already on xen-users, but noone could help.

I use Xen 3.2 on debian etch, build from source. domU is also debian etch.

I can create the domain just fine, but when I shut it down, it stays in 
status "---s--" forever until I use "xm destroy".

At first, I put domU on a DRBD disk with the block-drbd script, but I 
also tried with a file-backed domU, which results in the same problem.

The logs do not show any errors. Or at least I cannot see anything that 
looks like an error.

Here's what I see if I shutdown the domain from a console:

debian dktestvmxen:~# halt
Broadcast message from root@dktestvmxen (tty1) (Mon Feb 11 08:32:34 2008):
The system is going down for system halt NOW!
INIT: Switching to runlevel: 0
INIT: Sending processes the TERM signal
Stopping periodic command scheduler: crond.
Stopping internet superserver: inetd.
Stopping OpenBSD Secure Shell server: sshd.
Stopping kernel log daemon: klogd.
Stopping system log daemon: syslogd.
Asking all remaining processes to terminate...done.
Killing all remaining processes...done.
Deconfiguring network interfaces...done.
Cleaning up ifupdown....
Deactivating swap...done.
Will now halt.
md: stopping all md devices.
xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping
System halted.

At this point, the console is locked. If I quit the console with CTRL+5 
and use "xm list", I see

# xm list
Name                                        ID   Mem VCPUs      State 
Time(s)
Domain-0                                     0   256     1     r----- 
37627.4
dktestvmxen                                  1   256     1     ---s--    4.8

Here's my domU config file:

kernel='/boot/vmlinuz-2.6.18.8-xen'
ramdisk='/boot/initrd-2.6.18.8-xen.img'
disk = [ 'file:/dktestvmxen.img,hda1,w' ]
memory = 256
maxmem = 512
builder = 'linux'
name = 'dktestvmxen'
vif = [ 'mac=00:16:3e:13:71:7b,bridge=eth1' ]
localtime = 0
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
root = '/dev/hda1'
extra='TERM=xterm xencons=tty console=tty1'

This also happens if I shutdown the domain with "shutdown -hP now" or 
"xm shutdown $domid" from dom0.

Any help would be much appreciated.

Regards
Dominik

Re: Domain status after shutdown command: ---s--

[Keir Fraser]

What does /var/log/xen/xend.log say? Do you have a line like 'on_poweroff =
destroy' in your domain config file?

 -- Keir

On 19/2/08 12:34, "Dominik Klein" <dk@in-telegence.net> wrote:

> Hi
> 
> this was already on xen-users, but noone could help.
> 
> I use Xen 3.2 on debian etch, build from source. domU is also debian etch.
> 
> I can create the domain just fine, but when I shut it down, it stays in
> status "---s--" forever until I use "xm destroy".
> 
> At first, I put domU on a DRBD disk with the block-drbd script, but I
> also tried with a file-backed domU, which results in the same problem.
> 
> The logs do not show any errors. Or at least I cannot see anything that
> looks like an error.
> 
> Here's what I see if I shutdown the domain from a console:
> 
> debian dktestvmxen:~# halt
> Broadcast message from root@dktestvmxen (tty1) (Mon Feb 11 08:32:34 2008):
> The system is going down for system halt NOW!
> INIT: Switching to runlevel: 0
> INIT: Sending processes the TERM signal
> Stopping periodic command scheduler: crond.
> Stopping internet superserver: inetd.
> Stopping OpenBSD Secure Shell server: sshd.
> Stopping kernel log daemon: klogd.
> Stopping system log daemon: syslogd.
> Asking all remaining processes to terminate...done.
> Killing all remaining processes...done.
> Deconfiguring network interfaces...done.
> Cleaning up ifupdown....
> Deactivating swap...done.
> Will now halt.
> md: stopping all md devices.
> xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping
> System halted.
> 
> At this point, the console is locked. If I quit the console with CTRL+5
> and use "xm list", I see
> 
> # xm list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0   256     1     r-----
> 37627.4
> dktestvmxen                                  1   256     1     ---s--    4.8
> 
> Here's my domU config file:
> 
> kernel='/boot/vmlinuz-2.6.18.8-xen'
> ramdisk='/boot/initrd-2.6.18.8-xen.img'
> disk = [ 'file:/dktestvmxen.img,hda1,w' ]
> memory = 256
> maxmem = 512
> builder = 'linux'
> name = 'dktestvmxen'
> vif = [ 'mac=00:16:3e:13:71:7b,bridge=eth1' ]
> localtime = 0
> on_poweroff = 'destroy'
> on_reboot = 'restart'
> on_crash = 'restart'
> root = '/dev/hda1'
> extra='TERM=xterm xencons=tty console=tty1'
> 
> This also happens if I shutdown the domain with "shutdown -hP now" or
> "xm shutdown $domid" from dom0.
> 
> Any help would be much appreciated.
> 
> Regards
> Dominik
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Domain status after shutdown command: ---s--

[Dominik Klein]

Hi Keir,

thanks for your reply.

Keir Fraser wrote:
> What does /var/log/xen/xend.log say? 

This is what it says on startup of the domain:

[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) 
XendDomainInfo.create(['vm', ['name', 'dktestvmxen'], ['memory', 256], 
['maxmem', 512], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], 
['on_crash', 'restart'], ['vcpus', 1], ['on_xend_start', 'ignore'], 
['on_xend_stop', 'ignore'], ['image', ['linux', ['kernel', 
'/boot/vmlinuz-2.6.18.8-xen'], ['ramdisk', 
'/boot/initrd-2.6.18.8-xen.img'], ['root', '/dev/hda1'], ['args', 
'TERM=xterm xencons=tty console=tty1']]], ['device', ['vbd', ['uname', 
'file:/dktestvmxen.img'], ['dev', 'hda1'], ['mode', 'w']]], ['device', 
['vif', ['bridge', 'eth1'], ['mac', '00:16:3e:13:71:7b']]]])
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) 
XendDomainInfo.constructDomain
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Balloon: 1286904 KiB 
free; need 2048; done.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Adding Domain: 2
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) 
XendDomainInfo.initDomain: 2 256
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) 
_initDomain:shadow_memory=0x0, memory_static_max=0x20000000, 
memory_static_min=0x0.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Balloon: 1286904 KiB 
free; need 262144; done.
[2008-02-19 14:26:16 3967] INFO (__init__:1072) buildDomain os=linux 
dom=2 vcpus=1
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) domid          = 2
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) memsize        = 256
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) image          = 
/boot/vmlinuz-2.6.18.8-xen
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) store_evtchn   = 1
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) console_evtchn = 2
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) cmdline        = 
root=/dev/hda1 TERM=xterm xencons=tty console=tty1
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) ramdisk        = 
/boot/initrd-2.6.18.8-xen.img
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) vcpus          = 1
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) features       =
[2008-02-19 14:26:16 3967] INFO (__init__:1072) createDevice: vbd : 
{'uuid': '76719195-8e36-9129-a6f0-bbe8ec8d3ea0', 'bootable': 1, 
'driver': 'paravirtualised', 'dev': 'hda1', 'uname': 
'file:/dktestvmxen.img', 'mode': 'w'}
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) DevController: writing 
{'virtual-device': '769', 'device-type': 'disk', 'protocol': 
'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/2/769'} to /local/domain/2/device/vbd/769.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) DevController: writing 
{'domain': 'dktestvmxen', 'frontend': '/local/domain/2/device/vbd/769', 
'uuid': '76719195-8e36-9129-a6f0-bbe8ec8d3ea0', 'dev': 'hda1', 'state': 
'1', 'params': '/dktestvmxen.img', 'mode': 'w', 'online': '1', 
'frontend-id': '2', 'type': 'file'} to /local/domain/0/backend/vbd/2/769.
[2008-02-19 14:26:16 3967] INFO (__init__:1072) createDevice: vif : 
{'bridge': 'eth1', 'mac': '00:16:3e:13:71:7b', 'uuid': 
'b584940b-0281-92cb-570e-65bed687fdcd'}
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) DevController: writing 
{'mac': '00:16:3e:13:71:7b', 'handle': '0', 'protocol': 'x86_32-abi', 
'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vif/2/0'} to /local/domain/2/device/vif/0.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) DevController: writing 
{'bridge': 'eth1', 'domain': 'dktestvmxen', 'handle': '0', 'uuid': 
'b584940b-0281-92cb-570e-65bed687fdcd', 'script': 
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': 
'/local/domain/2/device/vif/0', 'mac': '00:16:3e:13:71:7b', 'online': 
'1', 'frontend-id': '2'} to /local/domain/0/backend/vif/2/0.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Storing VM details: 
{'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': 
'a6c4c40d-575d-6663-2ada-3fc912c13bbd', 'on_reboot': 'restart', 
'start_time': '1203427576.68', 'on_poweroff': 'destroy', 
'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': 
'0', 'vcpus': '1', 'vcpu_avail': '1', 'image': "(linux (kernel 
/boot/vmlinuz-2.6.18.8-xen) (ramdisk /boot/initrd-2.6.18.8-xen.img) 
(args 'root=/dev/hda1 TERM=xterm xencons=tty console=tty1') (notes 
(HV_START_LOW 4118806528) (FEATURES 
'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel') 
(VIRT_BASE 3221225472) (GUEST_VERSION 2.6) (PADDR_OFFSET 3221225472) 
(GUEST_OS linux) (HYPERCALL_PAGE 3222278144) (LOADER generic) 
(SUSPEND_CANCEL 1) (PAE_MODE yes) (ENTRY 3222274048) (XEN_VERSION 
xen-3.0)))", 'name': 'dktestvmxen'}
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Storing domain details: 
{'console/ring-ref': '327709', 'image/entry': '3222274048', 
'console/port': '2', 'store/ring-ref': '327710', 'image/loader': 
'generic', 'vm': '/vm/a6c4c40d-575d-6663-2ada-3fc912c13bbd', 
'control/platform-feature-multiprocessor-suspend': '1', 
'image/hv-start-low': '4118806528', 'image/guest-os': 'linux', 
'image/features/writable-descriptor-tables': '1', 'image/virt-base': 
'3221225472', 'memory/target': '262144', 'image/guest-version': '2.6', 
'image/features/supervisor-mode-kernel': '1', 'image/pae-mode': 'yes', 
'console/limit': '1048576', 'image/paddr-offset': '3221225472', 
'image/hypercall-page': '3222278144', 'image/suspend-cancel': '1', 
'cpu/0/availability': 'online', 'image/features/pae-pgdir-above-4gb': 
'1', 'image/features/writable-page-tables': '1', 'console/type': 
'xenconsoled', 'image/features/auto-translated-physmap': '1', 'name': 
'dktestvmxen', 'domid': '2', 'image/xen-version': 'xen-3.0', 
'store/port': '1'}
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) DevController: writing 
{'protocol': 'x86_32-abi', 'state': '1', 'backend-id': '0', 'backend': 
'/local/domain/0/backend/console/2/0'} to /local/domain/2/device/console/0.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) DevController: writing 
{'domain': 'dktestvmxen', 'protocol': 'vt100', 'uuid': 
'ed49aec0-415e-291c-3273-6b3c94806174', 'frontend': 
'/local/domain/2/device/console/0', 'state': '1', 'location': '2', 
'online': '1', 'frontend-id': '2'} to /local/domain/0/backend/console/2/0.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) 
XendDomainInfo.handleShutdownWatch
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices vif.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for 0.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vif/2/0/hotplug-status.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices vbd.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for 769.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/2/769/hotplug-status.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/2/769/hotplug-status.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices irq.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices vkbd.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices vfb.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices 
console.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for 0.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices pci.
[2008-02-19 14:26:16 3967] DEBUG (__init__:1072) Waiting for devices 
ioports.
[2008-02-19 14:26:17 3967] DEBUG (__init__:1072) Waiting for devices tap.
[2008-02-19 14:26:17 3967] DEBUG (__init__:1072) Waiting for devices vtpm.
[2008-02-19 14:26:17 3967] INFO (__init__:1072) Domain dktestvmxen (2) 
unpaused.

When I shutdown the domain, xend.log does not show anything.

> Do you have a line like 'on_poweroff =
> destroy' in your domain config file?

As you could see in my email: yes, I have that line.

>> Here's my domU config file:
>>
>> kernel='/boot/vmlinuz-2.6.18.8-xen'
>> ramdisk='/boot/initrd-2.6.18.8-xen.img'
>> disk = [ 'file:/dktestvmxen.img,hda1,w' ]
>> memory = 256
>> maxmem = 512
>> builder = 'linux'
>> name = 'dktestvmxen'
>> vif = [ 'mac=00:16:3e:13:71:7b,bridge=eth1' ]
>> localtime = 0
>> on_poweroff = 'destroy'
>> on_reboot = 'restart'
>> on_crash = 'restart'
>> root = '/dev/hda1'
>> extra='TERM=xterm xencons=tty console=tty1'

Regards
Dominik

Re: Domain status after shutdown command: ---s--

[Keir Fraser]

On 19/2/08 13:29, "Dominik Klein" <dk@in-telegence.net> wrote:

> When I shutdown the domain, xend.log does not show anything.

You should get a line something like "Domain has shutdown: ...". For some
reason that handler inside xend has not been invoked, which is odd since
xend is aware enough the domain has shutdown since 'xm list' displays it in
state 's'. You'll probably have to add some tracing to xend, and possibly
also to xenstored which is the entity responsible for notifying xend about
domain shutdown, to work out where the notification is getting lost.

 -- Keir

Re: Domain status after shutdown command: ---s--

[Dominik Klein]

> You should get a line something like "Domain has shutdown: ...". For some
> reason that handler inside xend has not been invoked, which is odd since
> xend is aware enough the domain has shutdown since 'xm list' displays it in
> state 's'. You'll probably have to add some tracing to xend, and possibly
> also to xenstored which is the entity responsible for notifying xend about
> domain shutdown, to work out where the notification is getting lost.

I tried to start xend with strace, but then I cannot start any domains 
(xm says "is xend running?").

How could I trace otherwise? I only know strace. Sorry

Is there an IRC channel for xen? Maybe we could be faster that way.

Regards
Dominik

Re: Domain status after shutdown command: ---s--

[Dominik Klein]

> When I shutdown the domain, xend.log does not show anything.

Hm, just found that that's not exactly true.

It does not show anything if I use "halt" or "shutdown" in domU.

But it does show this when executin "xm shutdown" in dom0.

[2008-02-19 15:29:44 3902] DEBUG (__init__:1072) 
XendDomainInfo.shutdown(poweroff)
[2008-02-19 15:29:44 3902] DEBUG (__init__:1072) 
XendDomainInfo.handleShutdownWatch
[2008-02-19 15:29:44 3902] DEBUG (__init__:1072) 
XendDomainInfo.handleShutdownWatch

The status remains the same though.

Regards
Dominik

Re: Domain status after shutdown command: ---s--

[Dominik Klein]

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

Keir Fraser wrote:
> On 19/2/08 13:29, "Dominik Klein" <dk@in-telegence.net> wrote:
> 
>> When I shutdown the domain, xend.log does not show anything.
> 
> You should get a line something like "Domain has shutdown: ...". For some
> reason that handler inside xend has not been invoked, which is odd since
> xend is aware enough the domain has shutdown since 'xm list' displays it in
> state 's'. You'll probably have to add some tracing to xend, and possibly
> also to xenstored which is the entity responsible for notifying xend about
> domain shutdown, to work out where the notification is getting lost.

Attached are strace logs. I attached strace to the xenstored and xend 
processes.

I started the domain, waited a couple seconds, ran "halt" from inside 
the domain and then in the end use "xm destroy" from dom0.

Regards
Dominik

[-- Attachment #2: strace.bz2 --]
[-- Type: application/x-bzip, Size: 103234 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Domain status after shutdown command: ---s--

[Marc Patino Gómez]

Hi all,

I have the same problem, I'm using also Debian Etch on AMD64 and Xen 
3.2.0 builded from sources. At the moment, I am trying to find a 
solution for this issue.

Regards,

Marc

Dominik Klein wrote:
> Hi
>
> this was already on xen-users, but noone could help.
>
> I use Xen 3.2 on debian etch, build from source. domU is also debian 
> etch.
>
> I can create the domain just fine, but when I shut it down, it stays 
> in status "---s--" forever until I use "xm destroy".
>
> At first, I put domU on a DRBD disk with the block-drbd script, but I 
> also tried with a file-backed domU, which results in the same problem.
>
> The logs do not show any errors. Or at least I cannot see anything 
> that looks like an error.
>
> Here's what I see if I shutdown the domain from a console:
>
> debian dktestvmxen:~# halt
> Broadcast message from root@dktestvmxen (tty1) (Mon Feb 11 08:32:34 
> 2008):
> The system is going down for system halt NOW!
> INIT: Switching to runlevel: 0
> INIT: Sending processes the TERM signal
> Stopping periodic command scheduler: crond.
> Stopping internet superserver: inetd.
> Stopping OpenBSD Secure Shell server: sshd.
> Stopping kernel log daemon: klogd.
> Stopping system log daemon: syslogd.
> Asking all remaining processes to terminate...done.
> Killing all remaining processes...done.
> Deconfiguring network interfaces...done.
> Cleaning up ifupdown....
> Deactivating swap...done.
> Will now halt.
> md: stopping all md devices.
> xenbus_dev_shutdown: device/console/0: Initialising != Connected, 
> skipping
> System halted.
>
> At this point, the console is locked. If I quit the console with 
> CTRL+5 and use "xm list", I see
>
> # xm list
> Name                                        ID   Mem VCPUs      State 
> Time(s)
> Domain-0                                     0   256     1     r----- 
> 37627.4
> dktestvmxen                                  1   256     1     
> ---s--    4.8
>
> Here's my domU config file:
>
> kernel='/boot/vmlinuz-2.6.18.8-xen'
> ramdisk='/boot/initrd-2.6.18.8-xen.img'
> disk = [ 'file:/dktestvmxen.img,hda1,w' ]
> memory = 256
> maxmem = 512
> builder = 'linux'
> name = 'dktestvmxen'
> vif = [ 'mac=00:16:3e:13:71:7b,bridge=eth1' ]
> localtime = 0
> on_poweroff = 'destroy'
> on_reboot = 'restart'
> on_crash = 'restart'
> root = '/dev/hda1'
> extra='TERM=xterm xencons=tty console=tty1'
>
> This also happens if I shutdown the domain with "shutdown -hP now" or 
> "xm shutdown $domid" from dom0.
>
> Any help would be much appreciated.
>
> Regards
> Dominik
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Domain status after shutdown command: ---s--

[Dominik Klein]

So I'm not alone with that problem.

I just tested with 3.2.1rc3 and the problem persists.

Regards
Dominik

Marc Patino Gómez wrote:
> Hi all,
> 
> I have the same problem, I'm using also Debian Etch on AMD64 and Xen 
> 3.2.0 builded from sources. At the moment, I am trying to find a 
> solution for this issue.
> 
> Regards,
> 
> Marc
> 
> Dominik Klein wrote:
>> Hi
>>
>> this was already on xen-users, but noone could help.
>>
>> I use Xen 3.2 on debian etch, build from source. domU is also debian 
>> etch.
>>
>> I can create the domain just fine, but when I shut it down, it stays 
>> in status "---s--" forever until I use "xm destroy".
>>
>> At first, I put domU on a DRBD disk with the block-drbd script, but I 
>> also tried with a file-backed domU, which results in the same problem.
>>
>> The logs do not show any errors. Or at least I cannot see anything 
>> that looks like an error.
>>
>> Here's what I see if I shutdown the domain from a console:
>>
>> debian dktestvmxen:~# halt
>> Broadcast message from root@dktestvmxen (tty1) (Mon Feb 11 08:32:34 
>> 2008):
>> The system is going down for system halt NOW!
>> INIT: Switching to runlevel: 0
>> INIT: Sending processes the TERM signal
>> Stopping periodic command scheduler: crond.
>> Stopping internet superserver: inetd.
>> Stopping OpenBSD Secure Shell server: sshd.
>> Stopping kernel log daemon: klogd.
>> Stopping system log daemon: syslogd.
>> Asking all remaining processes to terminate...done.
>> Killing all remaining processes...done.
>> Deconfiguring network interfaces...done.
>> Cleaning up ifupdown....
>> Deactivating swap...done.
>> Will now halt.
>> md: stopping all md devices.
>> xenbus_dev_shutdown: device/console/0: Initialising != Connected, 
>> skipping
>> System halted.
>>
>> At this point, the console is locked. If I quit the console with 
>> CTRL+5 and use "xm list", I see
>>
>> # xm list
>> Name                                        ID   Mem VCPUs      State 
>> Time(s)
>> Domain-0                                     0   256     1     r----- 
>> 37627.4
>> dktestvmxen                                  1   256     1     
>> ---s--    4.8
>>
>> Here's my domU config file:
>>
>> kernel='/boot/vmlinuz-2.6.18.8-xen'
>> ramdisk='/boot/initrd-2.6.18.8-xen.img'
>> disk = [ 'file:/dktestvmxen.img,hda1,w' ]
>> memory = 256
>> maxmem = 512
>> builder = 'linux'
>> name = 'dktestvmxen'
>> vif = [ 'mac=00:16:3e:13:71:7b,bridge=eth1' ]
>> localtime = 0
>> on_poweroff = 'destroy'
>> on_reboot = 'restart'
>> on_crash = 'restart'
>> root = '/dev/hda1'
>> extra='TERM=xterm xencons=tty console=tty1'
>>
>> This also happens if I shutdown the domain with "shutdown -hP now" or 
>> "xm shutdown $domid" from dom0.
>>
>> Any help would be much appreciated.
>>
>> Regards
>> Dominik
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 

Re: Domain status after shutdown command: ---s--

[Keir Fraser]

What's in the tail of /var/log/xen/xend.log after the domain shuts down?

 -- Keir

On 9/4/08 15:25, "Dominik Klein" <dk@in-telegence.net> wrote:

> So I'm not alone with that problem.
> 
> I just tested with 3.2.1rc3 and the problem persists.
> 
> Regards
> Dominik
> 
> Marc Patino Gómez wrote:
>> Hi all,
>> 
>> I have the same problem, I'm using also Debian Etch on AMD64 and Xen
>> 3.2.0 builded from sources. At the moment, I am trying to find a
>> solution for this issue.
>> 
>> Regards,
>> 
>> Marc
>> 
>> Dominik Klein wrote:
>>> Hi
>>> 
>>> this was already on xen-users, but noone could help.
>>> 
>>> I use Xen 3.2 on debian etch, build from source. domU is also debian
>>> etch.
>>> 
>>> I can create the domain just fine, but when I shut it down, it stays
>>> in status "---s--" forever until I use "xm destroy".
>>> 
>>> At first, I put domU on a DRBD disk with the block-drbd script, but I
>>> also tried with a file-backed domU, which results in the same problem.
>>> 
>>> The logs do not show any errors. Or at least I cannot see anything
>>> that looks like an error.
>>> 
>>> Here's what I see if I shutdown the domain from a console:
>>> 
>>> debian dktestvmxen:~# halt
>>> Broadcast message from root@dktestvmxen (tty1) (Mon Feb 11 08:32:34
>>> 2008):
>>> The system is going down for system halt NOW!
>>> INIT: Switching to runlevel: 0
>>> INIT: Sending processes the TERM signal
>>> Stopping periodic command scheduler: crond.
>>> Stopping internet superserver: inetd.
>>> Stopping OpenBSD Secure Shell server: sshd.
>>> Stopping kernel log daemon: klogd.
>>> Stopping system log daemon: syslogd.
>>> Asking all remaining processes to terminate...done.
>>> Killing all remaining processes...done.
>>> Deconfiguring network interfaces...done.
>>> Cleaning up ifupdown....
>>> Deactivating swap...done.
>>> Will now halt.
>>> md: stopping all md devices.
>>> xenbus_dev_shutdown: device/console/0: Initialising != Connected,
>>> skipping
>>> System halted.
>>> 
>>> At this point, the console is locked. If I quit the console with
>>> CTRL+5 and use "xm list", I see
>>> 
>>> # xm list
>>> Name                                        ID   Mem VCPUs      State
>>> Time(s)
>>> Domain-0                                     0   256     1     r-----
>>> 37627.4
>>> dktestvmxen                                  1   256     1
>>> ---s--    4.8
>>> 
>>> Here's my domU config file:
>>> 
>>> kernel='/boot/vmlinuz-2.6.18.8-xen'
>>> ramdisk='/boot/initrd-2.6.18.8-xen.img'
>>> disk = [ 'file:/dktestvmxen.img,hda1,w' ]
>>> memory = 256
>>> maxmem = 512
>>> builder = 'linux'
>>> name = 'dktestvmxen'
>>> vif = [ 'mac=00:16:3e:13:71:7b,bridge=eth1' ]
>>> localtime = 0
>>> on_poweroff = 'destroy'
>>> on_reboot = 'restart'
>>> on_crash = 'restart'
>>> root = '/dev/hda1'
>>> extra='TERM=xterm xencons=tty console=tty1'
>>> 
>>> This also happens if I shutdown the domain with "shutdown -hP now" or
>>> "xm shutdown $domid" from dom0.
>>> 
>>> Any help would be much appreciated.
>>> 
>>> Regards
>>> Dominik
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>> 
>> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Domain status after shutdown command: ---s--

[Dominik Klein]

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.

Regards
Dominik

Re: Domain status after shutdown command: ---s--

[Dominik Klein]

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

Regards
Dominik

Re: Domain status after shutdown command: ---s--

[Keir Fraser]

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

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

[Dominik Klein]

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