All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Quinton Hoole" <quinton@hoole.biz>
To: xen-devel@lists.sourceforge.net
Subject: Problems shutting down ttylinux VM's
Date: Fri, 4 Feb 2005 12:28:13 +0200	[thread overview]
Message-ID: <00dd01c50aa4$3d59d960$0300a8c0@Quinton> (raw)

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

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
 

[-- Attachment #2: Type: text/html, Size: 7792 bytes --]

                 reply	other threads:[~2005-02-04 10:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00dd01c50aa4$3d59d960$0300a8c0@Quinton' \
    --to=quinton@hoole.biz \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.