On Tue, Apr 10, 2018 at 02:31:15PM +0000, Olivier Cherrier wrote:
> On Sat, Apr 07, 2018 at 11:46:42AM -0700, ***@azathoth.net wrote:
> > > So i looked up logs and stuff and came to the point that my issues are
> > > exactly this ones:
> > > http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html
> > >
> > > It seems the issue was not further discussed and/or fixed?
> > >
> > > Regards,
> > > Aaron
> > >
> > > --
> > > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/
> > > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion
> > > GPG: 0x7A65E38D55BE96FE
> > > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE
> > >
> > You are jumping to conclusions.
> > All we know is that your VMs failed to run at some point. Whether or not it
> > is "exactly the same" as that other post is unknown, since you didn't run with
> > VMM_DEBUG and give us any more info. Or even submit a proper bug report.
> > For what it's worth, I'm still working on that other issue.
> For me, the issue never went away.
> I would say it is even more frequent now than before (end of 2017).
> Olivier Cherrier
> Phone: +352691754777
Yep, I dusted off that tree and spent a few hours on it last night.
Hopefully have a working diff soon; the EPT misconfigurations are gone but I'm
running into a uvm page list accounting error now that results in panics when
the VMs are torn down. I know why it's happening but the alternative approach
is a bit more messy and I'd hoped to stay away from that. But maybe I'll have