From owner-freebsd-virtualization@FreeBSD.ORG Wed Jan 7 17:45:34 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05009893 for ; Wed, 7 Jan 2015 17:45:34 +0000 (UTC) Received: from alto.onthenet.com.au (alto2.onthenet.com.au [203.13.68.14]) by mx1.freebsd.org (Postfix) with ESMTP id BA62D1B16 for ; Wed, 7 Jan 2015 17:45:33 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id 7A338126B7; Thu, 8 Jan 2015 03:45:25 +1000 (EST) Received: from Peters-MacBook-Pro.local (mobile-166-170-037-047.mycingular.net [166.170.37.47] (may be forged)) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id CAT59425 (AUTH peterg@ptree32.com.au); Thu, 8 Jan 2015 03:45:21 +1000 Message-ID: <54AD70AC.7020603@freebsd.org> Date: Wed, 07 Jan 2015 09:45:16 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Andrea Brancatelli Subject: Re: bhyve stuck References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2015 17:45:34 -0000 Hi Andrea, > Assertion failed: (aior != NULL), function ahci_handle_dma, file > /usr/src/usr.sbin/bhyve/pci_ahci.c, line 494. Ok - this should result in the bhyve process exiting. > Now the VM is totally hang. Trying to kill bhyve doesn’t work, not > even kill -9. I tries do to do a bhyvectl —destroy and the VM > disappeared from /dev/vmm but I am strongly uncomfortable with what > to do now. The process is still there. Can I restart the VM? It should be fine to restart after a bhyvectl --destroy > This is the state of the process: ... > 91715 100246 bhyve blk-2:0 7 121 stop getblk This seems to be the culprit. What's the version of FreeBSD running on the host ? tychon@ did quite a bit of work recently on making the block layer more robust in the face of guest controller timeouts. This made it in to CURRENT as of r274330, and was MFCd to 10-STABLE with r276429. That change may help with your issue. later, Peter.