Date: Sat, 14 Dec 2013 15:30:47 +0200 From: Markiyan Kushnir <markiyan.kushnir@gmail.com> To: Neel Natu <neelnatu@gmail.com> Cc: FreeBSD current <freebsd-current@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: 11.0-CURRENT panic while running a bhyve instance Message-ID: <CACvtUJfXLhZeVS7QFos7JPZLPtNJ4oFHJY0ONXOgsaXifDg=bw@mail.gmail.com> In-Reply-To: <CACvtUJeh67hKE2Cw8c37WsE=PcY03N4ntBDJYmMx8GW7GW7bAg@mail.gmail.com> References: <CACvtUJdtc_aZxmNjz=5UWuBP8DQb%2BGwioTZaPjuqPVsJbRkjcw@mail.gmail.com> <201312131304.57455.jhb@freebsd.org> <CACvtUJcoe=XXC5wJ7QciccuTcguXk6u=f13EHiXDcObhXP7r1A@mail.gmail.com> <CAFgRE9EmZr8f52Mp4tG25zWOOQLitvtFmJOfib55K_qi9e9ztA@mail.gmail.com> <CACvtUJeh67hKE2Cw8c37WsE=PcY03N4ntBDJYmMx8GW7GW7bAg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2013/12/14 Markiyan Kushnir <markiyan.kushnir@gmail.com>: > 2013/12/14 Neel Natu <neelnatu@gmail.com>: >> Hi Markiyan, >> >> On Fri, Dec 13, 2013 at 2:35 PM, Markiyan Kushnir >> <markiyan.kushnir@gmail.com> wrote: >>> 2013/12/13 John Baldwin <jhb@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. > To make it clear -- I didn't run bhyvectl when the VM was running, so I can tell for sure that nobody was trying to interact with the VM during its run. My first thought was that it would make sense to (periodically) query state of the VM using bhyvectl to get info about what was going on when it comes close to the crash... -- Markiyan. > -- > Markiyan. > >> best >> Neel >> >>> -- >>> Markiyan. >>> >>>>> -- >>>>> Markiyan >>>>> >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: Markiyan Kushnir <markiyan.kushnir@gmail.com> >>>>> Date: 2013/12/13 >>>>> Subject: >>>>> To: freebsd-current@freebsd.org, freebsd-virtualization@freebsd.org >>>>> >>>>> >>>>> I started some ports to compile inside a bhyve instance: >>>>> >>>>> root@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@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@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>>>> >>>> >>>> -- >>>> John Baldwin >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACvtUJfXLhZeVS7QFos7JPZLPtNJ4oFHJY0ONXOgsaXifDg=bw>