[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Shutdown of dom0 with running DomUs cannot deactivate volume group


  • To: mlg-hessigheim@xxxxxx
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Fri, 24 Oct 2008 15:35:02 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 24 Oct 2008 12:35:45 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=DaBCGyRUTqXHQtlE6zw8J/3NTDcSljvKxWHhkP5ZXMQCBZiIerOxSttUj4q6/rWkvR iucgbrHP0NGbvvigEutuyUkBZirY3D9OhqxS2yjzWGkGvaqGxzPjgeQNoyaB9jgLpJYa veDlKdX6tedSbqqaxQG8oNJJDwRhu5E2EZjOk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Fri, Oct 24, 2008 at 2:58 PM, Dustin Henning
<Dustin.Henning@xxxxxxxxxxx> wrote:
>        Doesn't xenddomains do this during shutdown?  I mean, it should wait
> so long and then forcefully terminate the domain if it won't shut down.  The
> time to wait prior to kill can be configured, but the forceful termination
> as part of the xenddomains shutdown, or is xenddomains part of Fedora and
> not native to xend?

The xendomains script is actually a good idea here and it comes standard
 with Xen.

The same basic idea should apply, but not tying the guest to xend has a lot
of advantages actually. For example when you just want to make a small
change and not bring all the guests down. Using the xendomains script
should be a better approach.

Cheers,
Todd

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.