Date: Wed, 9 Apr 2014 04:54:36 +0900 From: Takuya ASADA <syuu@dokukino.com> To: Steve Wills <swills@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: bhyve VM crashed Message-ID: <CALG4x-VCZWzHndbuW=TjAFusMM=-1fUXMrTUCLtOhGhJ=TyA6g@mail.gmail.com> In-Reply-To: <20140408192635.GB89356@mouf.net> References: <20140408182844.GC84921@mouf.net> <5344434F.6000004@freebsd.org> <20140408192635.GB89356@mouf.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Did you execute bhyveload before bhyve? 2014-04-09 4:26 GMT+09:00 Steve Wills <swills@freebsd.org>: > On Tue, Apr 08, 2014 at 11:43:27AM -0700, Peter Grehan wrote: > > Hi Steve, > > > > > I experienced a bhyve VM crash with this message: > > > > > > vm exit[1] > > > reason VMX > > > rip 0xffffffff80c7490b > > > inst_length 3 > > > status 0 > > > exit_reason 2 > > > > That's a triple-fault :( > > > > (the exit reasons are the VMX ones in Appendix C, Vol 3 of the Intel > SDM). > > > > Any idea what was happening at the time ? > > The VM was building ports. I could try to deduce which ports, but I > wouldn't be > 100% sure. > > > 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, > Steve > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALG4x-VCZWzHndbuW=TjAFusMM=-1fUXMrTUCLtOhGhJ=TyA6g>