From owner-freebsd-current@FreeBSD.ORG Sat Dec 14 23:23:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B985A68; Sat, 14 Dec 2013 23:23:03 +0000 (UTC) Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com [IPv6:2607:f8b0:400d:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D57441661; Sat, 14 Dec 2013 23:23:02 +0000 (UTC) Received: by mail-qe0-f48.google.com with SMTP id gc15so2807555qeb.7 for ; Sat, 14 Dec 2013 15:23:02 -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:content-transfer-encoding; bh=gK1j9JXKanmJxVl8cyJCzEcBEPGZdL9OeWUbEAkjXD8=; b=ZiXFjgxClJFUMM609ZfmdMZ3EehId+EX854PXCPABQQnSsvUGPP1t1/1lEF3kWlz8Z WsbGctto6Aep9n0w8NKgWvy/9W9rxiWeehqNMRyU6fZKTPq4ravytM88XE+C1Nw09orp XoIQb5SnHCwBDz1RSxo/2Dv4Ww7Tz8Q9G+V65Qxwzi1F8u43vhEAm5JdeY2wq1CKArLC H69vFmJQIwE/t5Ua/X0YKCAy+JhXRXvC7YMUXUAu4DBgCspJXRoYQuNrENSjk9UkttTU DygtQGPZ8fCWgWKzerO3O6jQq9T4LXoMZsgNLVMRG+Obi07xYBT9aDlax/pjKiVVmsTp qYnQ== MIME-Version: 1.0 X-Received: by 10.49.27.234 with SMTP id w10mr18939238qeg.22.1387063381926; Sat, 14 Dec 2013 15:23:01 -0800 (PST) Received: by 10.140.34.17 with HTTP; Sat, 14 Dec 2013 15:23:01 -0800 (PST) In-Reply-To: References: <201312131304.57455.jhb@freebsd.org> Date: Sat, 14 Dec 2013 15:23:01 -0800 Message-ID: Subject: Re: 11.0-CURRENT panic while running a bhyve instance From: Neel Natu To: Markiyan Kushnir Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD current , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 23:23:03 -0000 Hi Markiyan, On Sat, Dec 14, 2013 at 6:00 AM, Markiyan Kushnir wrote: > 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-zpUXxqCnem5iYTVqLUxrcWo4cmlhdkM1= c2lJa2dKak5R/edit?usp=3Dsharing >>>>> >>>> >>>> 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=3Daltroot-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=85 > Thanks, that helps a lot because I can see how bhyvectl could perturb the state of the vcpu and eventually lead to a panic. I'll submit a fix for this ASAP. best Neel > Here are core.txt of the two panics in a row: > > https://drive.google.com/file/d/0B9Q-zpUXxqCnMUxVdGwxSEs1dE0/edit?usp=3Ds= haring > > https://drive.google.com/file/d/0B9Q-zpUXxqCnREtuTXpabnQ5QXM/edit?usp=3Ds= haring > > -- > 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 a= ble >>>>>>> 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@freeb= sd.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"