From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 19 22:33:33 2014 Return-Path: Delivered-To: freebsd-virtualization@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 ESMTPS id 44BF1680 for ; Wed, 19 Feb 2014 22:33:33 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 04B081BDA for ; Wed, 19 Feb 2014 22:33:32 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 316E112456; Thu, 20 Feb 2014 08:33:31 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRY24676 (AUTH peterg@ptree32.com.au); Thu, 20 Feb 2014 08:33:30 +1000 Message-ID: <53053138.6020003@freebsd.org> Date: Wed, 19 Feb 2014 14:33:28 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Rudy Subject: Re: bhyve crashes... tip to /dev/nmdm1B References: <5305185A.9060801@monkeybrains.net> In-Reply-To: <5305185A.9060801@monkeybrains.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 19 Feb 2014 22:33:33 -0000 Hi Rudy, > # tip vm1 > Could not open backing file: No such file or directory This is a valid error message from bhyve, and happens when the file attached to a block device can't be opened. > connected > > {...I hit ENTER 5 times here...} This is probably the delay due to core being dumped. > [1] Segmentation fault bhyve -c 2 -m 2048M -H -P -A -s > 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap0 -s 3,ahci-cd,vm1.iso -l > com1,/dev/nmdm1A -s 4,virtio-blk,/dev/zvol/data/vm1 vm1 (core dumped) > > > I relaunched the VM and it works now... Anyone seen issues with nmdm? Try running in the foreground (-l com1,stdio) to see if bhyve can access the iso and zvol OK. (There is a bug here in that bhyve should just exit out if the backing image doesn't exist rather than dumping core.) later, Peter.