11.0-CURRENT panic while running a bhyve instance

Markiyan Kushnir markiyan.kushnir at gmail.com
Sat Dec 14 07:57:43 UTC 2013


2013/12/14 Neel Natu <neelnatu at gmail.com>:
> 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?
>

Well, I don't know if there was. I would set up the same scenario
again + a script running on the host querying bhyvectl. May be I would
catch it again. Please let me know if all it makes sense, and if so,
how it can be made better.

--
Markiyan.

> 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"


More information about the freebsd-virtualization mailing list