WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Problems shutting down ttylinux VM's

To: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Problems shutting down ttylinux VM's
From: "Quinton Hoole" <quinton@xxxxxxxxx>
Date: Fri, 4 Feb 2005 12:28:13 +0200
Delivery-date: Fri, 04 Feb 2005 10:29:31 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
Importance: Normal
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx

Hi

 

I’m having various (probably newbie related) problems shutting down ttylinux VM’s.

 

Firstly, using “xm shutdown” causes the VM to report “Ignore spurious shutdown request”, after which it (not unexpectedly) does not shut down. This happens if the VM is at the login prompt.  If I issue an “xm shutdown” after I’ve logged in to the VM, nothing at all happens in the VM (not even the “ignore spurious shutdown request” error message).  In both cases xm does not report any errors.

 

Secondly, shutdown itself does not appear to be in the ttylinux image that I downloaded from the xen site.  What is the preferred method of shutting down a ttylinux VM?

 

Thirdly, in the absence of shutdown, I’ve been using halt in the VM’s.  But this apparently does not do a clean shutdown.  In particular, after I’ve done a halt, it appears that the /etc/dhcpc/dhcpcd-eth0.pid file is not deleted.  This leads to the following error when I boot up the VM again:

 

Starting DHCP for interface eth0: **** dhcpcd: already running

****  dhcpcd: if not then delete /etc/dhcpc/dhcpcd-eth0.pid file

            failed

 

I can delete the file, and get the network working again on the following reboot, but after a halt and reboot, the problem recurs.

 

Any advice?

 

Q


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.4 - Release Date: 2005/02/01

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Problems shutting down ttylinux VM's, Quinton Hoole <=