Re: 11.0-CURRENT panic while running a bhyve instance

Hi Markiyan,

On Fri, Dec 13, 2013 at 2:35 PM, Markiyan Kushnir
<markiyan.kushnir_at_gmail.com> wrote:
> 2013/12/13 John Baldwin <jhb_at_freebsd.org>:
>> On Friday, December 13, 2013 5:46:20 am Markiyan Kushnir wrote:
>>> Forgot to fill the Subject: header, re-posting it fixed.
>>
>> The mailing lists strips attachments, can you post it at a URL?
>>
>
> Shared here:
>
> https://drive.google.com/file/d/0B9Q-zpUXxqCnem5iYTVqLUxrcWo4cmlhdkM1c2lJa2dKak5R/edit?usp=sharing
>

Thanks.

It looks like something funky going on with the vcpu state. Do you
know if there was any access to the VM via 'bhyvectl' close to the
time of the panic?

best
Neel

> --
> Markiyan.
>
>>> --
>>> Markiyan
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Markiyan Kushnir <markiyan.kushnir_at_gmail.com>
>>> Date: 2013/12/13
>>> Subject:
>>> To: freebsd-current_at_freebsd.org, freebsd-virtualization_at_freebsd.org
>>>
>>>
>>> I started some ports to compile inside a bhyve instance:
>>>
>>> root_at_vm:~ # uname -a
>>> FreeBSD vm.mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0
>>> r259250: Thu Dec 12 14:17:32 EET 2013
>>> root_at_vm.mkushnir.zapto.org:/
>>> usr/obj/usr/src.svnup/sys/MAREK  amd64
>>>
>>> and left it running unattended. Approx. 2 hours later the host went to
>>> panic. The bhyve instance survived after the panic and I could be able
>>> to complete my ports compilation.
>>>
>>> core.txt attached (gzipped)
>>> _______________________________________________
>>> freebsd-current_at_freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>>>
>>
>> --
>> John Baldwin
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"