Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Dec 2014 14:22:57 -0500
From:      Shawn Webb <lattera@gmail.com>
To:        Neel Natu <neelnatu@gmail.com>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: FreeBSD bhyve VM Exiting
Message-ID:  <2487562.Nj6jnlQzjX@hbsd-dev-local>
In-Reply-To: <CAFgRE9H1BTLxrcor%2B=-icT%2BOYMQusB2KD9=%2BRtiEFp2nL3MqtQ@mail.gmail.com>
References:  <CADt0fhxTdpyvttJgVnXe90nB_cMe3WPNPAAHabxq9hcUEMQ=tA@mail.gmail.com> <CAFgRE9H1BTLxrcor%2B=-icT%2BOYMQusB2KD9=%2BRtiEFp2nL3MqtQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--nextPart1728346.4RnBHVCunU
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Friday, December 26, 2014 12:07:44 PM Neel Natu wrote:
> Hi Shawn,
> 
> On Fri, Dec 26, 2014 at 6:26 AM, Shawn Webb <lattera@gmail.com> wrote:
> > Hey All,
> > 
> > I'm running a FreeBSD/amd64 11-current (r276204) guest VM in bhyve. It
> > seems that running Poudriere in it causes the VM to exit.
> > 
> > This is what bhyve outputs when the VM dies:
> >         reason          VMX
> >         rip             0xffffffff80d68564
> >         inst_length     5
> >         status          0
> >         exit_reason     2
> >         qualification   0x0000000000000000
> >         inst_type               0
> >         inst_error              0
> > 
> > I have no idea what "reason VMX" means or what "exit_reason 2" means. Is
> > there a way to decode that?
> 
> Exit reason '2' is a triple fault.
> 
> > What kinds of info/data do you guys need to debug this?
> 
> You'll need a FreeBSD host with svn revision >= 276098 and a custom
> kernel config to enable KTR.
> https://svnweb.freebsd.org/base?view=revision&revision=276098
> 
> Then you can set the following tunable "hw.vmm.trace_guest_exceptions"
> to "1" before loading vmm.ko. This will cause bhyve to trace all guest
> exceptions via KTR. You can verify that the tunable took effect using
> 'sysctl hw.vmm.trace_guest_exceptions'.
> 
> When the bhyve process exits you can then dump the KTR entries using
> something like this: 'sudo ktrdump -cto /tmp/ktrdump.out'. You'll
> probably want to do this in a script so the ktrdump(8) happens
> immediately after bhyve(8) exits.
> 
> I use the following options in my kernel config to enable KTR:
> options KTR
> options KTR_MASK=(KTR_GEN)
> options KTR_ENTRIES=(4*1024*1024)
> 
> Hope this helps.
> 
> best
> Neel

Hey Neel,

Thanks for the helpful suggestions! The good thing is that my host is already 
on a revision >= 276098 and my kernel is already built with KTR. With 31c3 
going on, the soonest I can do that will be Tuesday or Wednesday of next week. 
I'll update you then.

Thanks,

Shawn
--nextPart1728346.4RnBHVCunU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJUnwcRAAoJEGqEZY9SRW7udhAP/1T0NtXGwdTLFdlpSg9YNy1f
UkmIC4KYgdGLYoy57y13Fp/6doUoPqPLpH6/N2iU32pUvluPXwEhzYg1Zu6e1gaC
MzdSrCCMwV0nfGuoxpcHcY1C7xneKfXX6L+vqPi7axIL59SGmx+TI/fPRvjvTtee
il8vT8QCNYTNyYEo7IGCQKptDRjvg/JTHn8PCBEdG3K4M20uxa2QU/XfxwCWC5Ui
E+JRm6ZFoJtVFUd5ViqNrPik57s0mBJ09SjtjsXaLx/biC7z0VQNqHBRjnm7LNgL
YoCFkTgjq93BnQAZucmDBEbKjS1B9Ty1pezmRSfS9ln5+ylrTQ8B05XOlJrT72ra
jJ0mom995Zzb75epZ7KeHHBbCvxfy8nhXfBweZiYPBxQlzU7SHbINC+bE1fN1xQs
nW0RmBIfCuByy3O/IYXTNsu8dhwknJAVWvru7gXKSV17SWAfKbtl2oJGr68swkgu
fk5hspmLN+MK+zMR5LveARjNDN77VxFF1MZob51QBbCTgvHkpC1WnUcbRmQ8sQ/g
faaWx1beIy3egjB+ZgAbeCQjRqNWZ8BhDh1ZiNLrOylaAdO2BcQM5FUXhHNqcQhu
fxR1dlNCp0Lc5eIrrZQCmR1LrFUnwREcgT42fKslFG9EnNtLBIaeC6eSRSkf0Mqe
UzgN/BgP+LnPMZtw9p9w
=nEMY
-----END PGP SIGNATURE-----

--nextPart1728346.4RnBHVCunU--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2487562.Nj6jnlQzjX>