Hi Andriy,
On Tue, Jul 14, 2015 at 1:36 AM, Andriy Gapon wrote:
>
> I couldn't find any information in bhyve(8) on how bhyve responds to various
> signals. It seems that at least SIGTERM is intercepted and translated to an
> ACPI power event. How about other signals? What's the best signal to
Hi Andriy,
In the grub-bhyve menu of boot entries I can press 'e' and enter a screen where
I can modify boot commands for that entry.
The screen has the following help information at the bootom:
Minimum Emacs-like screen editing is supported.
TAB lists completions.
Press
On 23/06/2015 11:05, Andriy Gapon wrote:
> On 23/06/2015 10:26, Neel Natu wrote:
[snip]
>> Does this ever happen with a single vcpu guest?
>
> Never seen the problem with a single CPU so far.
> Also, never had that problem with FreeBSD guests.
>
>> The other mystery is the NMIs the host is receiv
In the grub-bhyve menu of boot entries I can press 'e' and enter a screen where
I can modify boot commands for that entry.
The screen has the following help information at the bootom:
Minimum Emacs-like screen editing is supported.
TAB lists completions.
Press Ctrl-x or F10
I couldn't find any information in bhyve(8) on how bhyve responds to various
signals. It seems that at least SIGTERM is intercepted and translated to an
ACPI power event. How about other signals? What's the best signal to use to
kill a hung VM that can not be stopped gracefully?
--
Andriy Gap
Not sure if there is anything that bhyve can do about the following, but maybe
it can. It seems that that after a host is suspended for several hours and
resumed while a bhyve VM is running, then time counting becomes rather broken in
the VM.
With Linux VMs I observe that date(1) keeps reporting
