On Mon, Jun 24, 2013 at 3:54 PM, Aryeh Friedman <aryeh.fried...@gmail.com>wrote:
> How do I make it so I do not need to allocate a xterm to being the
> console for a bhyve guest? (so far I have not been able to make it so
> I can break the connection to the console and the guest doesn't crash)
Yeah, this is because bhyve is exiting when it gets a SIGHUP.
Here is a patch that may help you sidestep this problem for now:
--- bhyverun.c (revision 252047)
+++ bhyverun.c (working copy)
@@ -679,6 +679,17 @@
vmname = argv;
+ struct sigaction sa;
+ sa.sa_flags = 0;
+ sa.sa_handler = SIG_IGN;
+ err = sigaction(SIGHUP, &sa, NULL);
+ assert(err == 0);
The right way to fix this is to have a configurable backend (terminal,
network port, pipe) for the virtual serial port.
> Related question when using vmrun.sh it seems like the vtnet on the
> guest becomes unusable after reboot of the guest (rebooting the host
> is the only solution I can find) is there a work around for this? (I
> tried toggling the state of if_tap and if_bridge)
If you could provide some more details I will try to reproduce it. For e.g.
IP address assigned to the guest, host networking setup etc.
> email@example.com mailing list
> To unsubscribe, send any mail to "
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to