2013/12/14 Markiyan Kushnir <markiyan.kushnir_at_gmail.com>: > 2013/12/14 Markiyan Kushnir <markiyan.kushnir_at_gmail.com>: >> 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. >> > > 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. Ok, I was able to hit a similarly looking panic exactly when trying to run "bhyvectl --vm=altroot-bhyve --get-all" while the VM was busy with its own "pkg delete -af". When the VM is mostly idle, bhyvectl --get-all goes smoothly. Now I'm thinking I might inadvertently run bhyvectl over my heavily running VM once when I was not at the desktop and wanted to see how things were going remotely from my office... Here are core.txt of the two panics in a row: https://drive.google.com/file/d/0B9Q-zpUXxqCnMUxVdGwxSEs1dE0/edit?usp=sharing https://drive.google.com/file/d/0B9Q-zpUXxqCnREtuTXpabnQ5QXM/edit?usp=sharing -- Markiyan. > >> -- >> 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"Received on Sat Dec 14 2013 - 13:00:34 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:45 UTC