Date: Mon, 03 Mar 2014 21:41:59 -0800 From: Peter Grehan <grehan@freebsd.org> To: Andrea Brancatelli <abrancatelli@schema31.it>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: bhyvectl Message-ID: <531567A7.6070000@freebsd.org> In-Reply-To: <CADfWLekXKYwfGQQzTCghHKCj9RV5Z44J1%2B2AAXcVSRqh2a3KCQ@mail.gmail.com> References: <CADfWLekXKYwfGQQzTCghHKCj9RV5Z44J1%2B2AAXcVSRqh2a3KCQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?531567A7.6070000>