From owner-freebsd-virtualization@FreeBSD.ORG Wed Apr 9 00:14:14 2014 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 D73EAC41; Wed, 9 Apr 2014 00:14:14 +0000 (UTC) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 79F281B0C; Wed, 9 Apr 2014 00:14:14 +0000 (UTC) Received: from mouf.net (swills@mouf [199.48.129.64]) by mouf.net (8.14.5/8.14.5) with ESMTP id s390DwVC094163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Apr 2014 00:14:03 GMT (envelope-from swills@mouf.net) Received: (from swills@localhost) by mouf.net (8.14.5/8.14.5/Submit) id s390DwJD094162; Wed, 9 Apr 2014 00:13:58 GMT (envelope-from swills) Date: Wed, 9 Apr 2014 00:13:58 +0000 From: Steve Wills To: Peter Grehan Subject: Re: bhyve VM crashed Message-ID: <20140409001355.GE89356@mouf.net> References: <20140408182844.GC84921@mouf.net> <5344434F.6000004@freebsd.org> <20140408192635.GB89356@mouf.net> <534466B8.9060708@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <534466B8.9060708@freebsd.org> User-Agent: Mutt/1.5.22 (2013-10-16) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Wed, 09 Apr 2014 00:14:03 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.98.1 at mouf.net X-Virus-Status: Clean Cc: 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: Wed, 09 Apr 2014 00:14:14 -0000 On Tue, Apr 08, 2014 at 02:14:32PM -0700, Peter Grehan wrote: > Hi Steve, > > > The VM was building ports. I could try to deduce which ports, but I > > wouldn't be 100% sure. > > Probably no need, unless this can be repro'd by building that > particular port. Ok, I'll keep an eye out for that. > Some more questions: Were there other VMs running at the same time ? Yes, there's currently a 9.2 amd64 guest as well, which was also running then and is still running. > What's the type of host CPU/number of CPUs/amount of RAM ? Did the VM hw.model: Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz hw.ncpu: 32 hw.physmem: 68644569088 > have much uptime before the crash ? Have you been able to run similar Was up maybe 4 days, not 100% sure, but I think that's right. > VMs on prior CURRENT releases without this issue (i.e. have we > introduced a regression) ? Don't know, just started doing this. > >> Also, for the guest, do you have the config that was being used > >> (e.g. bhyve command line) ? > > > > /usr/sbin/bhyve -c 4 -m 12G -A -H -P -g 0 -s 0:0,hostbridge -s > > 1:0,lpc -s 2:0,virtio-net,tap1,mac=58:9c:fc:01:01:02 -s > > 3:0,virtio-blk,/vm/100amd64/disk.img -l com1,/dev/nmdm1A 100amd64 > > Thanks for that. > > If you see this again, would you be able to grab VM state for all the > vcpus with > > bhyvectl --get-all --cpu=0 --vm=100amd64 > bhyvectl --get-all --cpu=1 --vm=100amd64 > bhyvectl --get-all --cpu=2 --vm=100amd64 > bhyvectl --get-all --cpu=3 --vm=100amd64 Will do, thanks! Steve