You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no exact number to be named, but for some weird reason after issuing 4-6 reboot commands from within the VM, the vm-supervisor process can't start a new bhyve child.
To resolve this issue I'll need to create a self-destruction mechanism for the parent process for vm-supervisor, whenever it sees that the VM was rebooted. And then simply start a new detached process that will execute hoster vm start vm-name again to start the VM.
The text was updated successfully, but these errors were encountered:
There is no exact number to be named, but for some weird reason after issuing 4-6 reboot commands from within the VM, the
vm-supervisor
process can't start a new bhyve child.To resolve this issue I'll need to create a self-destruction mechanism for the parent process for
vm-supervisor
, whenever it sees that the VM was rebooted. And then simply start a new detached process that will executehoster vm start vm-name
again to start the VM.The text was updated successfully, but these errors were encountered: