From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicholas Lee Subject: Stopping xend while a domU is running Date: Sun, 6 Mar 2005 17:32:24 +1300 Message-ID: <20050306043224.GC27446@stateless> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org As a little expt I stopped xend (/etc/init.d/xend stop) while running a single domU. The guest seemed to still be pingable. However I couldn't access it. Obviously console wasn't avaliable. I then tried to restart xend. xfrd/SrvDaemon started. However it was not accessible. ie. [2005-03-06 16:26:57 xend] INFO (SrvDaemon:607) Xend Daemon started [2005-03-06 16:31:53 xend] INFO (SrvDaemon:607) Xend Daemon started [2005-03-06 16:31:53 xend] INFO (XendRoot:91) EVENT> xend.start 0 Note the lack of "EVENT> xend.start". I was forced to reboot domO in order to get access to xen back. Upgrading the xend tools, and trying a restart seems to have the same affect. Is this a known issue? Being forced to shutdown all domUs to upgrades xend might be annoying in some situations. Nicholas ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click