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-users

[Xen-users] Unable to shutdown a VM

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Unable to shutdown a VM
From: Thomas <iamkenzo@xxxxxxxxx>
Date: Sat, 7 Jun 2008 19:21:13 +0200
Delivery-date: Sat, 07 Jun 2008 10:21:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=m3rDzGyTVzT1OrAIb0+Wrj85WYbMnUoC3HgdIpakOz0=; b=mevL169L7DowqM0RLWRCCwMZQSg+ADJaiSD93yPzNlIXKytQj88G1Mf3Ut3solgtUc AD30IW2rrAbJClMTgFXGZfk4OBnUL0bTxK5scAmAoi0Ap4Df17/3qWJ/j0Q9xXbTkdTG LFyzJH52oiMsipMe+e8+wbs3Zv3lbZKm112Pw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=TqtLGdw14wOef6iPab9voj+g8RVzaMU7cEqSxJ7myrr5vIGX8xMycoFqTbiOcDh0B+ 2/CCM7xDFJ7a8crJTxX3PLomDIQU9dq68//EYnKSdZpKHSYp0rkgHr8lCS7HfY0Em8QS vqtDtznYlvyd2u/Eep+5ZvOAa/YnfWXGDoIlI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi list,

I already had a VM working smoothly, then I decided to create a new
one. I made an error when copying the config file, I used the same
name for both VMs. When I saw my error, I edited the config file of
the second VM, but now I am unable to shut it down or reboot it. I
can't enter the VM either as it is not running, but "xm list" still
displays it. How can I turn it off or force it to reload its
configuration file?

Best regards,

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

<Prev in Thread] Current Thread [Next in Thread>