From owner-freebsd-virtualization@FreeBSD.ORG Tue Mar 4 05:42:04 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25905B15 for ; Tue, 4 Mar 2014 05:42:04 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id DC5DA1F5 for ; Tue, 4 Mar 2014 05:42:03 +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 50F6C12189; Tue, 4 Mar 2014 15:42:02 +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 BSG34631 (AUTH peterg@ptree32.com.au); Tue, 4 Mar 2014 15:42:01 +1000 Message-ID: <531567A7.6070000@freebsd.org> Date: Mon, 03 Mar 2014 21:41:59 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Andrea Brancatelli , "freebsd-virtualization@freebsd.org" Subject: Re: bhyvectl References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 04 Mar 2014 05:42:04 -0000 Hi Andrea, > I just throw away at least one hour because I was running bhyvectl destroy > --vm=something instead of bhyvectl --destroy --vm=something. Bhyvectl just > silently ignored the wrong "destroy" instead of "--destroy". > > Maybe it's worth printing out something in such circumstances??? :-) The simple fix, which should show up soon, is to exit in bhyveload if the VM has already been created (i.e. is must be deleted before re-running bhyveload). This will also fix the case of not running the delete. And, bhyvectl should be fixed to flag an error for this case. later, Peter.