From owner-freebsd-xen@FreeBSD.ORG Mon Oct 21 11:06:59 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 32CCFA8B for ; Mon, 21 Oct 2013 11:06:59 +0000 (UTC) (envelope-from owner-bugmaster@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 1F4B52E3A for ; Mon, 21 Oct 2013 11:06:59 +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 r9LB6wr2018861 for ; Mon, 21 Oct 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9LB6w7s018859 for freebsd-xen@FreeBSD.org; Mon, 21 Oct 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Oct 2013 11:06:58 GMT Message-Id: <201310211106.r9LB6w7s018859@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2013 11:06:59 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/180788 xen [xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot o kern/180403 xen [xen] Problems with GENERIC and XENHVM kernels with Xe o kern/180402 xen [xen] XEN kernel does not load in XenClient 4.5.5 o kern/179814 xen [xen] mountroot fails with error=19 under Xen on 9-STA o kern/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 39 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Oct 21 13:10:11 2013 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C50FEF80 for ; Mon, 21 Oct 2013 13:10:11 +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 9875626F9 for ; Mon, 21 Oct 2013 13:10:06 +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 r9LDA1qq049512 for ; Mon, 21 Oct 2013 13:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9LDA1wA049511; Mon, 21 Oct 2013 13:10:01 GMT (envelope-from gnats) Date: Mon, 21 Oct 2013 13:10:01 GMT Message-Id: <201310211310.r9LDA1wA049511@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: Mark Felder 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 List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2013 13:10:11 -0000 The following reply was made to PR kern/171118; it has been noted by GNATS. From: Mark Felder To: shidj , "bug-followup" Cc: Subject: Re: kern/171118: [xen] FreeBSD XENHVM guest doesn Date: Mon, 21 Oct 2013 08:00:43 -0500 On Tue, Aug 13, 2013, at 21:01, Jason Shi wrote: > > Though you may not get exactly what you expect when you really want your > VMs to "halt". > I'm struggling to think of a scenario where I want a VM to halt and not shutdown. From owner-freebsd-xen@FreeBSD.ORG Mon Oct 21 13:30:01 2013 Return-Path: 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 ; 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 ; 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 ; 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 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 List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 To: "bug-followup" 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 From owner-freebsd-xen@FreeBSD.ORG Mon Oct 21 15:20:02 2013 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 06E575F8 for ; Mon, 21 Oct 2013 15:20:02 +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 E5EF32EB7 for ; Mon, 21 Oct 2013 15:20: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 r9LFK135076845 for ; Mon, 21 Oct 2013 15:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9LFK12g076844; Mon, 21 Oct 2013 15:20:01 GMT (envelope-from gnats) Date: Mon, 21 Oct 2013 15:20:01 GMT Message-Id: <201310211520.r9LFK12g076844@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: kern/171118: [xen] FreeBSD XENHVM guest doesn't shutdown cleanly X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2013 15:20:02 -0000 The following reply was made to PR kern/171118; it has been noted by GNATS. From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= To: , Cc: Subject: Re: kern/171118: [xen] FreeBSD XENHVM guest doesn't shutdown cleanly Date: Mon, 21 Oct 2013 16:18:34 +0100 When using libxl the event sent is a "poweroff", but I guess XenServer toolstack is sending a "halt" event instead (which libxl doesn't use for anything). The following patch wires the "halt" event handler to the "poweroff" handler and removes the now unused "halt" handler. I'm currently on a trip, so I haven't been able to test the patch (not even compile tested). --- diff --git a/sys/dev/xen/control/control.c b/sys/dev/xen/control/control.c index 35c923d..78894ba 100644 --- a/sys/dev/xen/control/control.c +++ b/sys/dev/xen/control/control.c @@ -158,7 +158,6 @@ static xctrl_shutdown_handler_t xctrl_poweroff; static xctrl_shutdown_handler_t xctrl_reboot; static xctrl_shutdown_handler_t xctrl_suspend; static xctrl_shutdown_handler_t xctrl_crash; -static xctrl_shutdown_handler_t xctrl_halt; /*-------------------------- Private Data Structures -------------------------*/ /** Element type for lookup table of event name to handler. */ @@ -173,7 +172,7 @@ static const struct xctrl_shutdown_reason xctrl_shutdown_reasons[] = { { "reboot", xctrl_reboot }, { "suspend", xctrl_suspend }, { "crash", xctrl_crash }, - { "halt", xctrl_halt }, + { "halt", xctrl_poweroff }, }; struct xctrl_softc { @@ -427,12 +426,6 @@ xctrl_crash() } static void -xctrl_halt() -{ - shutdown_nice(RB_HALT); -} - -static void xen_pv_shutdown_final(void *arg, int howto) { /*