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

Re: [Xen-devel] changeset:6989 vm sticking around in shutdown state

To: xen-devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] changeset:6989 vm sticking around in shutdown state
From: Dan Smith <danms@xxxxxxxxxx>
Date: Thu, 22 Sep 2005 06:57:29 -0700
Delivery-date: Thu, 22 Sep 2005 13:55:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1127394791.23958.283.camel@xxxxxxxxxxxxxxxxxxxxxx> (Ted Kaczmarek's message of "Thu, 22 Sep 2005 09:13:11 -0400")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1127394791.23958.283.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)
TK> I cloned the config with a new name and the domU was recreated.

This brings me back to the topic of renaming stuck domains.  It seems
to me that having the tools prevent you from re-creating a domain just
because a shell of the domain is stuck will get annoying.  Admins may
end up cloning a config file and tweaking the name several times to
get the tools to allow recreation of one of their domUs without having
to reboot the host.

I know that the domains *shouldn't* get stuck once everything firms
up, but can't we have the tools be more user-friendly if the problem
does arise in a production environment?

How about adding a "force" flag to "xm create" that would rename any
stuck domains so that the creation can proceed?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx


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