kern/171118: [xen] FreeBSD XENHVM guest doesn

Mark Felder feld at feld.me
Mon Oct 21 13:30:01 UTC 2013


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

From: Mark Felder <feld at feld.me>
To: "bug-followup" <bug-followup at 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


More information about the freebsd-xen mailing list