From owner-freebsd-xen@FreeBSD.ORG  Mon Oct 21 13:30:01 2013
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id CF5AA415
 for <freebsd-xen@smarthost.ysv.freebsd.org>;
 Mon, 21 Oct 2013 13:30:01 +0000 (UTC)
 (envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id BDB232821
 for <freebsd-xen@smarthost.ysv.freebsd.org>;
 Mon, 21 Oct 2013 13:30:01 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9LDU1Ow054091
 for <freebsd-xen@freefall.freebsd.org>; Mon, 21 Oct 2013 13:30:01 GMT
 (envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
 by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9LDU1Wf054090;
 Mon, 21 Oct 2013 13:30:01 GMT (envelope-from gnats)
Date: Mon, 21 Oct 2013 13:30:01 GMT
Message-Id: <201310211330.r9LDU1Wf054090@freefall.freebsd.org>
To: freebsd-xen@FreeBSD.org
Cc: 
From: Mark Felder <feld@feld.me>
Subject: Re: kern/171118: [xen] FreeBSD XENHVM guest doesn
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Mark Felder <feld@feld.me>
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Oct 2013 13:30:01 -0000

The following reply was made to PR kern/171118; it has been noted by GNATS.

From: Mark Felder <feld@feld.me>
To: "bug-followup" <bug-followup@FreeBSD.org>
Cc:  
Subject: Re: kern/171118: [xen] FreeBSD XENHVM guest doesn
Date: Mon, 21 Oct 2013 08:25:47 -0500

 Quoting this in a reply to the PR -- it seems Jason's message was
 rejected by spam perhaps and didn't make it into GNATS?
 
 On Tue, Aug 13, 2013, at 21:01, Jason Shi wrote:
 > After we lanuch a "shutdown" operation in Xen Center, Xen Server issues a
 > clean_shutdown operation. 
 > And actually the signal sended to VM is "halt". We can see that from the
 > xen source log on dom0. e.g.:
 > Aug 13 15:03:48 xenserver-lxpwbbml xenopsd:
 > [debug|xenserver-lxpwbbml|7|Async.VM.clean_shutdown
 > R:832f756cad74|xenops] VM =
 > dc401e38-9        7af-5972-7150-d067d701fa88; domid = 115; Requesting
 > domain
 > halt
 > 
 > FreeBSD VM receives the signal and do shutdown_nice(RB_HALT). This is a
 > halt action which will not lead to
 >  a poweroff ending. So the VM domain will not be destroyed.
 > Xen Server expected the target domain to be destroyed until it times out.
 > Then Xen Center gets a timeout and 
 > it logs "shutdown failed" then.
 > 
 > I think this a xen bug. 
 > But as a workaround, you can modify the xctrl_halt function from:
 > shutdown_nice(RB_HALT); 
 > to
 > shutdown_nice(RB_POWEROFF|RB_HALT);
 > 
 > Though you may not get exactly what you expect when you really want your
 > VMs to "halt".
 > 
 > 
 > 
 > 
 > Jason Shi