David Ballester Montolio
2006-Jul-10 14:44 UTC
[Xen-users] reboot, destroy, shutdown... always get zombie domains
Hi to all: I''ve a machine under Centos 4.3 running xen 3 and in general, runs very well, the problem comes when i try to shutdown/reboot a domain. Even if I run a shutdown or reboot command inside guest domain or make a destroy/shutdown/save fom xm, the xen guest domain gets zombie state. By now my only way to have only the Dom0 running is ... reboot the whole machine. The guests domains are a copy of dom0 filesystems, with necesary changes ( network, services to start/stop, hostname... ) and are used to test oracle monoinstances. As I said, runs very well until i need to shutdown or reboot the domains. I installed xen dom0 and guests using karanbir singh notes Here comes relevant info about my domain0 : rpm -qa | grep xen "[root@xen xen-store]# rpm -qa | grep -i xen nptl-devel-2.3.4-2.13.xen.0.c4 glibc-devel-2.3.4-2.13.xen.0.c4 xen-3.0.0-2.1_rhel4.1 glibc-common-2.3.4-2.13.xen.0.c4 glibc-profile-2.3.4-2.13.xen.0.c4 xen-kernel-2.6.12-xen3_2.1_rhel4.1 glibc-2.3.4-2.13.xen.0.c4 glibc-utils-2.3.4-2.13.xen.0.c4 glibc-headers-2.3.4-2.13.xen.0.c4 nscd-2.3.4-2.13.xen.0.c4 [root@xen xen-store]# " tail -n50 /var/log/xend.log " [2006-07-10 16:06:05 xend] DEBUG (DevController:133) Waiting for devices vif. [2006-07-10 16:06:05 xend] DEBUG (DevController:139) Waiting for 0. [2006-07-10 16:06:05 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-07-10 16:06:05 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-07-10 16:06:06 xend] DEBUG (DevController:426) hotplugStatusCallback 1. [2006-07-10 16:06:06 xend] DEBUG (DevController:133) Waiting for devices usb. [2006-07-10 16:06:06 xend] DEBUG (DevController:133) Waiting for devices vbd. [2006-07-10 16:06:06 xend] DEBUG (DevController:139) Waiting for 2049. [2006-07-10 16:06:06 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status. [2006-07-10 16:06:06 xend] DEBUG (DevController:426) hotplugStatusCallback 1. [2006-07-10 16:06:06 xend] DEBUG (DevController:139) Waiting for 2050. [2006-07-10 16:06:06 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2050/hotplug-status. [2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2050/hotplug-status. [2006-07-10 16:06:07 xend] DEBUG (DevController:426) hotplugStatusCallback 1. [2006-07-10 16:06:07 xend] DEBUG (DevController:139) Waiting for 5632. [2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status. [2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status. [2006-07-10 16:06:07 xend] DEBUG (DevController:426) hotplugStatusCallback 1. [2006-07-10 16:06:07 xend] DEBUG (DevController:139) Waiting for 2065. [2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2065/hotplug-status. [2006-07-10 16:06:07 xend] DEBUG (DevController:426) hotplugStatusCallback 1. [2006-07-10 16:06:07 xend] DEBUG (DevController:133) Waiting for devices pci. [2006-07-10 16:06:07 xend] DEBUG (DevController:133) Waiting for devices ioports. [2006-07-10 16:06:07 xend] DEBUG (DevController:133) Waiting for devices vtpm. [2006-07-10 16:06:07 xend] INFO (XendDomain:360) Domain nodusa (1) unpaused. [2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:80) [xc_save]: /usr/lib/xen/bin/xc_save 10 19 1 0 0 0 [2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:200) suspend [2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:83) In saveInputHandler suspend [2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:85) Suspending 1 ... [2006-07-10 16:07:47 xend.XendDomainInfo] INFO (XendDomainInfo:810) Domain has shutdown: name=migrating-nodusa id=1 reason=suspend. [2006-07-10 16:07:47 xend] INFO (XendCheckpoint:88) Domain 1 suspended. [2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:91) Written done [2006-07-10 16:07:47 xend] ERROR (XendCheckpoint:227) Had 0 unexplained entries in p2m table 1: sent 166395, skipped 0, delta 19895ms, dom0 3%, target 0%, sent 274Mb/s, dirtied 0Mb/s 0 pages [2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) Total pages sent= 166395 (0.99x) [2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) (of which 0 were fixups) [2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) All memory is saved [2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) Save exit rc=0 [2006-07-10 16:08:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1273) XendDomainInfo.destroyDomain(1) [root@xen log]# " This was while doing a save command from xm Any tip? Best regards D. --------------------------------- LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com --0-99927223-1152542683=:82606 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi to all:<br><br>I''ve a machine under Centos 4.3 running xen 3 and in general, runs very well, the problem comes when i try to shutdown/reboot a domain. Even if I run a shutdown or reboot command inside guest domain or make a destroy/shutdown/save fom xm, the xen guest domain gets zombie state. By now my only way to have only the Dom0 running is ... reboot the whole machine.<br><br>The guests domains are a copy of dom0 filesystems, with necesary changes ( network, services to start/stop, hostname... ) and are used to test oracle monoinstances. As I said, runs very well until i need to shutdown or reboot the domains.<br><br>I installed xen dom0 and guests using <a href="http://www.karan.org/blog/index.php/2005/12/06/xen3_on_centos4">karanbir singh notes</a><br><br>Here comes relevant info about my domain0 :<br><br>rpm -qa | grep xen<br>"[root@xen xen-store]# rpm -qa | grep -i xen<br>nptl-devel-2.3.4-2.13.xen.0.c4<br>glibc-devel-2.3.4-2.13.xen.0.c4<br>xen-3.0.0-2.1_rhel4.1<br>glibc-common-2.3.4-2.13.xen.0.c4<br>glibc-profile-2.3.4-2.13.xen.0.c4<br>xen-kernel-2.6.12-xen3_2.1_rhel4.1<br>glibc-2.3.4-2.13.xen.0.c4<br>glibc-utils-2.3.4-2.13.xen.0.c4<br>glibc-headers-2.3.4-2.13.xen.0.c4<br>nscd-2.3.4-2.13.xen.0.c4<br>[root@xen xen-store]#<br>"<br><br>tail -n50 /var/log/xend.log<br>"<br>[2006-07-10 16:06:05 xend] DEBUG (DevController:133) Waiting for devices vif.<br>[2006-07-10 16:06:05 xend] DEBUG (DevController:139) Waiting for 0.<br>[2006-07-10 16:06:05 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.<br>[2006-07-10 16:06:05 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:426) hotplugStatusCallback 1.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:133) Waiting for devices usb.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:133) Waiting for devices vbd.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:139) Waiting for 2049.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:426) hotplugStatusCallback 1.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:139) Waiting for 2050.<br>[2006-07-10 16:06:06 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2050/hotplug-status.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2050/hotplug-status.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:426) hotplugStatusCallback 1.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:139) Waiting for 5632.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:426) hotplugStatusCallback 1.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:139) Waiting for 2065.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:409) hotplugStatusCallback /local/domain/0/backend/vbd/1/2065/hotplug-status.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:426) hotplugStatusCallback 1.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:133) Waiting for devices pci.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:133) Waiting for devices ioports.<br>[2006-07-10 16:06:07 xend] DEBUG (DevController:133) Waiting for devices vtpm.<br>[2006-07-10 16:06:07 xend] INFO (XendDomain:360) Domain nodusa (1) unpaused.<br>[2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:80) [xc_save]: /usr/lib/xen/bin/xc_save 10 19 1 0 0 0<br>[2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:200) suspend<br>[2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:83) In saveInputHandler suspend<br>[2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:85) Suspending 1 ...<br>[2006-07-10 16:07:47 xend.XendDomainInfo] INFO (XendDomainInfo:810) Domain has shutdown: name=migrating-nodusa id=1 reason=suspend.<br>[2006-07-10 16:07:47 xend] INFO (XendCheckpoint:88) Domain 1 suspended.<br>[2006-07-10 16:07:47 xend] DEBUG (XendCheckpoint:91) Written done<br>[2006-07-10 16:07:47 xend] ERROR (XendCheckpoint:227) Had 0 unexplained entries in p2m table<br> 1: sent 166395, skipped 0, delta 19895ms, dom0 3%, target 0%, sent 274Mb/s, dirtied 0Mb/s 0 pages<br>[2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) Total pages sent= 166395 (0.99x)<br>[2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) (of which 0 were fixups)<br>[2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) All memory is saved<br>[2006-07-10 16:08:08 xend] ERROR (XendCheckpoint:227) Save exit rc=0<br>[2006-07-10 16:08:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1273) XendDomainInfo.destroyDomain(1)<br>[root@xen log]#<br>"<br>This was while doing a save command from xm<br><br>Any tip?<br><br>Best regards<br><br>D.<br><br><br><br><p>  <hr size=1><br><font face="Verdana" size="-2">LLama Gratis a cualquier PC del Mundo.<br>Llamadas a fijos y móviles desde 1 céntimo por minuto.<br><a href="http://us.rd.yahoo.com/mail/es/tagline/messenger/*http://es.voice.yahoo.com/">http://es.voice.yahoo.com</a></font> --0-99927223-1152542683=:82606-- --===============1671100380=Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============1671100380==--
David Ballester Montolio
2006-Jul-13 15:29 UTC
RE: [Xen-users] reboot, destroy, shutdown... always get zombie domains (II)
David Ballester Montolio <dbm0572@yahoo.es> escribió: Hi to all: I''ve a machine under Centos 4.3 running xen 3 and in general, runs very well, the problem comes when i try to shutdown/reboot a domain. Even if I run a shutdown or reboot command inside guest domain or make a destroy/shutdown/save fom xm, the xen guest domain gets zombie state. By now my only way to have only the Dom0 running is ... reboot the whole machine. By now seems that both domains ( dom0 and guests ) shuts down well but finishes with ''Power down'' message and something prevents xen to finally release the info about the closed domain. I will play with acpi, apm and shuch type of things. ¿Any advice? Regards D. --------------------------------- LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com --0-1575628043-1152804599=:7356 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit <br><br><b><i>David Ballester Montolio <dbm0572@yahoo.es></i></b> escribió:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Hi to all:<br><br>I''ve a machine under Centos 4.3 running xen 3 and in general, runs very well, the problem comes when i try to shutdown/reboot a domain. Even if I run a shutdown or reboot command inside guest domain or make a destroy/shutdown/save fom xm, the xen guest domain gets zombie state. By now my only way to have only the Dom0 running is ... reboot the whole machine.<br><br></blockquote><br><br>By now seems that both domains ( dom0 and guests ) shuts down well but finishes with ''Power down'' message and something prevents xen to finally release the info about the closed domain. I will play with acpi, apm and shuch type of things. ¿Any advice?<br><br><br>Regards<br><br>D.<br><p>  <hr size=1><br><font face="Verdana" size="-2">LLama Gratis a cualquier PC del Mundo.<br>Llamadas a fijos y móviles desde 1 céntimo por minuto.<br><a href="http://us.rd.yahoo.com/mail/es/tagline/messenger/*http://es.voice.yahoo.com/">http://es.voice.yahoo.com</a></font> --0-1575628043-1152804599=:7356-- --===============0017596463=Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============0017596463==--