Date: Mon, 15 Oct 2018 10:25:40 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Mike Tancsa <mike@sentex.net>, freebsd-virtualization@freebsd.org Subject: Re: CFT: Reload LDTR after #VMEXIT on AMD-v in bhyve Message-ID: <f8335171-df16-8099-1cb0-279d593bf5c4@FreeBSD.org> In-Reply-To: <5a9c983c-3e10-58fd-be1f-bfffca2d9afd@sentex.net> References: <b74d13e5-1f76-1e28-3034-7ef32b983d32@FreeBSD.org> <8282ebc8-7287-04fa-42d7-2c8501c4b979@sentex.net> <a2fdb644-c608-b1a7-ec8a-ce78e8f8ccf6@FreeBSD.org> <5a9c983c-3e10-58fd-be1f-bfffca2d9afd@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/15/18 10:11 AM, Mike Tancsa wrote: > On 10/15/2018 12:23 PM, John Baldwin wrote: >> >> That panic doesn't really make sense. :( The patch only changes behavior >> when you are actually running a guest, it doesn't affect anything in the >> vmm.ko initialization. > > I dont understand either. I have a few klds to load. Is it possible > something is getting initialized out of order at boot up time ? r339355 > seems to have fixed it for me. But I suspect the real issue might come > back some other way > > https://lists.freebsd.org/pipermail/svn-src-head/2018-October/118820.html > > Regardless, I tested with your patch an amd64 and i386 vm and all seems > to work fine Ok, thanks! -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f8335171-df16-8099-1cb0-279d593bf5c4>