From owner-freebsd-virtualization@FreeBSD.ORG Sat Dec 14 14:00:34 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5085ED0; Sat, 14 Dec 2013 14:00:34 +0000 (UTC) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 03A3D14AE; Sat, 14 Dec 2013 14:00:33 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id a1so2982080wgh.29 for ; Sat, 14 Dec 2013 06:00:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ytxNJAI5K2cbVTRrfDhYkTs5sBLR9RXv2p9Fr/5r3WY=; b=Gt9yV6uQYs6z/vsC6nU+NC6PDJ4Pbb1f4FBTDtiYmT7sMkqTb+F9cs06Uml9KvwkU3 GRx55yUddYSan56H2RXKpBe+Sz1GDsaU62lBa6L8oXG5oE17eVxlCNz2+43q+R3bRTZe 0jNp1JxVqsCp88azeHjW5ntg/6jWf/3mxtfTxKtio6k+wNss5oTJY0XpuW8YchWbfO8D QFAuk4OD8lr0qbJsPsA6dWQf7va3Tcm9TSE1xYVhviUkls2lP8IuljMY34DMoBtJgXPO VxF270lnETz+Kfnz1UaOdjP4zuuQxELIxWXtaPwE9pit/Qmx0WoF8nNp+aLQEmOcY68D vgKA== MIME-Version: 1.0 X-Received: by 10.180.108.97 with SMTP id hj1mr6688364wib.59.1387029631779; Sat, 14 Dec 2013 06:00:31 -0800 (PST) Received: by 10.227.226.12 with HTTP; Sat, 14 Dec 2013 06:00:31 -0800 (PST) In-Reply-To: References: <201312131304.57455.jhb@freebsd.org> Date: Sat, 14 Dec 2013 16:00:31 +0200 Message-ID: Subject: Re: 11.0-CURRENT panic while running a bhyve instance From: Markiyan Kushnir To: Neel Natu Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD current , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 14:00:34 -0000 2013/12/14 Markiyan Kushnir : > 2013/12/14 Markiyan Kushnir : >> 2013/12/14 Neel Natu : >>> Hi Markiyan, >>> >>> On Fri, Dec 13, 2013 at 2:35 PM, Markiyan Kushnir >>> wrote: >>>> 2013/12/13 John Baldwin : >>>>> 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 >>>>>> 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"