On Sat, Jun 23, 2018 at 03:54:40PM -0500, Ax0n wrote: > On Sat, Jun 23, 2018 at 6:10 AM, Stefan Sperling <s...@stsp.name> wrote: > > > See https://marc.info/?l=openbsd-bugs&m=152960299009667&w=2 for > > a patch you could test. > > (raw patch: https://marc.info/?l=openbsd-bugs&m=152960299009667&q=raw) > > > > FWIW, that patch didn't apply cleanly to a fresh pull of the tree from > GitHub. I know it's not OFFICIALLY -CURRENT for realsies but it's what I > have been using on this laptop for months. It sounds like it was probably > patched against -STABLE? I didn't read the entire thread on bugs@. I have > tried with 3 daily snapshots in a row and I'm having the same problem. I > haven't actually fired up vmm in a few weeks, so I'm not sure exactly when > it quit working. I'm re-building with VMM_DEBUG first. > > Mike, I'll send all relevant info (dmesg, vmd -dvvv, vm.conf) to bugs@ once > I have it, unless this sounds like an ongoing thing you probably have on > your radar already. I'm not in a huge rush, so I can wait a bit if you > think you have something that'll make it into -CURRENT in a while.
-current already has the patch. -stable is what that link above could be applied to. if -current is failing for you, the output of VMM_DEBUG at the time of crash would be useful. -ml
