From owner-freebsd-virtualization@FreeBSD.ORG  Tue Apr  8 21:14:38 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
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 1F0EAAD8;
 Tue,  8 Apr 2014 21:14:38 +0000 (UTC)
Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12])
 by mx1.freebsd.org (Postfix) with ESMTP id D4B971635;
 Tue,  8 Apr 2014 21:14:37 +0000 (UTC)
Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57])
 by alto.onthenet.com.au (Postfix) with ESMTPS id 260A71234B;
 Wed,  9 Apr 2014 07:14:36 +1000 (EST)
Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210])
 by dommail.onthenet.com.au (MOS 4.2.4-GA)
 with ESMTP id BTF24710 (AUTH peterg@ptree32.com.au);
 Wed, 9 Apr 2014 07:14:35 +1000
Message-ID: <534466B8.9060708@freebsd.org>
Date: Tue, 08 Apr 2014 14:14:32 -0700
From: Peter Grehan <grehan@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Steve Wills <swills@freebsd.org>
Subject: Re: bhyve VM crashed
References: <20140408182844.GC84921@mouf.net> <5344434F.6000004@freebsd.org>
 <20140408192635.GB89356@mouf.net>
In-Reply-To: <20140408192635.GB89356@mouf.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 21:14:38 -0000

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.

  Some more questions: Were there other VMs running at the same time ?
What's the type of host CPU/number of CPUs/amount of RAM ? Did the VM
have much uptime before the crash ? Have you been able to run similar
VMs on prior CURRENT releases without this issue (i.e. have we
introduced a regression) ?

>> 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

later,

Peter.