From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Smith Subject: Re: changeset:6989 vm sticking around in shutdown state Date: Thu, 22 Sep 2005 06:57:29 -0700 Message-ID: <87oe6lb3xy.fsf@us.ibm.com> References: <1127394791.23958.283.camel@pluto.linsolutions.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <1127394791.23958.283.camel@pluto.linsolutions.com> (Ted Kaczmarek's message of "Thu, 22 Sep 2005 09:13:11 -0400") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List List-Id: xen-devel@lists.xenproject.org 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@us.ibm.com