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.



freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 
  • bhyvectl Andrea Brancatelli
    • Re: bhyvectl Peter Grehan

Reply via email to