On Wed, Feb 12, 2014 at 4:28 AM, Craig Rodrigues <rodr...@freebsd.org>wrote:

> On Tue, Feb 11, 2014 at 3:18 PM, Neel Natu <neeln...@gmail.com> wrote:
> >
> > >
> > >
> > >
> > > One question, if "bhyve" exits, do I have to call bhyveload again
> before
> > > calling bhyve?
> >
> > Yes, that is correct. You will also need to destroy the VM after bhyve
> > exits.
> >
> Why can't bhyve clean up after itself as the bhyve process exits
> and destroy the VM?
> It seems pointless to me for the user to have to explictly
> destroy the VM.  Once the bhyve process exits, I doesn't seem that I can
> use
> the VM again anyways.  To run the VM again, I seem to need to call:
>   -> bhyvectl to destroy the VM
>   -> bhyveload to load
>   -> bhyve to run the VM
> Aryeh has pointed out to me that it is the responsibility of the
> user to explictly destroy and tap and bridge devices used by the
> bhyve process after it exits.  Is this right?
> What if I have a  single bridge0 device, and 10 tap devices,
> one per VM?  If one VM exits and needs to be restarted, do
> I need to tear down all the taps and bridge?

Yes you do.   It gets really harry when you have multple vm's and taps per
instance that need to start and stop at arbitrary times.   We are currently
disccusing this issue on the petitecloud mailing list it might be off topic
here to get into too much detail.

Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to